Re: kernel trap 12

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:-On [20040720 09:22], Matthew Dillon (dillon@xxxxxxxxxxxxxxxxxxxx) wrote:
:>    This is worth a shot.  Try adding a KKASSERT() after that
:>    PDEBUG line (line 404 in kern/subr_bus.c) so we can hopefully get
:>    a backtrace of who called devclass_add_device() with a dev that
:>    has a NULL name.  If the dev has a NJULL name then it might have a
:>    NULL devclass too.
:
:KASSERT(DEVICENAME(dev) != null, "text")
:works to panic it.
:
:Damn, been ages since I messed with DDB.  Need some future handholding here.
:
:-- 
:Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
 
     Well, lets start with a stack trace ('trace' in ddb).

     p.s. that wasn't a type-o.. I really meant 'KKASSERT'... it's a short
     form of KASSERT that doesn't require a printf string.  e.g.:

     KKASSERT(DEVICENAME(dev) != NULL);

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>