Messages in this thread | | | Subject | Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize_nops() some] | From | Richard Purdie <> | Date | Wed, 22 Nov 2023 14:11:26 +0000 |
| |
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] > > > [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.
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
| |