Comment 231 for bug 1239578
Revision history for this message
| Larry Finger (larry-finger-lwfinger) wrote | #231 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Unfortunately, when you need to power off the system in this way, information being written to the logs is lost.
Whenever there is a particular sequence that causes a crash, I usually cause a terminal to sleep for 5 secs, and then have it do the sequence - all in a single line separated by a semicolon. Once the sleep is started, I switch to the logging console. On my system, that is selected with CTRL-ALT-F10. The graphics console is at CTRL-ALT-F7. Once the crash happens, I either write down the crucial info, or I take a photo of the screen.
If you have a second system, you might also look at the network console method of capturing dump info.