All of lore.kernel.org
 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 19:03:06 +0300	[thread overview]
Message-ID: <2d1e5f5e70d67361e3415dbbd764bfc0a4ff5a17@intel.com> (raw)
In-Reply-To: <6020c152-9de5-40cc-aedf-7024df45d27c@gmail.com>

On Mon, 04 Aug 2025, René Herman <rene.herman@gmail.com> wrote:
> On 04-08-2025 17:42, Jani Nikula wrote:
>
>> On Mon, 04 Aug 2025, René Herman <rene.herman@gmail.com> wrote:
>
>> All I'm saying is that any fix must not depend on the user having to use
>> a debugfs or a module parameter. It needs to work out of the box.
>
> Makes sense to me. Now, while repeating me being clueless about this 
> code and even technology outright, I've wondered if the thing to do 
> might even just be refusing to enable/use DRRS on this old Haswell-era 
> hardware
>
> Probably not a theoretically/technically sound/interesting  plan -- but 
> it sure would solve things for both me/us and the Ubuntu/freedesktop.org 
> bug-reporter, and frankly, I don't think anyone on a system like that in 
> 2025 would know or care in the first place. They just very much mind the 
> flickering...
>
> Maybe stupid; maybe regresses a ton of Haswell-era systems on which it 
> does work fine. No idea...

There's been a bunch of updates on DRRS in the past year, and I have yet
to see a dmesg with debugs enabled reproducing the issue on a recent
kernel. We need data before doing anything else. The discussion in this
thread is not actionable. For all I know the issue could've been fixed
already.

BR,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-08-04 16:03 UTC|newest]

Thread overview: 17+ 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
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 [this message]
2025-08-04 16:11                 ` René Herman
2025-08-21 19:24                   ` René Herman
2025-08-28  6:10                     ` René Herman
2025-09-09 12:53                       ` 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=2d1e5f5e70d67361e3415dbbd764bfc0a4ff5a17@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 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.