dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106671] Frequent lock ups for AMD RX 550 graphics card
Date: Fri, 07 Sep 2018 22:23:35 +0000	[thread overview]
Message-ID: <bug-106671-502-hNr7LblbWB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106671-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1334 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106671

--- Comment #13 from Alan W. Irwin <Alan.W.Irwin1234@gmail.com> ---
Well, after 1.5 (successful) days with the remote graphics experiment, I
decided instead it made more sense to go after the quicker acting instability
that I have previously experienced in direct graphics mode.  So just now I have
started
a direct graphics experiment after a Debian Testing upgrade which included the
following firmware and mesa changes:

firmware-amd-graphics updated "(20180825+dfsg-1) over (20180518-1)"

mesa updated "(18.1.7-1) over (18.1.6-1)"

In addition for this experiment I installed the  amd64-microcode package
that contains "microcode patches for all AMD AMD64 processors".

Also, as part of this experiment I have continued with the idle=nomwait kernel
parameter as verified by 

irwin@merlin> cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.17.0-3-amd64
root=UUID=1e45a1ee-a5d6-4327-9a7b-2663ffc0b157 ro rootwait quiet idle=nomwait

N.B. note those kernel parameters do not include any amdgpu-related parameters.
 Do you recommend any such parameters for the RX 550 such as amdgpu.dc=1 which
is sometimes recommended for older versions of AMD new-generation graphics
hardware?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2157 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

  parent reply	other threads:[~2018-09-07 22:23 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 [this message]
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
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-hNr7LblbWB@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