All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.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	[thread overview]
Message-ID: <bug-69491-28872-dQCFz6rlnW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-69491-28872@https.bugzilla.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.

  parent reply	other threads:[~2014-02-10 14:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27  9:09 [Bug 69491] New: Booting into Intel Haswell (baremetal) crashes with soft lockup [qemu-system-x86:911] bugzilla-daemon
2014-01-27  9:19 ` [Bug 69491] " bugzilla-daemon
2014-01-27  9:20 ` bugzilla-daemon
2014-01-27  9:31 ` [Bug 69491] Booting into a guest on Intel Haswell (bare-metal) throws soft lockups [qemu-system-x86:911] bugzilla-daemon
2014-01-27  9:37 ` bugzilla-daemon
2014-01-31 16:11 ` bugzilla-daemon
2014-02-10  9:23 ` bugzilla-daemon
2014-02-10 14:06 ` bugzilla-daemon [this message]
2014-02-26 20:32 ` bugzilla-daemon
2014-02-28  6:01 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-69491-28872-dQCFz6rlnW@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.