Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753189AbeAGKvA (ORCPT + 1 other); Sun, 7 Jan 2018 05:51:00 -0500 Received: from trent.utfs.org ([94.185.90.103]:48980 "EHLO trent.utfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752827AbeAGKu7 (ORCPT ); Sun, 7 Jan 2018 05:50:59 -0500 Date: Sun, 7 Jan 2018 02:50:56 -0800 (PST) From: Christian Kujau To: Tom Hromatka cc: Linus Torvalds , Linux Kernel Mailing List , Dhaval Giani , Greg Kroah-Hartman , Peter Zijlstra , Ingo Molnar , Thomas Gleixner Subject: Re: 4.15-rc6+ hang In-Reply-To: <1e1b4534-b0b4-90c9-479b-29058047f1e9@oracle.com> Message-ID: References: <1e1b4534-b0b4-90c9-479b-29058047f1e9@oracle.com> User-Agent: Alpine 2.21.9 (DEB 223 2017-09-30) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Thu, 4 Jan 2018, Tom Hromatka wrote: > > > [ 0.000000] ------------[ cut here ]------------ > > > [ 0.000000] XSAVE consistency problem, dumping leaves > > I think this is a vbox issue, with virtualbox not exposing all the > > xsave state, so that when the kernel adds up the xsave areas, the end > > result doesn't match what the total size is reported to be. > > It seems probable that this is a VirtualBox issue.  I was > able to boot my exact 4.15-rc6+ kernel in qemu-kvm v1.5.3 > just fine. This was discussed on vbox-dev back in May 2017 (see the whole thread for more details): https://www.virtualbox.org/pipermail/vbox-dev/2017-May/014466.html Does that help? Christian. -- BOFH excuse #9: doppler effect