Red Hat Bugzilla – Bug 459107
[RHEL5.3]: Hang when booting an i386 domU on an i386 HV
Last modified: 2009-01-20 15:07:28 EST
Description of problem:
I was trying to boot a 2.6.18-104 i386 kernel under and i386 HV, and it kept hanging during boot. I bisected it, and found out that it started happening in 2.6.18-98. Bisecting further, I found that this patch is the culprit:
[xen] PVFB probe & suspend fixes
Reverting that patch causes it to boot properly again. Interestingly enough, if I let the guest hang around long enough, it will eventually spew out some softlockup warnings, and even longer, will finally boot. The stack traces from the softlockups look like:
BUG: soft lockup - CPU#0 stuck for 10s! [swapper:0]
Pid: 0, comm: swapper
EIP: 0061:[<c055301b>] CPU: 0
EIP is at input_handler+0x39/0x13a
EFLAGS: 00000212 Not tainted (220.127.116.11 #6)
EAX: 003c4c47 EBX: c0edaba8 ECX: 00000033 EDX: 000007d0
ESI: ed7a2560 EDI: 0c033257 EBP: c0eda000 DS: 007b ES: 007b
CR0: 8005003b CR2: f5305000 CR3: 00f2c000 CR4: 00000660
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This bugzilla has Keywords: Regression.
Since no regressions are allowed between releases,
it is also being proposed as a blocker for this release.
Please resolve ASAP.
+ info->page = (void *)__get_free_page(GFP_KERNEL || __GFP_ZERO);
Oops. That probably wants to be (GFP_KERNEL | GFP_ZERO)
And that is the bug; using | instead of || makes it boot just fine on i386. We
also need to make sure this is not broken upstream.
Upstream is fine, both pvops and XS's 2.6.18.
You can download this test kernel from http://people.redhat.com/dzickus/el5
This bug has been marked for inclusion in the Red Hat Enterprise Linux 5.3
To aid in the development of relevant and accurate release notes, please fill
out the "Release Notes" field above with the following 4 pieces of information:
Cause: What actions or circumstances cause this bug to present.
Consequence: What happens when the bug presents.
Fix: What was done to fix the bug.
Result: What now happens when the actions or circumstances above occur. (NB:
this is not the same as 'the bug doesn't present anymore')
This one shouldn't have a release note; it was introduced, and fixed, during 5.3 beta testing.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.