> > I issued the call __db_show_panic_cmd() command and the response
> > was:
> >
> > Panic string: (null)
> >       0xa
> 
> Ouch... a (null) panic string... this is wierd...
> 

Hmm, there used to be one or two places where the kernel would drop into 
ddb before panicing.  I can't remember if they've all been removed.

A stack backtrace would be useful, it would at least tell us the function 
that was dying.

Also, you could try just continuing.  What happens then?

R.