Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753119AbeADTuy (ORCPT + 1 other); Thu, 4 Jan 2018 14:50:54 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:52256 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751952AbeADTuv (ORCPT ); Thu, 4 Jan 2018 14:50:51 -0500 Date: Thu, 4 Jan 2018 20:50:55 +0100 From: Greg Kroah-Hartman To: Thomas Voegtle 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 Message-ID: <20180104195055.GA29809@kroah.com> References: <20180103195056.837404126@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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 Does 4.15-rc6 also work 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? Any chance we can see the panic? There's another error report of this same type of thing on this thread, did you see that? thanks, greg k-h