From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Intel GFX Mailing List" <intel-gfx@lists.freedesktop.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
linaro-mm-sig@lists.linaro.org, "Daniel Vetter" <daniel@ffwll.ch>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"David Airlie" <airlied@gmail.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org
Subject: Re: [Intel-gfx] Linux 6.2.1 hits a display driver bug (list_del corruption, ffff88811b4af298->next is NULL)
Date: Mon, 06 Mar 2023 12:54:59 +0200 [thread overview]
Message-ID: <87v8jetaik.fsf@intel.com> (raw)
In-Reply-To: <ZAOTU5CRwdEC1lGH@biznet-home.integral.gnuweeb.org>
On Sun, 05 Mar 2023, Ammar Faizi <ammarfaizi2@gnuweeb.org> wrote:
> On Fri, Mar 03, 2023 at 03:06:18PM +0700, Bagas Sanjaya wrote:
>> Can you please try v6.1?
>
> It's reproducible in v6.1.9. I finally can reliably reproduce it, it
> only happens when I start a VM with qemu.
>
> Specifically adding this device to the qemu instance:
>
> <hostdev mode="subsystem" type="pci" managed="yes">
> <source>
> <address domain="0x0000" bus="0x00" slot="0x02" function="0x0"/>
> </source>
> <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/>
> </hostdev>
>
> And that slot is used by this hardware:
>
> 0000:00:02:0 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics]
>
> Removing it from the qemu instance solves the issue. But it's still a
> kernel bug anyway.
Please file a bug at fdo gitlab:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Intel GFX Mailing List" <intel-gfx@lists.freedesktop.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
"Stanislav Lisovskiy" <stanislav.lisovskiy@intel.com>,
linaro-mm-sig@lists.linaro.org,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Manasi Navare" <manasi.d.navare@intel.com>,
"Niranjana Vishwanathapura" <niranjana.vishwanathapura@intel.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org
Subject: Re: Linux 6.2.1 hits a display driver bug (list_del corruption, ffff88811b4af298->next is NULL)
Date: Mon, 06 Mar 2023 12:54:59 +0200 [thread overview]
Message-ID: <87v8jetaik.fsf@intel.com> (raw)
In-Reply-To: <ZAOTU5CRwdEC1lGH@biznet-home.integral.gnuweeb.org>
On Sun, 05 Mar 2023, Ammar Faizi <ammarfaizi2@gnuweeb.org> wrote:
> On Fri, Mar 03, 2023 at 03:06:18PM +0700, Bagas Sanjaya wrote:
>> Can you please try v6.1?
>
> It's reproducible in v6.1.9. I finally can reliably reproduce it, it
> only happens when I start a VM with qemu.
>
> Specifically adding this device to the qemu instance:
>
> <hostdev mode="subsystem" type="pci" managed="yes">
> <source>
> <address domain="0x0000" bus="0x00" slot="0x02" function="0x0"/>
> </source>
> <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/>
> </hostdev>
>
> And that slot is used by this hardware:
>
> 0000:00:02:0 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics]
>
> Removing it from the qemu instance solves the issue. But it's still a
> kernel bug anyway.
Please file a bug at fdo gitlab:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Intel GFX Mailing List" <intel-gfx@lists.freedesktop.org>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Stanislav Lisovskiy" <stanislav.lisovskiy@intel.com>,
"Niranjana Vishwanathapura" <niranjana.vishwanathapura@intel.com>,
"Manasi Navare" <manasi.d.navare@intel.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: Linux 6.2.1 hits a display driver bug (list_del corruption, ffff88811b4af298->next is NULL)
Date: Mon, 06 Mar 2023 12:54:59 +0200 [thread overview]
Message-ID: <87v8jetaik.fsf@intel.com> (raw)
In-Reply-To: <ZAOTU5CRwdEC1lGH@biznet-home.integral.gnuweeb.org>
On Sun, 05 Mar 2023, Ammar Faizi <ammarfaizi2@gnuweeb.org> wrote:
> On Fri, Mar 03, 2023 at 03:06:18PM +0700, Bagas Sanjaya wrote:
>> Can you please try v6.1?
>
> It's reproducible in v6.1.9. I finally can reliably reproduce it, it
> only happens when I start a VM with qemu.
>
> Specifically adding this device to the qemu instance:
>
> <hostdev mode="subsystem" type="pci" managed="yes">
> <source>
> <address domain="0x0000" bus="0x00" slot="0x02" function="0x0"/>
> </source>
> <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/>
> </hostdev>
>
> And that slot is used by this hardware:
>
> 0000:00:02:0 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics]
>
> Removing it from the qemu instance solves the issue. But it's still a
> kernel bug anyway.
Please file a bug at fdo gitlab:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-06 10:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 20:46 [Intel-gfx] Linux 6.2.1 hits a display driver bug (list_del corruption, ffff88811b4af298->next is NULL) Ammar Faizi
2023-03-02 20:46 ` Ammar Faizi
2023-03-02 20:46 ` Ammar Faizi
2023-03-03 8:06 ` [Intel-gfx] " Bagas Sanjaya
2023-03-03 8:06 ` Bagas Sanjaya
2023-03-03 8:06 ` Bagas Sanjaya
2023-03-04 18:52 ` [Intel-gfx] " Ammar Faizi
2023-03-04 18:52 ` Ammar Faizi
2023-03-04 18:52 ` Ammar Faizi
2023-03-06 10:54 ` Jani Nikula [this message]
2023-03-06 10:54 ` Jani Nikula
2023-03-06 10:54 ` Jani Nikula
2023-03-06 11:51 ` [Intel-gfx] " Ammar Faizi
2023-03-06 11:51 ` Ammar Faizi
2023-03-06 11:51 ` Ammar Faizi
2023-04-12 4:17 ` [Intel-gfx] " Bagas Sanjaya
2023-04-12 4:17 ` Bagas Sanjaya
2023-04-12 4:17 ` Bagas Sanjaya
2023-04-12 11:00 ` [Intel-gfx] " Ammar Faizi
2023-04-12 11:00 ` Ammar Faizi
2023-04-12 11:00 ` Ammar Faizi
2023-04-13 4:16 ` [Intel-gfx] " Bagas Sanjaya
2023-04-13 4:16 ` Bagas Sanjaya
2023-04-13 4:16 ` 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=87v8jetaik.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=ammarfaizi2@gnuweeb.org \
--cc=bagasdotme@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
/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.