On Tue, Nov 5, 2019 at 5:31 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Tue, Nov 05, 2019 at 02:33:48PM +0200, Amir Goldstein wrote:
> > On Tue, Nov 5, 2019 at 1:54 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > (sorry if you got this message twice; our SMTP server went bust)
> > >
> > > On Tue, Nov 05, 2019 at 09:14:06AM +0200, Amir Goldstein wrote:
> > > > My kvm-xfstests [1] VM doesn't boot with kmemleak enabled since commit
> > > > c5665868183f ("mm: kmemleak: use the memory pool for early allocations").
> > > >
> > > > There is no console output when running:
> > > >
> > > > $ kvm -boot order=c -net none -machine type=pc,accel=kvm:tcg -cpu host \
> > > >     -drive file=$ROOTFS,if=virtio,snapshot=on -vga none -nographic \
> > > >     -smp 2 -m 2048 -serial mon:stdio --kernel $KERNEL \
> > > >     --append 'root=/dev/vda console=ttyS0,115200'
> > >
> > > This was fixed in 5.4-rc4, see commit 2abd839aa7e6 ("kmemleak: Do not
> > > corrupt the object_list during clean-up").
> >
> > Did not fix my issue.
> > Still not booting with 5.4-rc6.
> > Any other suggestions?
>
> Can you pass an earlyprintk=ttyS0,115200 (if that's the correct x86
> syntax) on the kernel command line? It may print some early messages
> that would help with debugging.
>

Attached.

Thanks,
Amir.