> Deliberately breaking into DDB, e.g. via serial console BREAK, can lead
> to an abrupt end of the debugging session once the hardware watchdog
> reboots the machine. This is because all CPUs are IPL_HIGH. None of them
> tickles the watchdog anymore.
> The same is true on panic, when the system enters DDB. If you really
> want the system to reboot on panic, set ddb.panic to 0.
> So stop the watchdog timer when entering DDB. Restart it after the
> debugging session finished.
mpi@ ok'ed this already. Any more oks? Anyone wants to commit this?