intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "René Herman" <rene.herman@gmail.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Arun R Murthy" <arun.r.murthy@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Issue or bug concerning DRRS on old i7-4980HQ
Date: Mon, 04 Aug 2025 11:21:23 +0300	[thread overview]
Message-ID: <f9b10acb19bbe19813b4bebd9ac666b397d9c7c0@intel.com> (raw)
In-Reply-To: <d9d1a7ff-307a-4964-98bf-209781ffc6fe@gmail.com>

On Sat, 02 Aug 2025, René Herman <rene.herman@gmail.com> wrote:
> On 01-08-2025 11:19, Jani Nikula wrote:
>
>> On Thu, 31 Jul 2025, René Herman <rene.herman@gmail.com> wrote:
>>> Here's that Ubuntu launchpad bug on freedesktop.org, but including a
>>> possibly interesting fix from 5 months ago in the currently last comment:
>>>
>>> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3441
>> 
>> Might be useful to attach dmesg and VBT to the bug as described at [1].
>
> Just in case: please note the freedesktop.org bug is not our bug but 
> just a 4 year old same one. I also unfortunately don't have the hardware 
> on hand, and it seems the person I am assisting with this can't due to 
> vacation get to it right now.
>
> Although I'm not a graphics/display person, seems to me it's more or 
> less fixed by Arun Murthy (added to the To: list) in the last, still 
> recent-ish comment on that bug?
>
> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3441#note_2803858
>
> I.e., could while working with the person with the hardware not figure 
> out what the point of that i915_drrs_ctl would be if the system 
> immediately enabled it again anyway, so Arun's approach seems to make 
> sense to me.

Hacking debugfs is not a fix, it's a hack.

> This is probably going to be a more common issue soon when these older 
> no-TPM Haswell systems get installed with Linux at the end of Windows 10 
> support.

On the upside, we'll get more people with the hardware to test.


BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-08-04  8:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31  2:49 Issue or bug concerning DRRS on old i7-4980HQ René Herman
2025-07-31 14:01 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2025-07-31 15:07 ` René Herman
2025-08-01  9:19   ` Jani Nikula
2025-08-02 10:36     ` René Herman
2025-08-04  8:21       ` Jani Nikula [this message]
2025-08-04 10:25         ` René Herman
2025-08-04 15:42           ` Jani Nikula
2025-08-04 15:53             ` René Herman
2025-08-04 16:03               ` Jani Nikula
2025-08-04 16:11                 ` René Herman
2025-08-21 19:24                   ` René Herman
2025-08-28  6:10                     ` René Herman
2025-08-04  8:48       ` Murthy, Arun R
2025-08-04 10:12         ` René Herman
2025-08-04 15:46           ` Jani Nikula

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=f9b10acb19bbe19813b4bebd9ac666b397d9c7c0@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rene.herman@gmail.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=ville.syrjala@linux.intel.com \
    /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).