From: Scoopta <mlist@scoopta.email>
To: linux-kernel@vger.kernel.org
Subject: Re: RX 5700 XT Issues
Date: Thu, 13 Feb 2020 13:55:57 -0800 [thread overview]
Message-ID: <e63e075c-949b-84ea-d4c2-94510ee4704d@scoopta.email> (raw)
In-Reply-To: <2f5a756d-64d3-800c-499c-8531a6571e3a@scoopta.email>
I've opened a bug report here
https://gitlab.freedesktop.org/drm/amd/issues/1047 about this issue
On 2/12/20 1:34 AM, Scoopta wrote:
> I've attached the dmesg output after the error happens.
>
> On 2/11/20 9:45 PM, Scoopta wrote:
>> My previous statement doesn't appear to be correct syslog just wasn't
>> being flushed despite doing an REISUB. I'm getting a powerplay error.
>> Specifically it seems related to
>> https://gitlab.freedesktop.org/drm/amd/issues/900
>>
>> On 2/11/20 7:13 PM, Scoopta wrote:
>>> When playing demanding games my RX 5700 XT will sometimes just stop. All
>>> my displays turn off but the system stays responsive. Audio keeps
>>> working and I can REISUB no problem, the card just stops. Fans turn off
>>> lm-sensors reports N/A as all information on the sensors and my monitors
>>> go into power save. syslog is also completely quiet. amdgpu doesn't seem
>>> to error or anything so I have no idea how to troubleshoot if this is a
>>> hardware issue or if it's a driver issue. I couldn't find a drm or GPU
>>> specific list so I'm sending it here. I want to be sure it's not a
>>> driver issue or other kernel issue before doing an RMA.
>>>
prev parent reply other threads:[~2020-02-13 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 3:13 RX 5700 XT Issues Scoopta
2020-02-12 5:45 ` Scoopta
2020-02-12 9:34 ` Scoopta
2020-02-13 21:55 ` Scoopta [this message]
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=e63e075c-949b-84ea-d4c2-94510ee4704d@scoopta.email \
--to=mlist@scoopta.email \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).