Bug 2212780

Summary: backport of the fix for 2122515 to RHEL 9.0
Product: Red Hat Enterprise Linux 9 Reporter: Bernd Finger <bfinger>
Component: kernelAssignee: Myron Stowe <mstowe>
kernel sub component: PCI subsystem QA Contact: William Gomeringer <wgomerin>
Status: CLOSED MIGRATED Docs Contact:
Severity: unspecified    
Priority: unspecified CC: aarnold, peter.stark, ralf.probst, rhandlin
Version: 9.0Keywords: MigratedToJIRA
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-01 18:13:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bernd Finger 2023-06-06 10:51:01 UTC
Description of problem:
Booting a RHEL 9.0 GA ISO image on an x86_64 server with 3 NVME devices fails. The problem and a workaround are described in https://access.redhat.com/solutions/6992307 and the related Red Hat bugzilla bug is 2122515.

The behavior could not be reproduced with kernel-5.14.0-138.el9 (see https://bugzilla.redhat.com/show_bug.cgi?id=2122515#c1). As the RHEL 9.0 GA kernel is 5.14.0-70.13.1.el9_0 and a partner company is running software and hardware certification on RHEL 9.0, a backport is required.

Version-Release number of selected component (if applicable):

How reproducible: always

Steps to Reproduce:
1. Install RHEL 9.0 GA on an x86_64 server with an NVME device

Actual results: The boot fails.

Expected results: The boot succeeds, even without boot parameter intremap=off.

Additional info:

Comment 2 Doug Ledford 2023-08-31 15:50:59 UTC
This bug is scheduled for migration to Jira.  When that happens, this bugzilla issue will be permanently closed with the status MIGRATED and all future interaction on this issue will need to happen in the Jira issue.  The new issue will be part of the RHEL project (a project for Jira only issues, which will sync once, then close the bugzilla issue and all future updates will happen in Jira), not part of the RHELPLAN project (which is part of the automated bugzilla->Jira mirroring and which allows ongoing updates to the bugzilla bug and syncs those updates over to Jira).

For making sure you have access to Jira in order to continue accessing this issue, follow one of the appropriate knowledge base articles:

KB0016394 - https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016394
KB0016694 - https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016694
KB0016774 - https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016774

For general issues with Jira, open a ticket with rh-issues

Comment 3 RHEL Program Management 2023-09-01 18:12:09 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-01 18:13:16 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.

Users watching this BZ may not be automatically added to the Jira ticket.  Be sure to add yourself to the Watchers field in the Jira issue if you desire to continue following this issue.

Comment 5 Doug Ledford 2023-09-08 17:30:47 UTC
Additional information on creating a Jira account to access the migrated issue can be found here:

https://access.redhat.com/articles/7032570