Hi Stuart, I hadn't set ddb.console to 1 before, so unfortunately this isn't an option. I will do that in future though.. Looks like a hard-reboot is my only option. Thanks,
Cliff. Stuart Henderson wrote: > On 2008-07-14, clifford bailey <[EMAIL PROTECTED]> wrote: > >> First question: We have the machine left in its failed state at the >> moment. Is there a signal I can send it over the serial port to get the >> machine to panic before rebooting it (to give us as much information as >> possible)? >> > > Depends whether you A) have it set to use serial console and B) have > already set ddb.console=1 in sysctl.conf. If both those things are true, > send it a break over the serial port to enter DDB. > > N.B. whether ddb.console with serial console is useful depends on > what you have on the serial port; some devices send a break when they > reboot, which is not quite what you want, unless you want to find out > your terminal server rebooted by noticing all the attached devices > need you to "continue"... > > (as an aside, this seemed like knowledge worth passing on: if you've > got a serial port, maybe a USB-RS232 adapter, that doesn't let you send > break, apparently sending a single NULL at 50baud emulates it for some > devices).
