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.
I just rebased to 0.5.1, could you check if that works for you: https://brewweb.devel.redhat.com/taskinfo?taskID=7422119 ?
Also, the original bug report seems to suggest that a firmware upgrade fixes this issue. Is that not the case for you?
Narendra, Jordan, any thoughts on this?
As I understand, this bug seems to be same as bug 1034164. Please correct me if this understanding is wrong. If this bug is same as bug 1034164, BIOS version 2.2.3 has the fix (as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1034164#c69). Please let us know if any additional details are required.
Narendra, yes this looks like bug 1034164. Closing it as a dupe for now. Please reopen if necessary.
*** This bug has been marked as a duplicate of bug 1034164 ***