Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:7 as permitted sender) client-ip=2620:137:e000::3:7;
Message-ID: <e49abe2b336ce7534e9a7c82e21df9644f00f3a2.camel@linuxfoundation.org>
Subject: Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128
 x86/alternative: Rewrite optimize_nops() some]
From:   Richard Purdie <richard.purdie@linuxfoundation.org>
To:     Linux regressions mailing list <regressions@lists.linux.dev>,
        paul.gortmaker@windriver.com
Cc:     bp@alien8.de, linux-kernel@vger.kernel.org, peterz@infradead.org,
        tglx@linutronix.de, x86@kernel.org
Date:   Wed, 22 Nov 2023 14:11:26 +0000
In-Reply-To: <0adb772c-e8d2-4444-92b0-00cbfdaf1fac@leemhuis.info>
References: <ZUEgAAGDVqXz2Seo@windriver.com>
         <0adb772c-e8d2-4444-92b0-00cbfdaf1fac@leemhuis.info>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.1-0ubuntu1 
MIME-Version: 1.0
Precedence: bulk

On Sat, 2023-11-11 at 12:51 +0100, Linux regression tracking (Thorsten
Leemhuis) wrote:
> [CCing the regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>=20
> > [Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/altern=
ative: Rewrite optimize_nops() some]] On 30/10/2023 (Mon 20:30) Thomas Glei=
xner wrote:
> >=20
> > > On Mon, Oct 30 2023 at 19:24, Thomas Gleixner wrote:
> >=20
> > > > Can you add "debug-alternative" to the kernel command line and log =
both
> > > > a working and the non-working kernel output. It's noisy :)
> > > >=20
> > > > Also do you have a .config and the qemu command line handy?
> > >=20
> > > Forgot to ask: Does the probkem persist with 6.6 ?
> >=20
> > My bad, should have mentioned v6.6 and linux-next is impacted. Always a
> > conflict between burying the lead and boring people with details.
>=20
> Paul, was this regression ever solved? I wonder as I could not find
> anything with a "Fixes: 6c480f222128 [...]" tag on lore and this thread
> looks stalled.

I didn't see a reply to this. I can confirm the issue is still present
and we're not aware of any fix yet.

Cheers,

Richard