From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106671] Frequent lock ups for AMD RX 550 graphics card
Date: Thu, 15 Nov 2018 02:51:29 +0000 [thread overview]
Message-ID: <bug-106671-502-n9bdqs6LtY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106671-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1674 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #36 from Alan W. Irwin <Alan.W.Irwin1234@gmail.com> ---
(In reply to fin4478 from comment #35)
> 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
<https://community.amd.com/thread/225795> and
<https://bugzilla.kernel.org/show_bug.cgi?id=196683>. 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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2682 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-11-15 2:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106671-502@http.bugs.freedesktop.org/>
2018-05-28 8:47 ` [Bug 106671] Frequent lock ups for AMD RX 550 graphics card bugzilla-daemon
2018-05-28 18:07 ` bugzilla-daemon
2018-05-28 18:08 ` bugzilla-daemon
2018-05-28 18:32 ` bugzilla-daemon
2018-06-02 16:51 ` bugzilla-daemon
2018-06-02 16:54 ` bugzilla-daemon
2018-08-29 23:25 ` bugzilla-daemon
2018-09-04 19:26 ` bugzilla-daemon
2018-09-04 19:27 ` bugzilla-daemon
2018-09-05 7:37 ` bugzilla-daemon
2018-09-06 1:26 ` bugzilla-daemon
2018-09-06 6:56 ` bugzilla-daemon
2018-09-07 22:23 ` bugzilla-daemon
2018-09-07 22:36 ` bugzilla-daemon
2018-09-14 23:44 ` bugzilla-daemon
2018-09-15 0:04 ` bugzilla-daemon
2018-09-15 0:52 ` bugzilla-daemon
2018-09-24 4:44 ` bugzilla-daemon
2018-09-24 5:21 ` bugzilla-daemon
2018-09-24 5:34 ` bugzilla-daemon
2018-09-24 19:35 ` bugzilla-daemon
2018-09-24 19:58 ` bugzilla-daemon
2018-10-04 5:53 ` bugzilla-daemon
2018-10-05 1:39 ` bugzilla-daemon
2018-10-05 8:35 ` bugzilla-daemon
2018-10-05 8:40 ` bugzilla-daemon
2018-10-05 9:32 ` bugzilla-daemon
2018-10-05 9:59 ` bugzilla-daemon
2018-10-06 0:32 ` bugzilla-daemon
2018-10-17 21:28 ` bugzilla-daemon
2018-10-17 21:54 ` bugzilla-daemon
2018-10-21 5:58 ` bugzilla-daemon
2018-10-21 6:20 ` bugzilla-daemon
2018-11-04 5:56 ` bugzilla-daemon
2018-11-04 6:40 ` bugzilla-daemon
2018-11-10 8:38 ` bugzilla-daemon
2018-11-15 2:51 ` bugzilla-daemon [this message]
2019-09-25 18:03 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-106671-502-n9bdqs6LtY@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox