From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Éric Brunet" <eric.brunet@ens.fr>, stable@vger.kernel.org
Cc: regressions@lists.linux.dev, ville.syrjala@linux.intel.com,
jouni.hogander@intel.com, jani.nikula@intel.com,
gregkh@linuxfoundation.org
Subject: Re: Regression on drm/i915, with bisected commit
Date: Wed, 17 May 2023 06:51:44 +0700 [thread overview]
Message-ID: <ZGQXELf3MSt4oUsR@debian.me> (raw)
In-Reply-To: <3236901.44csPzL39Z@skaro>
[-- Attachment #1: Type: text/plain, Size: 4463 bytes --]
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.
>
> I checked that vanilla 6.2.12 does not have the bug and that both vanilla
> 6.2.13 and vanilla 6.3.2 do have the bug.
>
> I bisected the problem to commit e2b789bc3dc34edc87ffb85634967d24ed351acb (it
> is a one-liner reproduced at the end of this message).
>
> I checked that vanilla 6.3.2 with this commit reverted does not have the bug.
>
Can you also check that its mainline counterpart (e1c71f8f918047c) also
exhibits this regression?
> I am CC-ing every e-mail appearing in this commit , I hope this is ok, and I
> apologize if it is not.
>
> I have filled a fedora bug report about this, see https://bugzilla.redhat.com/
> show_bug.cgi?id=2203549 . You will find there a small video (made with fedora
> kernel 2.6.14) demonstrating the issue.
>
> Some more details:
>
> % sudo lspci -vk -s 00:02.0
> 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP3 GT2 [Iris
> Xe Graphics] (rev 0c) (prog-if 00 [VGA controller])
> DeviceName: Onboard IGD
> Subsystem: Hewlett-Packard Company Device 896d
> Flags: bus master, fast devsel, latency 0, IRQ 143
> Memory at 603c000000 (64-bit, non-prefetchable) [size=16M]
> Memory at 4000000000 (64-bit, prefetchable) [size=256M]
> I/O ports at 3000 [size=64]
> Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
> Capabilities: [40] Vendor Specific Information: Len=0c <?>
> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
> Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
> Capabilities: [d0] Power Management version 2
> Capabilities: [100] Process Address Space ID (PASID)
> Capabilities: [200] Address Translation Service (ATS)
> Capabilities: [300] Page Request Interface (PRI)
> Capabilities: [320] Single Root I/O Virtualization (SR-IOV)
> Kernel driver in use: i915
> Kernel modules: i915
>
> Relevant kernel boot messages: (appart from timestamps, these lines are
> identical for 6.2.12 and 6.2.14):
>
> [ 2.790043] i915 0000:00:02.0: vgaarb: deactivate vga console
> [ 2.790089] i915 0000:00:02.0: [drm] Using Transparent Hugepages
> [ 2.790497] i915 0000:00:02.0: vgaarb: changed VGA decodes:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> [ 2.793812] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/
> adlp_dmc_ver2_16.bin (v2.16)
> [ 2.825058] i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.bin
> version 70.5.1
> [ 2.825061] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version
> 7.9.3
> [ 2.842906] i915 0000:00:02.0: [drm] HuC authenticated
> [ 2.843778] i915 0000:00:02.0: [drm] GuC submission enabled
> [ 2.843779] i915 0000:00:02.0: [drm] GuC SLPC enabled
> [ 2.844200] i915 0000:00:02.0: [drm] GuC RC: enabled
> [ 2.845010] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected
> content support initialized
> [ 3.964766] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor
> 1
> [ 3.968403] ACPI: video: Video Device [GFX0] (multi-head: yes rom: no
> post: no)
> [ 3.968981] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/
> PNP0A08:00/LNXVIDEO:00/input/input18
> [ 3.977892] fbcon: i915drmfb (fb0) is primary device
> [ 3.977899] fbcon: Deferring console take-over
> [ 3.977904] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
> [ 4.026120] i915 0000:00:02.0: [drm] Selective fetch area calculation
> failed in pipe A
>
> Is there anything else I should provide? I am willing to run some tests, of
> course.
>
Anyway, thanks for regression report. I'm adding it to regzbot:
#regzbot ^introduced: e2b789bc3dc34ed
#regzbot title: Selective fetch area calculation regression on Alder Lake card
#regzbot link: https://bugzilla.redhat.com/show_bug.cgi?id=2203549
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-17 0:01 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 [this message]
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
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=ZGQXELf3MSt4oUsR@debian.me \
--to=bagasdotme@gmail.com \
--cc=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 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.