Re: qemu-i386 boot failed on mainline master - no console output

[Greg Kroah-Hartman]

On Wed, Apr 02, 2025 at 02:24:53PM +0530, Naresh Kamboju wrote:
> + Linus
> + Greg KH
> 
> On Wed, 2 Apr 2025 at 14:14, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote:
> >
> > Regressions on qemu-i386 devices boot tests failed with defconfig on
> > the mainline master no console output.
> >
> 
> The qemu-i386 boot failed with no console output and is still happening on
> the latest mainline master branch.
> 
> > First seen on the char-misc-6.15-rc1 merge 25601e85441d ("Merge tag
> > 'char-misc-6.15-rc1' of...)
> >  Good: [08733088b566b58283f0f12fb73f5db6a9a9de30] Merge tag
> > 'rust-fixes-6.15-merge'
> >  Bad:  [91e5bfe317d8f8471fbaa3e70cf66cae1314a516] Merge tag 'dmaengine-6.15-rc1'
> >
> > * qemu-i386
> >  - boot
> >
> > Regression Analysis:
> >  - New regression? Yes
> >  - Reproducibility? Yes
> >
> > Test regression: qemu-i386 boot failed on mainline master
> > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx>
> >
> > Anders bisected this to,
> >   # first bad commit:
> >     [eb0ece16027f8223d5dc9aaf90124f70577bd22a]
> >     Merge tag 'mm-stable-2025-03-30-16-52' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

But this is bisected to the mm merge, not the char-misc merge, right?

And is this just on i386?  Nothing arch-specific in the char-misc merge
that I can see, so I would place bets on mm doing something accidentally
on 32bit systems.

thanks,

greg k-h