Bug #840
closedpanic without a panic message
0%
Description
I was running many things (including trying to compile a lot of pkgsrc packages
inside a SMP vkernel) and the machine paniced. Since I was in X, I could not see
the panic message itself, but fortunately I got a dump.
The dump is available at leaf:~rumko/crash/dumps/*.0
backtrace:
#0 dumpsys () at thread.h:83
#1 0xc0295f21 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc029623e in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:797
#3 0xc04e0800 in trap_fatal (frame=0xf145db94, eva=Variable "eva" is not available.
) at /usr/src/sys/platform/pc32/i386/trap.c:1096
#4 0xc04e0958 in trap_pfault (frame=0xf145db94, usermode=0, eva=2635001959) at
/usr/src/sys/platform/pc32/i386/trap.c:997
#5 0xc04e1010 in trap (frame=0xf145db94) at
/usr/src/sys/platform/pc32/i386/trap.c:680
#6 0xc04cdbb6 in calltrap () at /usr/src/sys/platform/pc32/i386/exception.s:783
#7 0xc04ddbbb in pmap_remove_pte (pmap=0xe0082454, ptq=Variable "ptq" is not
available.
) at /usr/src/sys/platform/pc32/i386/pmap.c:1518
#8 0xc04de057 in pmap_remove (pmap=0xe0082454, sva=3217022976, eva=3217027072)
at /usr/src/sys/platform/pc32/i386/pmap.c:1631
#9 0xc04142da in vm_map_madvise (map=0xe00823d0, start=3217022976,
end=3217027072, behav=10, value=0)
at /usr/src/sys/vm/vm_map.c:1738
#10 0xc041e24a in sys_vmspace_mcontrol (uap=0xf145dcf0) at
/usr/src/sys/vm/vm_vmspace.c:359
#11 0xc04e16d9 in syscall2 (frame=0xf145dd40) at
/usr/src/sys/platform/pc32/i386/trap.c:1339
#12 0xc04cdc55 in Xint0x80_syscall () at
/usr/src/sys/platform/pc32/i386/exception.s:872
#13 0x282b6cfc in ?? ()
#14 0x66177b40 in ?? ()
#15 0x0000002f in ?? ()
#16 0x00000000 in ?? ()
#17 0x00000000 in ?? ()
#18 0x00000000 in ?? ()
#19 0x00000000 in ?? ()
#20 0x4bae3000 in ?? ()
#21 0xf0dc0e00 in ?? ()
#22 0xff800000 in ?? ()
#23 0xf145d9e8 in ?? ()
#24 0xf145d9a8 in ?? ()
#25 0xc0604894 in softclock_pcpu_ary ()
#26 0xc029e655 in lwkt_switch () at /usr/src/sys/kern/lwkt_thread.c:752
Previous frame inner to this frame (corrupt stack?)
Updated by tuxillo over 18 years ago
Won't fix. Lack of information. Rumko told he'll report back again in the case
it happens with latest.