I tested some things with sparc64 crashdumps today and noticed an inconsistent
behaviour: if you break into ddb and say "reboot 0x104" the system will most
likely not just dump, but trigger DIAGNOSTIC/LOCKDEBUG assertions (e.g.
when aquiring mutexes due to still being in interrupt context). This assertion
will panic, and drop back to ddb. Now repeating the same "reboot 0x104"
will work - since "panicstr" is set.

I would like to change this with the following patch.

Any objections?

Martin