From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216625] [regression] GPU lockup on Radeon R7 Kaveri
Date: Thu, 09 Mar 2023 06:23:05 +0000 [thread overview]
Message-ID: <bug-216625-2300-QQFAjQUq6R@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216625-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216625
--- Comment #10 from Pierre Ossman (pierre-bugzilla@ossman.eu) ---
I finally got that old version of mesa to build. Unfortunately, the hangs still
happen even with that. :/
> Mar 09 07:18:30 kernel: radeon 0000:00:01.0: ring 3 stalled for more than
> 10028msec
> Mar 09 07:18:30 kernel: radeon 0000:00:01.0: GPU lockup (current fence id
> 0x000000000000fa91 last fence id 0x000000000000fabc on ring 3)
> Mar 09 07:18:31 kernel: radeon 0000:00:01.0: ring 5 stalled for more than
> 10077msec
> Mar 09 07:18:31 kernel: radeon 0000:00:01.0: GPU lockup (current fence id
> 0x00000000000018fb last fence id 0x00000000000018fe on ring 5)
> Mar 09 07:18:31 kernel: radeon 0000:00:01.0: ring 0 stalled for more than
> 10202msec
> ...
What can we do next to pinpoint this?
It seems to fail rather reliably after a suspend/resume. Is there some test
suite I can run to provoke things?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-03-09 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 15:52 [Bug 216625] New: [regression] GPU lockup on Radeon R7 Kaveri bugzilla-daemon
2022-10-25 15:52 ` [Bug 216625] " bugzilla-daemon
2022-10-25 16:24 ` bugzilla-daemon
2022-10-26 5:40 ` bugzilla-daemon
2022-10-26 5:58 ` bugzilla-daemon
2022-10-28 5:40 ` bugzilla-daemon
2022-11-11 6:47 ` bugzilla-daemon
2022-11-11 14:54 ` bugzilla-daemon
2022-12-20 6:53 ` bugzilla-daemon
2022-12-20 15:13 ` bugzilla-daemon
2023-03-06 6:13 ` bugzilla-daemon
2023-03-09 6:23 ` bugzilla-daemon [this message]
2023-03-24 17:52 ` 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-216625-2300-QQFAjQUq6R@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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