[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180105154830.GA16369@kroah.com>
Date: Fri, 5 Jan 2018 16:48:30 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Thomas Voegtle <tv@...96.de>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net,
shuahkh@....samsung.com, patches@...nelci.org,
ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
stable@...r.kernel.org
Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review
On Fri, Jan 05, 2018 at 04:25:33PM +0100, Thomas Voegtle wrote:
> On Fri, 5 Jan 2018, Greg Kroah-Hartman wrote:
>
> > On Thu, Jan 04, 2018 at 08:38:23PM +0100, Thomas Voegtle wrote:
> > >
> > > When I start 4.4.110-rc1 on a virtual machine (qemu) init throws a
> > > segfault and the kernel panics (attempted to kill init).
> > > The VM host is a Haswell system.
> > >
> > > The same kernel binary boots fine on a (other) Haswell system.
> > >
> > > I tried:
> > >
> > > 4.4.110-rc1 broken
> > > 4.4.109 ok
> > > 4.9.75-rc1 ok
> > >
> > > All systems are OpenSuSE 42.3 64bit.
> > >
> > > qemu is started only with:
> > > qemu-system-x86_64 -m 2048 -enable-kvm -drive
> > > file=tvsuse,format=raw,if=none,id=virtdisk0 -device
> > > virtio-blk-pci,scsi=off,drive=virtdisk0
> > >
> > > Am I the only one who sees this? Has anyone booted that kernel on qemu?
> >
> > I've now released 4.4.110, which had 4 more patches on top of what
> > 4.4.109-rc1 had in it, that should hopefully resolve these issues.
> >
> > Can you test that and let me know if you still have problems?
>
> It's fixed. I can boot 4.4.110 on qemu without problems so far.
Yeah!!!
> ./test_vsyscall_64 still fails though, like Kees wrote about 4.4.110-rc1
> https://lkml.org/lkml/2018/1/5/123
>
> That's another issue?
Yes it is, that's next up to get resolved.
thanks for testing and letting me know,
greg k-h
Powered by blists - more mailing lists