From: "René Herman" <rene.herman@gmail.com>
To: "Jani Nikula" <jani.nikula@linux.intel.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, 4 Aug 2025 18:11:09 +0200 [thread overview]
Message-ID: <9b7e2c8a-e728-4d10-8787-76d4834d1e26@gmail.com> (raw)
In-Reply-To: <2d1e5f5e70d67361e3415dbbd764bfc0a4ff5a17@intel.com>
On 04-08-2025 18:03, Jani Nikula wrote:
> 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.
I'll try and talk the (new to Linux) user with the hardware through
installing a current mainline kernel, but expect this may at least need
to wait for him to be back from that mentioned vacation. Will follow up
if there's anything to report.
Regards,
Rene.
next prev parent reply other threads:[~2025-08-04 16:09 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
2025-08-04 16:11 ` René Herman [this message]
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=9b7e2c8a-e728-4d10-8787-76d4834d1e26@gmail.com \
--to=rene.herman@gmail.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.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.