dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216625] New: [regression] GPU lockup on Radeon R7 Kaveri
Date: Tue, 25 Oct 2022 15:52:04 +0000	[thread overview]
Message-ID: <bug-216625-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216625

            Bug ID: 216625
           Summary: [regression] GPU lockup on Radeon R7 Kaveri
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.19.16-100.fc35.x86_64
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: pierre-bugzilla@ossman.eu
        Regression: No

Created attachment 303084
  --> https://bugzilla.kernel.org/attachment.cgi?id=303084&action=edit
dmesg since problems began

Ever since I upgraded from Fedora 34 to Fedora 35 I've gotten random GPU
lockups. This machine has otherwise been stable for years.

I don't really know what triggers the issue. I *think* it happens in some cases
when I try to play a video in Firefox, but I'm not completely sure.

Reported here, but Fedora generally don't give any attention to GPU driver
issues:

https://bugzilla.redhat.com/show_bug.cgi?id=2131923

Last working system:

  kernel-5.13.8-100.fc33.x86_64
  libglvnd-1:1.3.3-1.fc34.x86_64
  mesa-libGL-21.1.8-3.fc34.x86_64
  libdrm-2.4.109-1.fc34.x86_64
  xorg-x11-server-Xorg-1.20.14-3.fc34.x86_64

First broken system:

  kernel-5.19.8-100.fc35.x86_64
  libglvnd-1:1.3.4-2.fc35.x86_64
  mesa-libGL-21.3.9-1.fc35.x86_64
  libdrm-2.4.110-1.fc35.x86_64
  xorg-x11-server-Xorg-1.20.14-7.fc35.x86_64

Attached is all kernel logs since the issue started happening. It also includes
a fresh boot from the last good kernel, and a good run with the new kernel.

I think that first run with the new kernel was just a fluke, though. The only
package upgraded after the system upgrade and before the lockups started is
annobin.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-10-25 15:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 15:52 bugzilla-daemon [this message]
2022-10-25 15:52 ` [Bug 216625] [regression] GPU lockup on Radeon R7 Kaveri 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
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@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