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.
------- Comment From linuxram.com 2011-04-20 16:04 EDT-------
This is a blocker bug. It ***cannot be deferred**** to 6.2 since it is a key feature targeted for 6.1.
BTW: the problem does not exist with upstream kernel. We are in the process of identifying the patch that fixes the problem.
RP
------- Comment From linuxram.com 2011-04-25 21:55 EDT-------
We, John and myself, started diving deeper to narrow down the patch that fixed the problem upstream. After some 25-30 different iterations with incremental changes, git-bisects, mix-and-match of upstream driver with rc4 kernels etc, suddenly the problem disappeared. We can neither reproduce the problem on rc2 nor on rc4....... We are now scratching our heads to discover a theory that can explain this mystery...
Stay tuned. BTW: I have no reason to say this bug as a blocker any more.
Comment 14RHEL Program Management
2011-10-07 15:31:05 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
------- Comment From whetzel.com 2011-10-12 11:39 EDT-------
This bug was closed on the IBM side due to our inability to reproduce the issue after multiple attempts.