stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Éric Brunet" <eric.brunet@ens.fr>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
	jouni.hogander@intel.com, jani.nikula@intel.com,
	gregkh@linuxfoundation.org
Subject: Re: Regression on drm/i915, with bisected commit
Date: Thu, 18 May 2023 10:14:30 +0200	[thread overview]
Message-ID: <5681706.DvuYhMxLoT@skaro> (raw)
In-Reply-To: <ZGU56n66OAe0DqN3@intel.com>

Le mercredi 17 mai 2023, 22:32:42 CEST Ville Syrjälä a écrit :
> On Tue, May 16, 2023 at 03:04:53PM +0200, Éric Brunet wrote:
> > Hello all,
> > 
> > I have a HP Elite x360 1049 G9 2-in-1 notebook running fedora 38 with an
> > Adler Lake intel video card.
> > 
> > After upgrading to kernel 6.2.13 (as packaged by fedora), I started seeing
> > severe video glitches made of random pixels in a vertical band occupying
> > about 20% of my screen, on the right. The glitches would happen both with
> > X.org and wayland.
> 
> Please file a bug at https://gitlab.freedesktop.org/drm/intel/issues/new
> boot with "log_buf_len=4M drm.debug=0xe" passed to kernel cmdline, and
> attach the resulting dmesg to the bug.

Thank you for your answer, I have just opened the issue as requested.

https://gitlab.freedesktop.org/drm/intel/-/issues/8480

Éric Brunet



  reply	other threads:[~2023-05-18  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 13:04 Regression on drm/i915, with bisected commit Éric Brunet
2023-05-16 23:51 ` Bagas Sanjaya
2023-05-17  9:21   ` Hogander, Jouni
2023-05-18  7:39   ` Bagas Sanjaya
2023-06-05 11:05   ` Linux regression tracking #update (Thorsten Leemhuis)
2023-05-17 20:32 ` Ville Syrjälä
2023-05-18  8:14   ` Éric Brunet [this message]
2023-05-18 13:31     ` Bagas Sanjaya

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=5681706.DvuYhMxLoT@skaro \
    --to=eric.brunet@ens.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=jani.nikula@intel.com \
    --cc=jouni.hogander@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --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).