Date: Sat, 30 May 1998 03:50:34 -0700 From: brian@worldcontrol.com To: freebsd-current@FreeBSD.ORG Cc: toor@dyson.iquest.net Subject: Panic: SMP, CAM, Dyson SMP patches Message-ID: <19980530035034.A26571@top.worldcontrol.com>
next in thread | raw e-mail | index | archive | help
I'm running 3.0-CURRENT #2: Fri May 29 12:45:20 PDT 1998
with CAM, and Dyson's 26.may SMP patches.
It panic'ed during a 'make -j 8 buildworld' pretty near the end.
It did not panic during two 'make -j 4 buildworld's.
I'm also quite suspicious of these silo overflow messages. They
only occur with a kernel running the Dyson SMP patches.
...
May 30 02:11:18 bls2 /kernel: sio1: 1 more silo overflow (total 33)
May 30 02:32:16 bls2 /kernel: sio1: 1 more silo overflow (total 34)
May 30 03:08:43 bls2 /kernel: sio1: 1 more silo overflow (total 35)
Fatal trap 12: page fault while in kernel mode
mp_lock = 01000003; cpuid = 1; lapic.id = 00000000
fault virtual address = 0xffffff8e
fault code = supervisor write, page not present
instruction pointer = 0x8:0xf4c53c5b
stack pointer = 0x10:0xf4c53c2c
frame pointer = 0x10:0xf4c53c48
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 9871 (make)
interrupt mask = <- SMP: XXX
trap number = 12
panic: page fault
mp_lock = 01000003; cpuid = 1; lapic.id = 00000000
boot() called on cpu#1
syncing disks...
regretably I had the kernel in DDB_UNATTENDED, rather than
DDB and the system froze after syncing disks...
Why am I not getting kernel crashdumps? I've set:
savecore_enable="YES" # Save kernel crashdumps for debugging (or NO).
dumpdev="/dev/da0s2b" # Device name to crashdump to (if enabled).
in /etc/rc.conf.
--
Brian Litzinger <brian@litzinger.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980530035034.A26571>