All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210683] Nasty amdgpu powersave regression Navi14
Date: Tue, 22 Dec 2020 08:29:32 +0000	[thread overview]
Message-ID: <bug-210683-2300-vjvLxEl6Cm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210683-2300@https.bugzilla.kernel.org/>

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

--- Comment #5 from David Mak (david.18.19.21@gmail.com) ---
Created attachment 294289
  --> https://bugzilla.kernel.org/attachment.cgi?id=294289&action=edit
git bisect for Navi 21.

Not sure if I am doing is properly, but I performed a git bisect between 5.9
and 5.10 on drivers/gpu/drm/amd.

Note that none of the supposedly "good" commits actually fixed the issue. I
just mark them as "good" because those commits either cannot modeset to my
monitor's resolution, or the kernel fails to write certain registers to my GPU
and causes my display lose signal and go to standby. So technically the "first
bad commit" is just the first commit that I can boot into SDDM/KDE and can also
reproduce the issue.

Please let me know if there are anything else I can help with. I have a spare
Vega 64 (Vega 10) card lying around, but it has its own memory clock issues as
far as I remember =/

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

You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-12-22  8:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 13:08 [Bug 210683] New: Nasty gpu powersave regression Navi14 bugzilla-daemon
2020-12-14 13:09 ` [Bug 210683] " bugzilla-daemon
2020-12-14 13:15 ` [Bug 210683] Nasty amdgpu " bugzilla-daemon
2020-12-14 13:22 ` bugzilla-daemon
2020-12-14 13:40 ` bugzilla-daemon
2020-12-14 13:41 ` bugzilla-daemon
2020-12-14 18:22 ` bugzilla-daemon
2020-12-20  3:26 ` bugzilla-daemon
2020-12-22  8:29 ` bugzilla-daemon [this message]
2020-12-24 11:25 ` bugzilla-daemon
2020-12-26 16:14 ` bugzilla-daemon
2020-12-26 16:15 ` bugzilla-daemon
2020-12-27 16:24 ` bugzilla-daemon
2020-12-27 16:26 ` bugzilla-daemon
2021-01-16  4:33 ` 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-210683-2300-vjvLxEl6Cm@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.