Comment 634 for bug 1690085
Revision history for this message
|
|
#634 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
I was severely affected a year ago. My system would not run through one rebuild of Gentoo, i.e. it would lock up / hard freeze after only a few hours. I suspect the heavy disk corruption I experienced every time it happened was a direct result of this, and not caused by unrelated hardware defects. The situation was dire and at the time I had to set "typical power idle" in the firmware in order to make the problem go away and the system usable.
Things seem to have improved a lot since then. I now have default firmware settings (i.e. I have NOT set "typical power idle"), I have default Linux idle settings (i.e. I have NOT set idle=halt, idle=mwait or similar), and am I not using any other counter measure anymore. The system is as stable as it gets: No lockups and no unexplainable segfaults. This is since before Linux 5.0 and I strongly suspect the recent firmware update to version 4207 to have fixed the issue.
CPU: AMD Ryzen 5 2400G
Motherboard: Asus ROG STRIX B350-F Gaming
Firmware version: 4207
Linux: 5.0.1 (with Gentoo patches)