Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
commit 8a22b9996b001c88f2bfb54c6de6a05fc39e177a
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge>
Date: Mon Jul 12 11:49:59 2010 -0700
xen: drop xen_sched_clock in favour of using plain wallclock time
This upstream patch was found while doing analysis for bug 709856. While it's unclear that this patch will resolve any other issues (now that we've already implemented a fix bug 709856). We should backport it and give it some good testing, as it may.
Comment 2RHEL Program Management
2011-06-07 08:21:12 UTC
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 release.
Created attachment 521811[details]
script to reproduce the defect
Verified with kernel-2.6.32-193.el6.
Reproduced the defect with the script provided in
http://comments.gmane.org/gmane.comp.emulators.xen.devel/86173 with minor update.
Boot up RHEL6.1 GA x86_64 PV guest with 4 vcpus (host processor : Intel Xeon E7- 4850), and ran the attached script, it got large value of user or sys， like:
# time perl test.pl
[...]
Files=300, Tests=900, 31 wallclock secs ( 2.25 usr 4.65 sys + 6148914822.77 cusr 12297829458.52 csys = 18446744288.19 CPU)
Result: PASS
real 0m31.337s
user 0m0.001s
sys 204963824m23.408s
After update guest kernel to kernel-2.6.32-193.el6, ran the attached script for several times, the results looks reasonable:
# time perl test.pl
[...]
Files=300, Tests=900, 32 wallclock secs ( 2.31 usr 4.55 sys + 7.14 cusr 29.03 csys = 43.03 CPU)
Result: PASS
real 0m32.446s
user 0m9.985s
sys 0m33.772s
So change bug to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2011-1530.html
commit 8a22b9996b001c88f2bfb54c6de6a05fc39e177a Author: Jeremy Fitzhardinge <jeremy.fitzhardinge> Date: Mon Jul 12 11:49:59 2010 -0700 xen: drop xen_sched_clock in favour of using plain wallclock time This upstream patch was found while doing analysis for bug 709856. While it's unclear that this patch will resolve any other issues (now that we've already implemented a fix bug 709856). We should backport it and give it some good testing, as it may.