Description of problem: If we shutdown 2xDomU at once. DomU hungs and causes Dom0 hung The reason is it is not serialize the time service at previous version. This patch serializes the execution of following efi.runtimes. - GetTime - SetTime - GetWakeTime - SetWakeTime Linux/ia64 uses similar spinlocks in the EFI RTC driver. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.shutdown 2xdomU at once. xm shutdown xxx;xm shutdown yyy Actual results: DomU shutdown hung and Dom0 hungs. Expected results: DomU shutdown successfully and Dom0 works properly. Additional info: xen-ia64-unstable:CS12390: e28beea6d228 http://xenbits.xensource.com/ext/xen-ia64-unstable.hg?cs=e28beea6d228
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Updating severity=2 to aree with issue tracker.
Per discussion with Prarit and Aron, Bug 215507: > > Status-NEW, patch available (/xen/arch/ia64/xen/fw_emul.c posted Fri Nov 10 12:03:19 - looks mundane) Should go in RHEL5.0 before RC. Aron please ACK for devel; QA please ACK/NAK.
QE ack for RHEL5.
Escalating for RHEL5.0 consideration per Thursday's RHEL5 meeting. Patch available and all 3 ACKs. Changing status to ASSIGNED.
devel ACK ...however this patch was included in the patchset submitted in bug 210637, so I'm setting this bug to depend on that one, instead of treating this as a separate patch
Moving this to modified based on comment 6.
A package has been built which should help the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.