Comment 480 for bug 1690085
Revision history for this message
|
|
#480 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to OptionalRealName from comment #393)
> There still does not appear to be a single consistent solution to this
> problem and it exists in Ryzen 1xxx and 2xxx series.
Actually, there are several workarounds known to work listed in this thread.
I've been running a stable x1800 using the rcu_nocbs=0-15 fixes noted above for almost a year now.
> This thread is utterly embarrassing for AMD, truly embarrassing.
It's a nuanced hard to troubleshoot bug in a processor + support chipsets with a known workaround which only seems to happen on Linux... not really sure how that is "embarrassing". It sucks, it's new silicon. Welcome to being an early adopter.
Look at Intel's heart-bleed and all the other major security catastrophes they've had in recent history. Stuff happens. I do wish AMD would address it, but they're likely reluctant to bring it up until they have a reliable fix (if it even is a fix on their end)