From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"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,
"Linux Regressions" <regressions@lists.linux.dev>,
"Linux regression tracking" <regressions@leemhuis.info>
Subject: Re: Linux 6.2.1 hits a display driver bug (list_del corruption, ffff88811b4af298->next is NULL)
Date: Wed, 12 Apr 2023 18:00:07 +0700 [thread overview]
Message-ID: <ZDaPNx7WSKeMqgmj@biznet-home.integral.gnuweeb.org> (raw)
In-Reply-To: <ZDYw0vVg7Y1oExJL@debian.me>
On Wed, Apr 12, 2023 at 11:17:22AM +0700, Bagas Sanjaya wrote:
> From gitlab issue above, I don't see any progress on bisection attempt.
> Ammar, have you successfully boot Ubuntu 20.04 with v5.10 kernel and
> test there?
I am still using Ubuntu 22.04. Haven't tried 20.04. I'll arrange time
for it this week.
> Anyway, I'm adding this to regzbot (with tentative commit range):
>
> #regzbot introduced: v5.10..v5.15.103
> #regzbot title: Linux 6.2.1 hits a display driver bug (list_del corruption, ffff88811b4af298->next is NULL)
> #regzbot link: https://gitlab.freedesktop.org/drm/intel/-/issues/8274
>
> (Also Cc: Thorsten)
Not sure why you marked it as regression. I haven't even found the last
good commit. It's possible that it's always broken since the beginning.
--
Ammar Faizi
next prev parent reply other threads:[~2023-04-12 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6feae796-db3f-1135-a607-cfefb0259788@gnuweeb.org>
[not found] ` <ZAGqet3U8AMm4Uf1@debian.me>
[not found] ` <ZAOTU5CRwdEC1lGH@biznet-home.integral.gnuweeb.org>
[not found] ` <87v8jetaik.fsf@intel.com>
[not found] ` <ZAXT1B1GTlmA78Ld@biznet-home.integral.gnuweeb.org>
2023-04-12 4:17 ` Linux 6.2.1 hits a display driver bug (list_del corruption, ffff88811b4af298->next is NULL) Bagas Sanjaya
2023-04-12 11:00 ` Ammar Faizi [this message]
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=ZDaPNx7WSKeMqgmj@biznet-home.integral.gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=airlied@gmail.com \
--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=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manasi.d.navare@intel.com \
--cc=niranjana.vishwanathapura@intel.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=stanislav.lisovskiy@intel.com \
--cc=sumit.semwal@linaro.org \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=tzimmermann@suse.de \
--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).