Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753141AbeADUKS (ORCPT + 1 other); Thu, 4 Jan 2018 15:10:18 -0500 Received: from mail-pl0-f67.google.com ([209.85.160.67]:37658 "EHLO mail-pl0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752964AbeADUKP (ORCPT ); Thu, 4 Jan 2018 15:10:15 -0500 X-Google-Smtp-Source: ACJfBovSUDJ3Odpw89XEyiILY8FLUNfmV7c+/apwB+lRWL9i96x6iRZsUDv3/fDmMA6dRU+/1iehWA== Date: Thu, 4 Jan 2018 12:10:12 -0800 From: Guenter Roeck To: Thomas Voegtle Cc: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, 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: <20180104201012.GA29474@roeck-us.net> 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.5.24 (2015-08-30) 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 > > 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 >