[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.20.1801042035570.10507@er-systems.de>
Date: Thu, 4 Jan 2018 20:38:23 +0100 (CET)
From: Thomas Voegtle <tv@...96.de>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
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
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?
Confused,
Thomas
Powered by blists - more mailing lists