Registered Member
|
Hello!
My Kubuntu18.04.1 machine fatally crashes at random times. Computer stays on (can hear the fan running), display/screen black and doesn't 'wake' after keyboard press, keyboard locks up (caps lock light not toggling), mouse non-responsive, power button does nothing. This happens at random intervals during gaming, internet browser use, no use at all (even when just sitting at the login screen). At first I thought it was the CPU/GPUs over-heating, so I began monitoring them, but it happens when they're both hot and 'cold'. Possibly my GPUs/CPU aren't fully-supported, and randomly crash when doing specific registering jobs, etc. I can recreate the behaviour/symptoms by suspending the system to RAM. It refuses to wake, and the same display/keyboard/mouse symptoms show. Syslog shows different issues, depending on if the bug/crash happens during a RAM suspension, or during a random crash. If I suspend to RAM, it doesn't show errors (simply says "starting suspend to ram..." etc. If it's a crash, syslog has some error output (attached below). The weird thing is that this happens randomly when I'm actively and non-actively using the system (non-actively would probably be due to the computer going to 'sleep' via suspend to RAM after a certain amount of time). I've attached what syslog spits out just before the random crash, and when I boot kubuntu back up. Also attached the syslog when the system is manually suspended to RAM. Same symptoms, different syslog output. The crash syslog is most likely the most telling/is of most importance. Nothing seems harmful in syslog just before suspending to RAM. The system stops logging due to the suspension, but seems to keep logging once the screen goes black on a random crash, so that probably means it's some kind of driver failure instead of a kernel panic or something? I think the suspension not waking and the random crash are two separate, but very similar issues. I have a feeling there's just little support for my RAM/GPU/CPU/Motherboard. I've also attached my system profile. If you need more info, let me know. Am going to try out Crash Dump: https://wiki.ubuntu.com/Kernel/CrashdumpRecipe EDIT: Tried it. No dump occurred! I'm guessing the system goes into some sort of RAM suspension, which wouldn't be seen as a crash, then it just never comes back out... and shows very little signs of life. Almost like a coma. Maybe the motherboard or bus controllers or something get deactivated and never reactivate. There are other .crash files in there involving kde, but I can't figure out how to debug them. I've downloaded the appropriate vmlinux debug file, and use apport-unpack to get the CoreDump, but crash comes back saying the CoreDump doesn't match the vmlinux. Anyways, hopefully someone will have some insight into this, or will be able to point me in the direction of where to make this known to some developers! Brief Profile Mac Pro Late 2013 - https://support.apple.com/kb/SP697?locale=en_US Weird, I know, but I've also got macOS and Windows installed for a triple-boot setup. Super fun, and testing its capabilities! Processor - Intel Xeon E5 with 25MB L3 cache and Turbo Boost up to 3.9GHz - 3.0GHz 8-Core Memory - DDR3 ECC memory 3.0GHz 8-Core 64GB (four 16GB) Graphics - Dual AMD FirePro D300 graphics processors with 2GB of GDDR5 VRAM each - 3.7GHz Quad-Core Begin paste dump, as I can't seem to attach files to my post! Profile Mac Pro Late 2013 - https://support.apple.com/kb/SP697?locale=en_US Weird, I know, but I've also got macOS and Windows installed for a triple-boot setup. Super fun, and testing its capabilities! Processor - Intel Xeon E5 with 25MB L3 cache and Turbo Boost up to 3.9GHz - 3.0GHz 8-Core Memory - DDR3 ECC memory 3.0GHz 8-Core 64GB (four 16GB) Graphics - Dual AMD FirePro D300 graphics processors with 2GB of GDDR5 VRAM each - 3.7GHz Quad-Core System profile using "System Profiler and Benchmark" on Kubuntu Discover
Syslog Events Random Crash Syslog - Glaring errors here. I think I even cut off it's logging after a couple of minutes of it being black by hard resetting. Next time I'll let it run longer.
Suspending to RAM syslog - Less glaring, doesn't log any errors after it thinks it's successfully suspended
|
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]