On Mon, Aug 23, 1999 at 09:44:10PM +0100, a little birdie told me
that Doug Rabson remarked
>
> It seems like isa bus is never being attached for some reason. Have a
> look at nexus_attach() and see if anything suspicious is happening (like
> an error return from device_probe_and_attach()).
FWIW, I've been getting a panic on bootup for months (mid-April, maybe?)
on -CURRENT on one of my systems; could this be at all related?
Here is some info from the panic I got mid-late April. I'll try
cvsup'ing and building a new kernel tonite and see if it's fixed, but in
case it isn't here's some info.
Bootup gets to here:
isab0: <PCI to ISA bridge (vendor:0e11 device:0002)> at device 15.0 on pci0
and them *boom*
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24000208
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01456f5
stack pointer = 0x10:0xc02d5ef8
frame pointer = 0x10:0xc02d5f04
code segment = base 0x0, limit 0xfffff, type 0x1b
= DRL 0, pres 1, def32 1, gran 1
processor eflags = interrupts enabled, resume, IOPL=0
current process = 0 ( )
interrupt mask = net tty bio cam
kernel: type 12 trap, code:0
DDB reveals
Stopped at device_probe_and_attach+0x9 movl 0x8(%ebx),%edi
trace shows:
device_probe_and_attach(24000200) at device_probe_and_attach+0x9
bus_generic_attach(c09e1880, c02d5f38, c0145737, c09e1880, c09e1880)
at bus_generic_attach+0x16
DEVICE_ATTACH(c09e1880, c09e1880, 0, c061cb40, c02d5f48)
at DEVICE_ATTACH+0x25
--
Matthew Fuller (MF4839) | [EMAIL PROTECTED]
Unix Systems Administrator | [EMAIL PROTECTED]
Specializing in FreeBSD | http://www.over-yonder.net/
FutureSouth Communications | ISPHelp ISP Consulting
"The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
