Comment 13 for bug 1328708

I'm a little unclear as to what you'd like me to do with DebuggingKernelSuspend. The system crashes are not deterministic--they happen about once a week at my current use rate. So, I can't make them happen. My last crash was last night, but I had to hard reboot 4 times before I had a functioning system. The first time was to restart after the crash, the last 3 times were because the system froze as it tried to load KDE. On the last reboot, KDE came back, so it's on this reboot that I'm collecting data.

As far as I can tell, the DebuggingKernelSuspend document suggests obtaining the two pieces of output I've attached. There are no instances of "hash matches" in the enclosed dmesg output.

Anyway, hope this helps. If there's anything else I can do, let me know. Incidentally, I told the system to report bugs (these appeared in dialog boxes on reboot), but the usual apport password authentication and other dialogs never came up, so I don't know whether the bug reports were sent (probably not).

BTW, I can't make sense out of what DebuggingKernelSuspend is saying about the clock. There don't seem to be any commands listed that make use of that.

Peter