Bug 210801 - [panic] Fatal trap 12: page fault while in kernel mode (new in 11.0-ALPHA6 from 11.0-ALPHA3)
Summary: [panic] Fatal trap 12: page fault while in kernel mode (new in 11.0-ALPHA6 fr...
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2016-07-03 23:57 UTC by Jason Unovitch
Modified: 2016-07-06 00:22 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Unovitch freebsd_committer freebsd_triage 2016-07-03 23:57:48 UTC
Possible regression between ALPHA3 and ALPHA6. It's happened randomly while doing some Poudriere runs and going back and forth at the console testing ports.   Sadly I do not have a replication case just yet but have had two panics since updating Friday.

- Before
FreeBSD 11.0-ALPHA3 #0 r301817M: Sat Jun 11 08:34:23 UTC 2016

- After
FreeBSD 11.0-ALPHA6 #0 r302303M: Fri Jul  1 04:55:24 UTC 2016

- Changes for the 'M'
M       share/man/man4/coretemp.4
M       sys/dev/coretemp/coretemp.c

- Excerpt from core:
...
#0  doadump (textdump=0) at pcpu.h:221
221     pcpu.h: No such file or directory.
        in pcpu.h
(kgdb) #0  doadump (textdump=0) at pcpu.h:221
#1  0xffffffff8039beab in db_dump (dummy=<value optimized out>, dummy2=false, 
    dummy3=0, dummy4=0x0) at /usr/src/head/sys/ddb/db_command.c:533
#2  0xffffffff8039bca9 in db_command (cmd_table=<value optimized out>)
    at /usr/src/head/sys/ddb/db_command.c:440
#3  0xffffffff8039ba04 in db_command_loop ()
    at /usr/src/head/sys/ddb/db_command.c:493
#4  0xffffffff8039e9eb in db_trap (type=<value optimized out>, 
    code=<value optimized out>) at /usr/src/head/sys/ddb/db_main.c:251
#5  0xffffffff80b323d3 in kdb_trap (type=<value optimized out>, 
    code=<value optimized out>, tf=<value optimized out>)
    at /usr/src/head/sys/kern/subr_kdb.c:654
#6  0xffffffff80fd52d1 in trap_fatal (frame=0xfffffe0469f087e0, eva=1036)
    at /usr/src/head/sys/amd64/amd64/trap.c:836
#7  0xffffffff80fd5503 in trap_pfault (frame=0xfffffe0469f087e0, usermode=0)
    at /usr/src/head/sys/amd64/amd64/trap.c:691
#8  0xffffffff80fd4aac in trap (frame=0xfffffe0469f087e0)
    at /usr/src/head/sys/amd64/amd64/trap.c:442
#9  0xffffffff80fb7ba1 in calltrap ()
    at /usr/src/head/sys/amd64/amd64/exception.S:236
#10 0xffffffff80a9164c in filt_proc (kn=0xfffff800918b6900, 
    hint=<value optimized out>) at /usr/src/head/sys/kern/kern_event.c:473
#11 0xffffffff80a8fbad in knote (list=<value optimized out>, hint=2147483648, 
    lockflags=<value optimized out>)
    at /usr/src/head/sys/kern/kern_event.c:2045
#12 0xffffffff80a96dad in exit1 (td=0xfffff8023875a000, rval=184783104, 
    signo=0) at /usr/src/head/sys/kern/kern_exit.c:515
#13 0xffffffff80a95ddd in sys_sys_exit (td=0xfffff800918b6900, 
    uap=<value optimized out>) at /usr/src/head/sys/kern/kern_exit.c:178
#14 0xffffffff80fd5c6e in amd64_syscall (td=<value optimized out>, traced=0)
    at subr_syscall.c:135
#15 0xffffffff80fb7e8b in Xfast_syscall ()
    at /usr/src/head/sys/amd64/amd64/exception.S:396
#16 0x000000080092a8ca in ?? ()
Previous frame inner to this frame (corrupt stack?)
Current language:  auto; currently minimal

Given the filt_proc/knote mentions, CC the folks from https://reviews.freebsd.org/D6859 (r302235) as a best guess looking at the SVN log for guidance.
(kgdb)
Comment 1 Jason Unovitch freebsd_committer freebsd_triage 2016-07-04 00:02:05 UTC
The full core file is available at freefall.freebsd.org:/home/junovitch/core.txt.pr201801-1

I can try reverting the commit I guessed on or just standby on any guidance. Thanks!
Comment 2 Konstantin Belousov freebsd_committer freebsd_triage 2016-07-04 00:13:08 UTC
(In reply to Jason Unovitch from comment #0)
This is most likely fixed by r302308.  If it is not, I will ask for further info.
Comment 3 Jason Unovitch freebsd_committer freebsd_triage 2016-07-04 00:17:41 UTC
(In reply to Konstantin Belousov from comment #2)
Thank you for the quick response.  I am updating my kernel now and will report back what I see.
Comment 4 Jason Unovitch freebsd_committer freebsd_triage 2016-07-06 00:22:29 UTC
I believe this is resolved. 48 hours with no panic on r302331 is an improvement over the behavior observed before the above mentioned fix.  If I happen to see it again I'll reopen.  Thank you Konstantin.