Re: correction: fatal trap 12 when booting without ACPI (was wrongly Re: Fatal Trap 12 that goes away with NO ACPI --- anyone interested?)

From: Dan Nelson <dnelson_at_allantgroup.com>
Date: Wed, 26 May 2004 00:58:12 -0500
In the last episode (May 25), John Baldwin said:
> On Tuesday 25 May 2004 09:21 am, Klaus Robert Suetterlin wrote:
> > I'm sorry, I mixed it all up:
> >
> > - The sytem hangs with fatal trap 12 if I use default, which is
> > without ACPI (because my loader.conf does not contain
> > ``acpi_load="YES"'').
> >
> > - And it boots ok, when I choose the second (beastie boot menu)
> > entry, which is with ACPI _enabled_ in my case.
> 
> Ok, does the faulting address look like 0x58:0xfyyyy?

Not in my case.  Here's the full panic:

...
Device configuration finished.


Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x10d6d7dc
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc04e6013
stack pointer           = 0x10:0xc0821d48
frame pointer           = 0x10:0xc0821d54
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gram 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 0 (swapper)
kernel: type 12 trap, code = 0
Stopped at      module_lookupbyname+0x13:       movl    0x1c(%ebx),%ecx
db> where
module_lookupbyname(c065638a,c069d2a0,c064cddc,66) at module_lookupbyname+0x13
module_register_init(c06834a8,c0da18a4,c0da18a4,81ec00,81e000) at module_register_init+0x22
mi_startup() at mi_startup+0x90
begin() at begin+0x2c
db>


-- 
	Dan Nelson
	dnelson_at_allantgroup.com
Received on Tue May 25 2004 - 20:58:37 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:55 UTC