Здравствуйте, FreeBSD.
Fatal double fault:
eip = 0xc0e538e8
esp = 0xc7945004
ebp = 0xc7945c64
cpuid = 3; apic id = 03
panic: double fault
cpuid = 3
KDB: stack backtrace:
#0 0xc0af724f at kdb_backtrace+0x4f
#1 0xc0ac3c4f at panic+0x16f
#2 0xc0e68aab at dblfault_handler+0x9b
Uptime: 17h57m50s
uname -a
FreeBSD newflux 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #4 r239949: Fri Aug 31
16:57:42 EEST 2012 root@newflux:/usr/obj/usr/src/sys/KES_KERN_v9 i386
Fatal double fault:
eip = 0xc0e538e8
esp = 0xc7945004
ebp = 0xc7945c64
cpuid = 3; apic id = 03
panic: double fault
cpuid = 3
KDB: stack
2011
:/usr/obj/usr/src/sys/PAE_KES
Panic String: double fault
Dump Parity: 3261793647
Bounds: 9
Dump Status: good
# kgdb kernel.debug /var/crash/vmcore.9
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License
Occasionally, I get a fatal double fault after halt -p.
Anyone know about this already?
I wrote down the info, it anyone wants it.
I searched using the search box on the home page, but none of the hits looked
like this panic.
I will search the mailing list archives now
Hi Bernt,
A few observations:
1) This double fault apparently occurs fairly early in your boot
process. Do you initialize anything late, like an external drive or
some other hardware?
2) By your saying that you "usually" get either trap 9 or 12, I
assume it happens frequently enou
about every 1.5 to 2 weeks, the server throws the error:
fatal double fault
cpuid=15
spinlock sched lock held by 0xff032f3c1500 > 5 seconds
This server is located in a colo many miles away. I had to have a person
at the colo facility read off the message that was on the screen. I hope
weeks, the server throws the error:
fatal double fault
cpuid=15
spinlock sched lock held by 0xff032f3c1500 > 5 seconds
This server is located in a colo many miles away. I had to have a person
at the colo facility read off the message that was on the screen. I hope
it is exact (or
