<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Frequent lock ups for AMD RX 550 graphics card" href="https://bugs.freedesktop.org/show_bug.cgi?id=106671#c36">Comment # 36</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Frequent lock ups for AMD RX 550 graphics card" href="https://bugs.freedesktop.org/show_bug.cgi?id=106671">bug 106671</a> from <a class="email" href="mailto:Alan.W.Irwin1234@gmail.com" title="Alan W. Irwin <Alan.W.Irwin1234@gmail.com>"> Alan W. Irwin</a> <pre>(In reply to fin4478 from <a href="show_bug.cgi?id=106671#c35">comment #35</a>) > To prevent random kernel lock ups with Ryzen, enable RCU_NOCB_CPU in the > kernel configuration and boot the kernel with the rcu_nocbs=0-X command > line parameter. X is the cpu thread count -1. To fix this with bios, set to > Typical Current Idle in the bios Advanced/AMD CBS menu. I was quickly able to verify all you said at <<a href="https://community.amd.com/thread/225795">https://community.amd.com/thread/225795</a>> and <<a href="https://bugzilla.kernel.org/show_bug.cgi?id=196683">https://bugzilla.kernel.org/show_bug.cgi?id=196683</a>>. So it appears all Linux Ryzen owners should be aware of this "idle" issue and take the necessary workarounds, but despite over many months publicizing my Linux Ryzen troubles in a number of different Linux forums (including this bug report) and many different google searches I remained clueless about this bad Linux Ryzen situation until now. So many thanks for being the first to clue me in! It took me a while to figure out how to rebuild the latest Debian Buster kernel (4.18.10) with RCU_NOCB_CPU enabled, but I have done that now and just rebooted with that custom kernel using the rcu_nocbs=0-15 kernel parameter (my Ryzen 7 1700 has 8 cores and 16 threads). So my hopes are high that this step will clean up the lockup issues I have been experiencing when my system was idling at night. But I have also experienced lockups when the system was being used so the rcu_nocbs=0-15 workaround may not be the sole step I have to take to stabilize my Linux Ryzen system.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>