Bug 69491
Summary: | Booting into a guest on Intel Haswell (bare-metal) throws soft lockups [qemu-system-x86:911] | ||
---|---|---|---|
Product: | Virtualization | Reporter: | Kashyap Chamarthy (kashyap.cv) |
Component: | kvm | Assignee: | virtualization_kvm |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | gleb, Robert.Hu |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.14.0-0.rc0.git9.1.fc21 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
Complete stdout of dmesg
Complete stdout of dmidecode Complete stdout of `x86info -a` Successful stderr of `dmesg` on L0 with Kernel 3.14.0-0.rc1.git4.1.fc21.x86_64 |
Description
Kashyap Chamarthy
2014-01-27 09:09:49 UTC
Created attachment 123501 [details]
Complete stdout of dmesg
Created attachment 123511 [details]
Complete stdout of dmidecode
Created attachment 123541 [details]
Complete stdout of `x86info -a`
Downstream bug -- https://bugzilla.redhat.com/show_bug.cgi?id=1058209 We suspect it is caused by same root cause with 69361 https://bugzilla.kernel.org/show_bug.cgi?id=69361 We apply the same patch and test on a Haswell machine, don't have such call trace and boot up successfully. Please have a try on the patch in your environment. Created attachment 125521 [details]
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.
(In reply to Kashyap Chamarthy from comment #6) [. . .] > > 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" I still see this same problem with this Kernel on L0 and L1: 3.14.0-0.rc3.git2.1.fc21.x86_64 This is now fixed with this[1] patch from Paolo. Test result[2]. [1] https://patchwork.kernel.org/patch/3736391/ [2] http://article.gmane.org/gmane.comp.emulators.kvm.devel/119406 |