I have seen both a trap 12 and a trap 9 from a Friday Feb. 2 kernel. This is
occuring on my laptop (AST Ascentia 810N) which I can't seem to get to create a
core dump. Here is a hand transcription of what I see.
Mounting root from ufs:/dev/ad0s1a
pccard: card inserted, slot 0
pccard: card inserted, slot 1
kernel trap 9 with interrupts disabled
Fatal trap 9: general protection fault while in kernel mode
instruction pointer = 0x8:0xc0270ad8
stack pointer = 0x10:0xc2fb4f50
frame pointer = 0x10:0xc2fb4f64
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 16 (irq14:ata0)
kernel: type 9 trap, code=0
Stopped at sw1b+0x77: ltr %si
backtrace
sw1b(4000) at sw1b+0x77 (note this is actually swtch())
ithd_loop(0,c2fb4fa8) at ithd_loop+0xf7
fork_exit(c0275bd0,0,c2fb4fa8_ at fork_exit+0x2d
fork_trampoline() at fork_trampoline+0x8
I don't have WITNESS or INVARIANTS at this time and don;t have a serial console
so I can't capture the output.
I can try adding these to my kernel and transcribe a little bit by hand. I can
also send my kernel config and dmesg from a Nov kernel which boots.
Jim Bloom
[EMAIL PROTECTED]
John Baldwin wrote:
>
> On 05-Feb-01 Crist J. Clark wrote:
> > I don't recall reports of trouble with recent CURRENT, but my CVSup
> > from yesterday afternoon is panicing. Before I try too debug this, has
> > anyone been getting these or knows what I might be missing?
> >
> > Boot messages and the panic info are attached.
>
> Could you please turn on DDB, WITNESS, and INVARIANTS in your kernel and see if
> you can reproduce this? Also, compile the kernel with debug symbols. Then
> type 'trace' at the db> prompt when it does to get a backtrace of where it blew
> up. Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
