From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216625] [regression] GPU lockup on Radeon R7 Kaveri
Date: Mon, 06 Mar 2023 06:13:25 +0000 [thread overview]
Message-ID: <bug-216625-2300-ma9ubdFM0L@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 #9 from Pierre Ossman (pierre-bugzilla@ossman.eu) ---
FYI, it seems to have gotten worse since upgrading from
kernel-6.1.8-100.fc36.x86_64 to kernel-6.1.13-100.fc36.x86_64.
It now hangs more arbitrarily, not just when trying to play a video. Having
done a suspend/resume cycle is still a requirement though.
I'm struggling building the old version of mesa that still worked. It isn't
very compatible with newer LLVM, and there is something wrong with Fedora's
packaging of LLVM 12 (that seems to be the matching LLVM version for that old
mesa). I'll need some more effort to get that test up and running.
--
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-06 6:13 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 [this message]
2023-03-09 6:23 ` bugzilla-daemon
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-ma9ubdFM0L@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.