Comment 36 for bug 1774950

Revision history for this message
Matze (redroach) wrote :

@pHeLiOn: Thanks for putting in the effort! Seeing that this is not resolved yet, I figured that though I'm not a kernel-hacker/sysadmin-guru by a long shot, I'll throw my tidbits in, in the faint hope that someone gets onto the right track.
(For rememberance: Acer Aspire E13, Intel Celeron N2940, 4GB RAM, changed standard HD for a 250G SSD)

1.)
The 'other' bug I mentioned above was (I believe) resolved by adding the statement intel_idle.max_cstate=1 in the grub configuration file. However, my first inquiries into the problem (System freezes, not resolvable by anything (didnt try remote access, though)) pointed me to a potential problem with the SSD HD. Now, I cannot, for the life of me, remember what it was, exactly, but it was something along the lines of Point No. 6 on this site:
http://bernaerts.dyndns.org/linux/74-ubuntu/250-ubuntu-tweaks-ssd
I remembered this because you narrowed it down to some CPU types PLUS SSD, so, maybe there's a hint somewhere.

2.)
In my above Post, I mentioned that my problem was 'fixed' in 18.04 by downgrading the kernel, as mentioned.
Well, it IS fixed in a way, but there remain some oddities - for example: After Boot, the cooling fan is on (running at a moderate pace at first) no matter what, even after a cold boot. It takes putting the system into suspend and out again (which, as mentioned, works now!) so that the fan is turned off completely - and, somewhat worringly, stays off. I've not tested running the system at full power to see if the cooling fan comes on again, when required - so as of now, I take it a bit on 'good faith' that it will :)

These are my further observations - hope it helps somehow!