All of 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] GFX10 AMDGPUs can no longer enter idle state after commit. Commit has been pushed to stable branches too.
Date: Mon, 28 Jun 2021 11:10:06 +0000	[thread overview]
Message-ID: <bug-213561-2300-ulC150qlUN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213561-2300@https.bugzilla.kernel.org/>

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

--- Comment #12 from Linux_Chemist (untaintableangel@hotmail.co.uk) ---
(In reply to Marco Scardovi from comment #11)
> Hi everyone, I'm facing same issue here on kernel 5.12.13 with the AMD 3200U
> in an HP-15s laptop. Can you confirm these commits will fix for iGPU too?

Hi Marco, it should do if it's the same issue. Your choice of actions are to
either:

1) Downgrade to or use kernel 5.12.12 (I don't know which distro you're using,
but it should be available somewhere).
2) Build your own kernel from mainline (currently latest version is 5.13 final)
3) Wait until kernel 5.12.14 or later is available for you (at this time, I
don't think it's been released yet).
4) Download and run a kernel from a 3rd party source that doesn't contain these
commits.

As you're on a laptop (and thus probably on battery power), I would just pick
an earlier kernel for now (option 1). 
If you've got grub for your bootloader (for example), just install an earlier
kernel (or use another one if there's one installed), by choosing it at grub's
menu when you boot up, then once you're logged in and confirm you're not on
5.12.13 (confirm with the command 'uname -a'), remove/uninstall 5.12.13 and
then return things to how you like it.

-- 
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-28 11:10 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
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 [this message]
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-ulC150qlUN@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 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.