Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752848AbeADToP (ORCPT + 1 other); Thu, 4 Jan 2018 14:44:15 -0500 Received: from er-systems.de ([148.251.68.21]:32942 "EHLO er-systems.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751829AbeADToN (ORCPT ); Thu, 4 Jan 2018 14:44:13 -0500 X-Greylist: delayed 345 seconds by postgrey-1.27 at vger.kernel.org; Thu, 04 Jan 2018 14:44:13 EST Date: Thu, 4 Jan 2018 20:38:23 +0100 (CET) From: Thomas Voegtle X-X-Sender: thomas@er-systems.de To: Greg Kroah-Hartman cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuahkh@osg.samsung.com, patches@kernelci.org, ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org, stable@vger.kernel.org Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review In-Reply-To: <20180103195056.837404126@linuxfoundation.org> Message-ID: References: <20180103195056.837404126@linuxfoundation.org> User-Agent: Alpine 2.20 (LSU 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Virus-Checker-Version: clamassassin 1.2.4 with clamdscan / ClamAV 0.99.2/24191/Thu Jan 4 14:15:17 2018 signatures . Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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