Well, a DDB traceback would help. Failing that, at least what does
0xc101891b correspond to.... otherwise, it's all ENOGUESS....
On Sun, 17 Oct 1999, Michael Reifenberger wrote:
> Hi,
> I got the following crash since a couple of time since upgrading one machine to
> -current as of today. It seems to occurs during somewhat heavier diskaccess.
> Sorry no detailed backtrace for now because I deleted my kernel.debug since the
> last crash and dumping 256MB takes a long time...
>
> Does the crash trigger anything.
>
> SMP 2 cpus
> IdlePTD 3194880
> initial pcb at 282c40
> panicstr: page fault
> panic messages:
> ---
> Fatal trap 12: page fault while in kernel mode
> mp_lock = 00000002; cpuid = 0; lapic.id = 01000000
> fault virtual address = 0xdeadc0e6
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc101891b
> stack pointer = 0x10:0xce004d3c
> frame pointer = 0x10:0xce004d4c
> 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 = 6296 (bash)
> interrupt mask = none <- SMP: XXX
> trap number = 12
> panic: page fault
> mp_lock = 00000002; cpuid = 0; lapic.id = 01000000
> boot() called on cpu#0
>
>
> Bye!
> ----
> Michael Reifenberger
> Plaut Software GmbH, R/3 Basis
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
