[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180104201012.GA29474@roeck-us.net>
Date: Thu, 4 Jan 2018 12:10:12 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Thomas Voegtle <tv@...96.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, 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 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 did, but not on Haswell, and not with the same root file system.
It boots fine in qemu on E5-2690 v3.
Do you have a traceback ?
Guenter
> Confused,
>
> Thomas
>
Powered by blists - more mailing lists