All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216625] [regression] GPU lockup on Radeon R7 Kaveri
Date: Wed, 26 Oct 2022 05:40:29 +0000	[thread overview]
Message-ID: <bug-216625-2300-0S0wcgrYwL@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 #2 from Pierre Ossman (pierre-bugzilla@ossman.eu) ---
A bisect will be difficult, given that I can't reproduce it. :/

Any clues from the dmesg that could tell how to provoke it? Or some settings
that could provide more information?

I can try a few version and see if I'm able to narrow it down somewhat. It's
difficult to know when to assume it's a good version as in some cases it has
gone weeks without a lookup...

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

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

  parent reply	other threads:[~2022-10-26  5:40 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 [this message]
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-0S0wcgrYwL@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.