Comment 2 for bug 37218

Revision history for this message
Eric Feliksik (milouny) wrote : kern.log directly after crash

I tried it several times after the system came back from hibernation (so not just a screensaver/sleep-issue) without success:
I just booted, and at the moment the crash often (but not always) happens, when X should kick in, I quickly moved the mouse. Then X actually *did* kick in (maybe it was just time, or maybe the screensaver was de-activated???)
The desktop background was displayed with a black rounded rectangle in the middle (maybe the remains of log-out window). So the mouse-pointer responded for a second, then the system did not respond anymore.

I followed DebuggingSystemCrash instructions:
1) what's posted below is, I'm afraid, not the output of the dump. It is, however, the complete kern.log (I booted from a live-cd now)
2) My SysRq is on my PrintScrn key, should I use some extra modifying key on top of Alt+SysRq+1 ?

See the attached kern.log below. )

The screen was black, but went on, displayed the desktop background with a black rounded rectangle in the middle (maybe the remains of log-out window). So the mouse-pointer responded for a second, then the system did not respond anymore.

I followed DebuggingSystemCrash instructions:
1) the attached kern.log does not, I'm afraid, contain the output of the dump. It is all there is, however (I booted from live-cd after crash)
2) My SysRq is on my PrintScrn key, should I use some extra modifying key on top of Alt+SysRq+1 ?

I'm afraid the system was not 'sufficiently alive', so I also couldn't get output from tty1 or something.

on kern.log: See the crashes on "Mar 31 14:09:43", and "Apr 5 10:48:59".