Bug 2135966
| Summary: | pciehp cannot detect any slot | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | lingwangneuraleng |
| Component: | kernel | Assignee: | Myron Stowe <mstowe> |
| kernel sub component: | PCI subsystem | QA Contact: | William Gomeringer <wgomerin> |
| Status: | CLOSED MIGRATED | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | Keywords: | MigratedToJIRA |
| Version: | 8.7 | Flags: | pm-rhel:
mirror+
|
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-01 18:13:04 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
lingwangneuraleng
2022-10-19 00:05:56 UTC
For some reason in the new kernel the pcie slots are detected by acpiphp instead of pciehp: ``` [ 0.472092] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.601789] acpiphp: Slot [0] registered [ 0.616053] acpiphp: Slot [0-2] registered [ 0.632062] acpiphp: Slot [0-3] registered [ 0.641026] acpiphp: Slot [0-4] registered [ 0.654095] acpiphp: Slot [0-5] registered [ 0.668644] acpiphp: Slot [0-6] registered [ 0.679036] acpiphp: Slot [0-7] registered [ 0.690992] acpiphp: Slot [0-8] registered [ 0.693592] acpiphp: Slot [0-9] registered ``` In 8.6, acpiphp does not register those slots instead pciehp register them. 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 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. 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. Additional information on creating a Jira account to access the migrated issue can be found here: https://access.redhat.com/articles/7032570 |