All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 28 Aug 2025 08:10:45 +0200	[thread overview]
Message-ID: <d0542c33-e4ce-493b-8e08-78c3b7c3ce43@gmail.com> (raw)
In-Reply-To: <6f55d851-53ac-403b-b2e0-834df94b16bf@gmail.com>

On 21-08-2025 21:24, René Herman wrote:

> We managed to install the 6.16 mainline kernel and generate the 
> requested dmesg and VBT logs, with the requested "drm.debug=0xe 
> log_buf_len=4M ignore_loglevel" kernel parameters. They are attached at
> 
> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3441#note_3064300
> 
> Hope this helps. Many thanks for looking.

Hi all.

Was this useful?

Kind regards,
Rene.

  reply	other threads:[~2025-08-28  6:10 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
2025-08-21 19:24                   ` René Herman
2025-08-28  6:10                     ` René Herman [this message]
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=d0542c33-e4ce-493b-8e08-78c3b7c3ce43@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.