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 111989] Diagnosing issues with Radeon VII
Date: Tue, 15 Oct 2019 00:42:03 +0000	[thread overview]
Message-ID: <bug-111989-502-BbbjXv0CT3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111989-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from L.S.S. <ragnaros39216@yandex.com> ---
A little update:

Was able to trigger system lockup/hard reset even at low clock speed (at around
1000MHz) last night. It happened when I reapplied the clock settings after it
entered safe clock again, most likely due to that I was also doing something
else on the system (which caused the card to enter safe clock in the first
place).

I still couldn't find a way to increase the log verbosity, but I've tried the
following:

1. Disabling CUs to match that of a Vega 56
(amdgpu.disable_cu=0.0.14,0.0.15,1.0.14,1.0.15,2.0. 14,2.0.15,3.0.14,3.0.15,
found in the Phoronix post[1]). This obviously had no effect as I'm yet to know
which are the real ones I should disable, or if this problem can really be
worked around or not this way.

2. Disabling DC (amdgpu.dc=0): The system won't boot at all.

3. Setting amdgpu.vm_update_mode=3: The system freezes a short while after
startup, but it doesn't hard reset. I can just press the reset button and the
card still works after reboot, without having to do a power cycle.

The system is currently at the latest stable kernel (5.3), but the problem had
existed for quite a while (on all kernel versions, so it must be due to the
hardware itself).

NOTE: On the other hand, the card seems to intermittently cause stutters to the
system possibly with some related but corrected AERs showing in the system log,
but the problem went away after I set the PCIe slot the card is on to GEN2
speed.

[1].
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/1049483-amd-devs-error-ring-gfx-timeout?p=1050232#post1050232

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

[-- Attachment #1.2: Type: text/html, Size: 2732 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-10-15  0:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14  7:27 [Bug 111989] Diagnosing issues with Radeon VII bugzilla-daemon
2019-10-14  7:29 ` bugzilla-daemon
2019-10-15  0:42 ` bugzilla-daemon [this message]
2019-11-19  9:58 ` 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-111989-502-BbbjXv0CT3@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