From: Georg C. F. G. <gr...@gn...> - 2004-10-06 12:30:56
|
>> When kdb is left and the buffer is different from 0, the contents >> are dumped to dmesg/syslog. nc> Something like printk :> It wouldn't work with suspending because nc> we're overwriting such buffers when copying the original kernel nc> back (with the contents from suspend-time). Furthermore, it won't nc> help if you get such a crash because you're never going to start nc> syslogd and get the data written. I agree that it would not help in all cases. In this case it would have helped, though. The machine is running, syslog is doing its job -- that is how I got the sysrq-T output. So if kbd had support for that, we could have saved ourselves the trouble of taking a photograph of the screen and mailing that around. Speaking of which: Since you told me that you did not see it, I just resent it, please let me know whether it reaches you this time. Regards, Georg -- Georg C. F. Greve <gr...@gn...> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org) |