[Bug 198208] FreeBSD 10.1 multiple kernel panics
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Mar 2 21:27:10 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198208
Bug ID: 198208
Summary: FreeBSD 10.1 multiple kernel panics
Product: Base System
Version: 10.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: lists.dan at gmail.com
I recently installed 10.1 on a server that had been running 8.4. Since
installing 10.1 it panics and reboots when under load. It is rare for it to go
a couple of days without panicing. Here is the info from the latest crash.
FreeBSD name.replaced 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0: Fri Feb 27
11:17:46 CST 2015 root at name.replaced:/usr/obj/usr/src/sys/TEST amd64
(The TEST kernel is just GENERIC and optionsIPFIREWALL_DEFAULT_TO_ACCEPT)
Hostname process = trap number = 12
1341 (amavisd-milter)
panic: page fault
cpuid = 3
KDB: stack backtrace:
#0 0xffffffff809638e0 at kdb_backtrace+0x60
#1 0xffffffff80928a05 at panic+0x155
#2 0xffffffff80d305ff at trap_fatal+0x38f
#3 0xffffffff80d30918 at trap_pfault+0x308
#4 0xffffffff80d2ff7a at trap+0x47a
#5 0xffffffff80d15e62 at calltrap+0x8
#6 0xffffffff809c66a5 at vfs_busy+0x45
#7 0xffffffff809bebae at lookup+0x75e
#8 0xffffffff809be154 at namei+0x4d4
#9 0xffffffff809d244e at kern_statat_vnhook+0xae
#10 0xffffffff809d22dd at sys_stat+0x2d
#11 0xffffffff80d30f31 at amd64_syscall+0x351
#12 0xffffffff80d1614b at Xfast_syscall+0xfb
Uptime: 2d21h52m53s
Dumping 1202 out of 16347 MB:..2%..11%..22%..31%..42%..51%..62%..71%..82%..91%
Reading symbols from /boot/kernel/ipl.ko.symbols...done.
Loaded symbols for /boot/kernel/ipl.ko.symbols
Reading symbols from /boot/kernel/ums.ko.symbols...done.
Loaded symbols for /boot/kernel/ums.ko.symbols
#0 doadump (textdump=<value optimized out>) at pcpu.h:219
219 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) #0 doadump (textdump=<value optimized out>) at pcpu.h:219
#1 0xffffffff80928682 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:452
#2 0xffffffff80928a44 in panic (fmt=<value optimized out>)
at /usr/src/sys/kern/kern_shutdown.c:759
#3 0xffffffff80d305ff in trap_fatal (frame=<value optimized out>,
eva=<value optimized out>) at /usr/src/sys/amd64/amd64/trap.c:865
#4 0xffffffff80d30918 in trap_pfault (frame=0xfffffe0469de95d0,
usermode=<value optimized out>) at /usr/src/sys/amd64/amd64/trap.c:676
#5 0xffffffff80d2ff7a in trap (frame=0xfffffe0469de95d0)
at /usr/src/sys/amd64/amd64/trap.c:440
#6 0xffffffff80d15e62 in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:232
#7 0xffffffff809152c1 in __mtx_lock_sleep (c=0xfffff80012a82348,
tid=18446735277953190176, opts=0, file=0x0, line=0)
at /usr/src/sys/kern/kern_mutex.c:433
#8 0xffffffff809c66a5 in vfs_busy (mp=0xfffff80012a82330, flags=0)
at /usr/src/sys/kern/vfs_subr.c:411
#9 0xffffffff809bebae in lookup (ndp=0xfffffe0469de9948)
at /usr/src/sys/kern/vfs_lookup.c:783
#10 0xffffffff809be154 in namei (ndp=0xfffffe0469de9948)
at /usr/src/sys/kern/vfs_lookup.c:302
#11 0xffffffff809d244e in kern_statat_vnhook (td=0xfffff80014110920,
flag=<value optimized out>, fd=-100,
path=0x803c11850 <Address 0x803c11850 out of bounds>,
pathseg=UIO_USERSPACE, sbp=0xfffffe0469de9a60, hook=0x100d08)
at /usr/src/sys/kern/vfs_syscalls.c:2284
#12 0xffffffff809d22dd in sys_stat (td=0xfffff80014110920,
uap=0xfffffe0469de9b80) at /usr/src/sys/kern/vfs_syscalls.c:2264
#13 0xffffffff80d30f31 in amd64_syscall (td=0xfffff80014110920, traced=0)
at subr_syscall.c:134
#14 0xffffffff80d1614b in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:391
#15 0x0000000800f9239a in ?? ()
Previous frame inner to this frame (corrupt stack?)
Hostname language: auto; Hostnamely minimal
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list