From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 69491] Booting into a guest on Intel Haswell (bare-metal)
 throws soft lockups [qemu-system-x86:911]
Date: Mon, 10 Feb 2014 14:06:32 +0000
Message-ID: <bug-69491-28872-dQCFz6rlnW@https.bugzilla.kernel.org/>
References: <bug-69491-28872@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.kernel.org ([198.145.19.201]:48235 "EHLO mail.kernel.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751894AbaBJOGh (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 10 Feb 2014 09:06:37 -0500
Received: from mail.kernel.org (localhost [127.0.0.1])
	by mail.kernel.org (Postfix) with ESMTP id 226BE201E4
	for <kvm@vger.kernel.org>; Mon, 10 Feb 2014 14:06:36 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org [172.20.200.51])
	by mail.kernel.org (Postfix) with ESMTP id 9733E201B6
	for <kvm@vger.kernel.org>; Mon, 10 Feb 2014 14:06:34 +0000 (UTC)
In-Reply-To: <bug-69491-28872@https.bugzilla.kernel.org/>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

https://bugzilla.kernel.org/show_bug.cgi?id=69491

--- Comment #6 from Kashyap Chamarthy <kashyap.cv@gmail.com> ---
Created attachment 125521
  --> https://bugzilla.kernel.org/attachment.cgi?id=125521&action=edit
Successful stderr of `dmesg` on L0 with Kernel 3.14.0-0.rc1.git4.1.fc21.x86_64

I just tested with this Kernel 3.14.0-0.rc1.git4.1.fc21.x86_64 my bare-metal,
booted L1 (running: 3.14.0-0.rc1.git4.1.fc21.x86_64) and L2 ( running
3.11.10-301.fc20.x86_64')

Couple of observations
----------------------

  - I don't see the soft lockups any more on host
  - L2 is just stuck on:

      Booting `Fedora, with Linux 3.11.10-301.fc20.x86_64'

    when booted over a serial console. I tried booting into single 
    level, it's just stuck there, attempting to "Booting a command list"

  - To isolate the problem Kernel, I also tried:
      - Shutdown L2; Booting L1 into 3.14.0-0.rc1.git1.1.fc21.x86_64;
        Start L2 with 3.11.10-301.fc20.x86_64 -- stuck on boot.

        Repeated the above test with booting L1 into 
        3.12.8-300.fc20.x86_64, and starting L2 results -- stuck on
        boot.

    So, from the above symptoms, I'm inferring the problem appears to be 
    with current L0 Kernel (3.14.0-0.rc1.git4.1). Because
    booting it into its older Kernel (kernel-3.12.8-300.fc20.x86_64),
    brings up L2 successfully

I'm yet to investigate further here.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.