For some reason I'm occasionally getting an endless loop of "panic:
trap" instead of DDB, and the only recourse is to drop into the RMC and
force a hard reset.  It's as if DDB is itself sometimes triggering a
trap for some reason.

This is getting really annoying for me as it takes a very long time to
bring an ES40 back to life after a hard reset (especially when you have
it test all its 16GB of memory :-)

If anyone has any clues or suggestions....

(in this case the panic is because my RAIDframe backport is failing to
do the autoconfigure and thus there's no valid root filesystem, but I'd
really rather it drop to DDB so I could just reboot directly and avoid
the full "init" delay!)

panic: no init

CPU 1: fatal kernel trap:

CPU 1    trap entry = 0x3 (instruction fault)
CPU 1    a0         = 0x1
CPU 1    a1         = 0xfffffd01fc0003f8
CPU 1    a2         = 0xfffffd01fc0003fd
CPU 1    pc         = 0xfffffc000050cae4
CPU 1    ra         = 0xfffffc00003efd40
CPU 1    pv         = 0xfffffc000050cae0
CPU 1    curproc    = 0xfffffc00872a4000
CPU 1        pid = 1, comm = init

panic: trap

CPU 1: fatal kernel trap:

CPU 1    trap entry = 0x3 (instruction fault)
CPU 1    a0         = 0x1
CPU 1    a1         = 0xfffffd01fc0003f8
CPU 1    a2         = 0xfffffd01fc0003fd
CPU 1    pc         = 0xfffffc000050cae4
CPU 1    ra         = 0xfffffc00003efd40
CPU 1    pv         = 0xfffffc000050cae0
CPU 1    curproc    = 0xfffffc00872a4000
CPU 1        pid = 1, comm = init

panic: trap

[[ and so on.... ]]

-- 
						Greg A. Woods

H:+1 416 218-0098  W:+1 416 489-5852 x122  VE3TCP  RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>          Secrets of the Weird <woods@weird.com>