From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206475] amdgpu under load drop signal to monitor until hard reset
Date: Sat, 23 May 2020 16:44:13 +0000 [thread overview]
Message-ID: <bug-206475-2300-p6p4DRfMOx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206475-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206475
--- Comment #12 from Andrew Ammerlaan (andrewammerlaan@riseup.net) ---
Created attachment 289247
--> https://bugzilla.kernel.org/attachment.cgi?id=289247&action=edit
messages (reset succesful this time)
And again, twice on the same day :(
But this time:
amdgpu 0000:01:00.0: GPU reset begin!
amdgpu 0000:01:00.0: GPU BACO reset
amdgpu 0000:01:00.0: GPU reset succeeded, trying to resume
This time the reset succeeded, however after restarting X, I got stuck on the
KDE login splash screen. The log (attached) shows some segfaults.
It seems to me that there are two issues here.
1) The GPU is (often) not successfully recovered after a reset, and if it is
recovered successfully segfaults follow in radeonsi_dri.so
2) It goes into a reset in the first place, for no apparent reason
I guess this bug report is mostly about the second issue, why does it go into a
reset? How do I debug this?
It would be great if we could get this fixed, as it is getting kinda annoying.
(This is a brand new GPU, it is not overheating, what is wrong? )
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-23 16:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 20:36 [Bug 206475] New: amdgpu under load drop signal to monitor until hard reset bugzilla-daemon
2020-02-10 13:20 ` [Bug 206475] " bugzilla-daemon
2020-02-10 13:21 ` bugzilla-daemon
2020-02-10 16:39 ` bugzilla-daemon
2020-02-10 16:40 ` bugzilla-daemon
2020-02-10 19:33 ` bugzilla-daemon
2020-02-17 13:23 ` bugzilla-daemon
2020-02-21 21:13 ` bugzilla-daemon
2020-02-24 13:50 ` bugzilla-daemon
2020-02-24 13:52 ` bugzilla-daemon
2020-05-22 12:55 ` bugzilla-daemon
2020-05-23 14:40 ` bugzilla-daemon
2020-05-23 16:44 ` bugzilla-daemon [this message]
2020-06-16 15:48 ` bugzilla-daemon
2020-06-16 16:39 ` bugzilla-daemon
2020-06-24 20:33 ` bugzilla-daemon
2020-06-24 20:41 ` bugzilla-daemon
2020-06-25 9:58 ` bugzilla-daemon
2020-09-15 18:31 ` bugzilla-daemon
2020-09-16 7:52 ` bugzilla-daemon
2021-03-22 9:36 ` bugzilla-daemon
2022-01-06 17:58 ` bugzilla-daemon
2022-01-06 23:44 ` 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-206475-2300-p6p4DRfMOx@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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;
as well as URLs for NNTP newsgroup(s).