In article <200503041529.j24FTUUq023054@ector.cs.purdue.edu>,
J Chapman Flack  <flack@cs.purdue.edu> wrote:
>Martin Husemann wrote:
>
>> Can you try running it on a kernel with options LOCKDEBUG?
>
>Umm, sure.  Question: that'll probably produce some interesting kernel
>output.  Do you know of any way to get that reliably into a file that's
>flushed near the point where I have to push the big gray button?
>
>I suppose ddb will more the dmesg for me and I can copy it down ... or I
>could try to log it with a terminal emulator and a serial console, but
>I've not bothered trying to set something like that up yet.  I'm looking
>for the lazy way.  :)
>

t /l  will send the trace to the log. If you don't power-cycle the machine,
it will appear in syslog next time you boot (assuming your bios does not
trash memory ofcourse).

christos