Date: Wed, 31 Oct 2012 10:44:06 GMT From: Tommy Sonne Alstrøm <tommy@anakin.ws> To: freebsd-gnats-submit@FreeBSD.org Subject: amd64/173235: Have received two crashes within 1 day after installing new packages: Fatal trap 12: page fault in kernel mode Message-ID: <201210311044.q9VAi67w079723@red.freebsd.org> Resent-Message-ID: <201210311050.q9VAo17R015202@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 173235
>Category: amd64
>Synopsis: Have received two crashes within 1 day after installing new packages: Fatal trap 12: page fault in kernel mode
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-amd64
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Oct 31 10:50:01 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Tommy Sonne Alstrøm
>Release: Freebsd 9.0
>Organization:
personal use
>Environment:
FreeBSD ophelia.anakin.ws 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
I've been running freebsd for about 40 days now on the machine in question without any issues. Yesterday I was migrating apache+mysql data and when I was done I decided to run a zpool scrub (using ZFS raidz). I'm starting to do this and then after about 30 seconds I loose the connection to my machine.
When I got home I find the machine is hanging and it needs to be powered off. The text on the screen is a kernel panic with some call stack (I took a picture).
After a power-off the system was able to reboot but gave a new kernel panic, this time with a dump. The system rebooted and made a crash dump and was able to reboot into some kind of save mode. This is what I got:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x20
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80876af8
stack pointer = 0x28:0xffffff8451ab29e0
frame pointer = 0x28:0xffffff8451ab2a10
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = resume, IOPL = 0
current process = 1192 (smbiod1)
trap number = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff808680fe at kdb_backtrace+0x5e
#1 0xffffffff80832cb7 at panic+0x187
#2 0xffffffff80b185a0 at trap_fatal+0x290
#3 0xffffffff80b18c57 at trap+0x287
#4 0xffffffff80b0324f at calltrap+0x8
#5 0xffffffff80822d50 at _mtx_unlock_sleep+0x50
#6 0xffffffff8185a50c at smb_iod_invrq+0xbc
#7 0xffffffff8185b621 at smb_iod_addrq+0x211
#8 0xffffffff81857fd9 at smb_rq_simple+0x39
#9 0xffffffff8185689e at smb_smb_ssnsetup+0x17e
#10 0xffffffff8185a68f at smb_iod_connect+0x11f
#11 0xffffffff8185b0e0 at smb_iod_thread+0x1d0
#12 0xffffffff8080682f at fork_exit+0x11f
#13 0xffffffff80b0377e at fork_trampoline+0xe
Uptime: 40s
Dumping 816 out of 16088 MB:..2%..12%..22%..32%..42%..51%..61%..71%..81%..91%
Here the zpool scrub managed to finish without errors. Then I rebooted and everything worked fine.
This morning again I've discovered that there was another crash. Again this is what I got:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x20
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80876af8
stack pointer = 0x28:0xffffff8451ab29e0
frame pointer = 0x28:0xffffff8451ab2a10
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = resume, IOPL = 0
current process = 1192 (smbiod1)
trap number = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff808680fe at kdb_backtrace+0x5e
#1 0xffffffff80832cb7 at panic+0x187
#2 0xffffffff80b185a0 at trap_fatal+0x290
#3 0xffffffff80b18c57 at trap+0x287
#4 0xffffffff80b0324f at calltrap+0x8
#5 0xffffffff80822d50 at _mtx_unlock_sleep+0x50
#6 0xffffffff8185a50c at smb_iod_invrq+0xbc
#7 0xffffffff8185b621 at smb_iod_addrq+0x211
#8 0xffffffff81857fd9 at smb_rq_simple+0x39
#9 0xffffffff8185689e at smb_smb_ssnsetup+0x17e
#10 0xffffffff8185a68f at smb_iod_connect+0x11f
#11 0xffffffff8185b0e0 at smb_iod_thread+0x1d0
#12 0xffffffff8080682f at fork_exit+0x11f
#13 0xffffffff80b0377e at fork_trampoline+0xe
Uptime: 40s
Dumping 816 out of 16088 MB:..2%..12%..22%..32%..42%..51%..61%..71%..81%..91%
I use an Intel Server MB with CRC memory so these errors should not occur, but maybe this is a result of faulty memory ? In that case, how can I exclude that?
I've read http://www.freebsd.org/doc/faq/troubleshoot.html#trap-12-panic and
http://www.freebsd.org/doc/faq/advanced.html#kernel-panic-troubleshooting
But since there is these core files I'm thinking maybe the dump is already there ?
Thanks in advance!
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201210311044.q9VAi67w079723>