From: Sasa Dragic <sasa.dragic@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/1] fix RC6p related regression on Sandy Bridge
Date: Mon, 19 Dec 2022 18:29:26 +0100 [thread overview]
Message-ID: <20221219172927.9603-1-sasa.dragic@gmail.com> (raw)
Hi all,
RC6p got re-enabled on Sandy Bridge over time, seemingly by accident
over time, causing graphical glitches and occasional GPU hangs on my
old ThinkPad T420, severity depending on kernel version.
It is a known issue, e.g.:
https://wiki.ubuntu.com/Kernel/PowerManagementRC6
https://www.yoctoproject.org/pipermail/yocto/2012-June/007164.html
It was originally disabled in commit 1c8ecf80fdee ("drm/i915: do not
enable RC6p on Sandy Bridge"), and subsequently re-enabled by
13c5a577b342 ("drm/i915/gt: Select the deepest available parking mode
for rc6"), which seems to focus only on Ivy Bridge.
This patch re-disables RC6p on Sandy Bridge.
I don't know if this issue is fixed otherwise, and I just have a faulty
hardware, but there are few unresolved Sandy Bridge issues floating on
the net, which could be related to this. When disabling RC6p graphics
works flawlessly, as it also works on 4.15 kernel without modifications.
I didn't want to clutter this mail with too much info, so feel free to
ask for details, links or to file bug report if necessary.
Thanks,
Sasa
Sasa Dragic (1):
drm/i915: re-disable RC6p on Sandy Bridge
drivers/gpu/drm/i915/i915_pci.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.37.2
next reply other threads:[~2022-12-19 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 17:29 Sasa Dragic [this message]
2022-12-19 17:29 ` [Intel-gfx] [PATCH 1/1] drm/i915: re-disable RC6p on Sandy Bridge Sasa Dragic
2022-12-20 10:32 ` Ville Syrjälä
2022-12-20 15:50 ` Sasa Dragic
2022-12-21 14:09 ` Rodrigo Vivi
2023-01-17 22:50 ` Ville Syrjälä
2022-12-21 17:40 ` [Intel-gfx] ✓ Fi.CI.BAT: success for fix RC6p related regression " Patchwork
2022-12-21 18:52 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=20221219172927.9603-1-sasa.dragic@gmail.com \
--to=sasa.dragic@gmail.com \
--cc=intel-gfx@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