dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213823] Broken power management for amdgpu
Date: Sun, 14 Nov 2021 14:03:47 +0000	[thread overview]
Message-ID: <bug-213823-2300-ShdXU0JFUo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213823-2300@https.bugzilla.kernel.org/>

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

--- Comment #6 from Bruno Pagani (bruno.n.pagani@gmail.com) ---
So while I still don’t have time to setup bisecting, I’m now affected even on
LTS kernel. Also, I’ve been in touch with other users having a similar laptop
(the XPS version instead of the Precision, but still KabyLake-G), and they
don’t seem affected. Thus I’m not sure anymore this is a kernel issue (and
whether BOCO vs ATPX is relevant). Where should I seek for guidance in
understanding why my dGPU stays stuck in D0 instead of going into D3? Is this
or https://gitlab.freedesktop.org/drm/amd and appropriate place?

-- 
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-11-14 14:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 20:03 [Bug 213823] New: Broken power management for amdgpu bugzilla-daemon
2021-07-22 20:04 ` [Bug 213823] " bugzilla-daemon
2021-07-22 20:04 ` bugzilla-daemon
2021-07-22 20:16 ` bugzilla-daemon
2021-07-22 22:06 ` bugzilla-daemon
2021-07-22 22:06 ` bugzilla-daemon
2021-07-22 22:14 ` bugzilla-daemon
2021-11-14 14:03 ` bugzilla-daemon [this message]
2022-10-02 17:42 ` 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-213823-2300-ShdXU0JFUo@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;
as well as URLs for NNTP newsgroup(s).