Re: kernel trap 12

[Jeroen Ruigrok/asmodai <asmodai@xxxxxx>]

-On [20040717 03:12], Matthew Dillon (dillon@xxxxxxxxxxxxxxxxxxxx) wrote:
>    Well, it's obviously a null function pointer fault but the question
>    is what device was it trying to call through?  Try the following
>    patch to see if better information can be gleaned.

I had already done that yesterday.
Shortcutting the device_quiet() doesn't help at all.

The device_printf() was something I didn't try yet.  Combined with BUS_DEBUG
still in my kernel it yields:

devclass_find_internal:115: looking for nexus
devclass_add_device:404: (null) in devclass nexus
devclass_alloc_unit:353: unit 0 in devclass nexus
devclass_alloc_unit:393: now: unit 0 in devclass nexus
root_bus_configure:2309: .
devclass_find_driver_internal:253: nexus in devclass root
device_probe_child:641: Trying nexus
nexus0: nexus_probe()

After that it kernel trap 12's.

-- 
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
Free Tibet! http://www.savetibet.org/ | http://www.tibet.nu/
http://www.tendra.org/   | http://diary.in-nomine.org/
Sometimes I wonder why are we so blind to face...