dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213561] [bisected][regression] AMD GPU can no longer enter idle state after commit
Date: Thu, 24 Jun 2021 14:06:26 +0000	[thread overview]
Message-ID: <bug-213561-2300-GHNwyII6rC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213561-2300@https.bugzilla.kernel.org/>

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

Linux_Chemist (untaintableangel@hotmail.co.uk) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|5.13rc7, 5.12.13            |5.13rc7, 5.12.13, 5.10.46,
                   |                            |5.4.128

--- Comment #6 from Linux_Chemist (untaintableangel@hotmail.co.uk) ---
Commit is also present in kernels 5.10.46 and 5.4.128 (stables) dated 23rd June
2021, so updating info for bug report. Should be a few people hitting this if
they update to the latest kernels this week.

It is also conceivable that a similar bug may happen with gfx9 devices with a
similar commit (I don't know and can't test though) (but that is commit
4cbbe34807938e6e494e535a68d5ff64edac3f20 upstream) that is also in all of these
kernels.
If you don't have a gfx10 device, you should file a separate bug report if that
commit IS causing you an issue (it may not, I'm just guessing based on reports)
- build a linux kernel and do a git bisect to check.

-- 
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:[~2021-06-24 14:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 14:41 [Bug 213561] New: [bisected] AMD GPU can no longer idle state after commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 bugzilla-daemon
2021-06-23 14:41 ` [Bug 213561] " bugzilla-daemon
2021-06-23 14:41 ` [Bug 213561] [bisected] AMD GPU can no longer enter " bugzilla-daemon
2021-06-23 19:15 ` [Bug 213561] [bisected][regression] AMD GPU can no longer enter idle state after commit bugzilla-daemon
2021-06-24  2:57 ` bugzilla-daemon
2021-06-24  3:53 ` bugzilla-daemon
2021-06-24 11:19 ` bugzilla-daemon
2021-06-24 11:48 ` bugzilla-daemon
2021-06-24 12:14 ` bugzilla-daemon
2021-06-24 13:59 ` bugzilla-daemon
2021-06-24 14:06 ` bugzilla-daemon [this message]
2021-06-24 14:07 ` [Bug 213561] [bisected][regression] GFX10 AMDGPUs can no longer enter idle state after commit. Commit has been pushed to stable branches too bugzilla-daemon
2021-06-24 14:18 ` bugzilla-daemon
2021-06-24 18:16 ` bugzilla-daemon
2021-06-24 21:52 ` bugzilla-daemon
2021-06-24 22:53 ` bugzilla-daemon
2021-06-28  7:22 ` bugzilla-daemon
2021-06-28 11:10 ` bugzilla-daemon
2021-06-28 12:06 ` bugzilla-daemon
2021-06-28 16:05 ` bugzilla-daemon
2022-01-20  5:27 ` 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-213561-2300-GHNwyII6rC@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