Discussion:
Fatal trap 12
(too old to reply)
Manuel Stühn
2018-05-26 11:46:42 UTC
Permalink
Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing
several "Fatal traps 12". Before the update i did not have any of those.
In all cases the traps occured some time after resume.

Below there is some output found in /var/crash/core.txt

__curthread () at ./machine/pcpu.h:231
231 ./machine/pcpu.h: No such file or directory.
(kgdb) #0 __curthread () at ./machine/pcpu.h:231
#1 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:366
#2 0xffffffff80b9a6f0 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:446
#3 0xffffffff80b9ab83 in vpanic (fmt=<optimized out>,
ap=0xfffffe0056507e50)
at /usr/src/sys/kern/kern_shutdown.c:863
#4 0xffffffff80b9a973 in panic (fmt=<unavailable>)
at /usr/src/sys/kern/kern_shutdown.c:790
#5 0xffffffff80ba5c3b in kdb_switch () at
/usr/src/sys/kern/kern_synch.c:377
#6 0xffffffff80ba5bb9 in mi_switch (flags=<unavailable>, newtd=0x0)
at /usr/src/sys/kern/kern_synch.c:406
#7 0xffffffff80bf3f5f in sleepq_timedwait (wchan=<unavailable>,
pri=<unavailable>) at /usr/src/sys/kern/subr_sleepqueue.c:727
#8 0xffffffff833c7bed in linux_add_to_sleepqueue
(wchan=0xfffff8000bf6ad80, task=0xfffff8000bf6ad80, wmesg=<optimized
out>, timeout=50, state=<optimized out>)
at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:70
#9 0xffffffff833c7a58 in linux_wait_event_common (wqh=<optimized out>,
wq=<optimized out>, timeout=50, state=2, lock=0x0)
at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:270
#10 0xffffffff83458de6 in ?? ()
#11 0x000000061d026200 in ?? ()
#12 0x0000000600000000 in ?? ()
#13 0xfffff8000bf6ad80 in ?? ()
#14 0xffffffff833c7540 in ?? ()
at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:167
from /boot/kernel/linuxkpi.ko
#15 0xfffff80007804828 in ?? ()
#16 0xfffff80007804828 in ?? ()
#17 0x0000000000000030 in ?? ()
#18 0x0000000000000000 in ?? ()
(kgdb)


Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x3
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80cc60cb
stack pointer = 0x28:0xfffffe0056508560
frame pointer = 0x28:0xfffffe0056508760
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 10218 (nextcloud)
--
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x300000011
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80cc60cb
stack pointer = 0x28:0xfffffe005e4d1560
frame pointer = 0x28:0xfffffe005e4d1760
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 17918 (DNS Resolver #16)
--
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x3
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80cc60cb
stack pointer = 0x28:0xfffffe0056508560
frame pointer = 0x28:0xfffffe0056508760
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 10218 (nextcloud)

If there is any other information i can provide for solving this, please
let me know.

--
Manuel
blubee blubeeme
2018-05-26 12:32:17 UTC
Permalink
Post by Manuel Stühn
Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing
several "Fatal traps 12". Before the update i did not have any of those.
In all cases the traps occured some time after resume.
Below there is some output found in /var/crash/core.txt
__curthread () at ./machine/pcpu.h:231
231 ./machine/pcpu.h: No such file or directory.
(kgdb) #0 __curthread () at ./machine/pcpu.h:231
#1 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:366
#2 0xffffffff80b9a6f0 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:446
#3 0xffffffff80b9ab83 in vpanic (fmt=<optimized out>,
ap=0xfffffe0056507e50)
at /usr/src/sys/kern/kern_shutdown.c:863
#4 0xffffffff80b9a973 in panic (fmt=<unavailable>)
at /usr/src/sys/kern/kern_shutdown.c:790
#5 0xffffffff80ba5c3b in kdb_switch () at
/usr/src/sys/kern/kern_synch.c:377
#6 0xffffffff80ba5bb9 in mi_switch (flags=<unavailable>, newtd=0x0)
at /usr/src/sys/kern/kern_synch.c:406
#7 0xffffffff80bf3f5f in sleepq_timedwait (wchan=<unavailable>,
pri=<unavailable>) at /usr/src/sys/kern/subr_sleepqueue.c:727
#8 0xffffffff833c7bed in linux_add_to_sleepqueue
(wchan=0xfffff8000bf6ad80, task=0xfffff8000bf6ad80, wmesg=<optimized
out>, timeout=50, state=<optimized out>)
at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:70
#9 0xffffffff833c7a58 in linux_wait_event_common (wqh=<optimized out>,
wq=<optimized out>, timeout=50, state=2, lock=0x0)
at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:270
#10 0xffffffff83458de6 in ?? ()
#11 0x000000061d026200 in ?? ()
#12 0x0000000600000000 in ?? ()
#13 0xfffff8000bf6ad80 in ?? ()
#14 0xffffffff833c7540 in ?? ()
at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:167
from /boot/kernel/linuxkpi.ko
#15 0xfffff80007804828 in ?? ()
#16 0xfffff80007804828 in ?? ()
#17 0x0000000000000030 in ?? ()
#18 0x0000000000000000 in ?? ()
(kgdb)
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x3
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80cc60cb
stack pointer = 0x28:0xfffffe0056508560
frame pointer = 0x28:0xfffffe0056508760
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 10218 (nextcloud)
--
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x300000011
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80cc60cb
stack pointer = 0x28:0xfffffe005e4d1560
frame pointer = 0x28:0xfffffe005e4d1760
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 17918 (DNS Resolver #16)
--
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x3
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80cc60cb
stack pointer = 0x28:0xfffffe0056508560
frame pointer = 0x28:0xfffffe0056508760
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 10218 (nextcloud)
If there is any other information i can provide for solving this, please
let me know.
--
Manuel
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current
Aren't you the guy using the drm-kmod if yes, your custom complied kernel
and not the default kernel causing those issues.

Best,
Owen
Manuel Stühn
2018-05-26 14:56:17 UTC
Permalink
Post by blubee blubeeme
Aren't you the guy using the drm-kmod if yes, your custom complied kernel
and not the default kernel causing those issues.
Best,
Owen
I'm indeed using graphics/drm-stable-kmod, but i do not use a custom
kernel:
uname -rsmv
FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #8 r334167: Thu May 24
20:06:20 CEST 2018
***@valinor:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64

The drm-stable-kmod was installed from ports with the corresponding
src-tree.

--
Manuel
Manuel Stühn
2018-05-30 21:49:02 UTC
Permalink
Post by Manuel Stühn
Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing
several "Fatal traps 12". Before the update i did not have any of those.
In all cases the traps occured some time after resume.
I tried to debug this further by building different kernel versions (all
GENERIC-NODEBUG). The last working revision is r334117, the first not
working is r334123. Revisions 334118-334122 of the kernel did not build,
so i cannot try these.

Any ideas what could cause these issue?

--
Manuel

Continue reading on narkive:
Loading...