[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r0k9ym0y.ffs@tglx>
Date: Wed, 29 Nov 2023 09:57:33 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>, paul.gortmaker@...driver.com
Cc: bp@...en8.de, linux-kernel@...r.kernel.org, peterz@...radead.org,
richard.purdie@...uxfoundation.org, x86@...nel.org,
Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128
x86/alternative: Rewrite optimize_nops() some]
On Sat, Nov 11 2023 at 12:51, Linux regression tracking wrote:
> [CCing the regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>
>> [Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize_nops() some]] On 30/10/2023 (Mon 20:30) Thomas Gleixner wrote:
>>
>>> On Mon, Oct 30 2023 at 19:24, Thomas Gleixner wrote:
>>
>>> > Can you add "debug-alternative" to the kernel command line and log both
>>> > a working and the non-working kernel output. It's noisy :)
>>> >
>>> > Also do you have a .config and the qemu command line handy?
>>>
>>> Forgot to ask: Does the probkem persist with 6.6 ?
>>
>> My bad, should have mentioned v6.6 and linux-next is impacted. Always a
>> conflict between burying the lead and boring people with details.
>
> 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.
Hmm. I was waiting for the .config file to materialize and for an
eventual analysis of the alternatives debug output....
Powered by blists - more mailing lists