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.

Description of problem:
According to MS requirements for WHQL certifications for the next version of Windows Server, PCIe devices must support AER:
>>>
“Device.DevFund.Server.PCI.PCIAER - Windows Server PCI Express devices are required to support Advanced Error Reporting [AER] as defined in PCI Express Base Specification version 2.1.”
Description

See Tables 6-2, 6-3, 6-4, and 6-5 of the PCI Specification on how errors are detected in hardware, the default severity of the error, and the expected action taken by the agent which detects the error with regards to error reporting and logging.
All three methods of error reporting; completion status, error messages, error forwarding\data poisoning. Completion status enables the Requester to associate an error with a specific Request.

Error messages indicate if the problem is correctable or not, and fatal or not
Error forwarding\data poisoning can help determine if a particular Switch along the path poisoned the TLP
>>>
https://go.microsoft.com/fwlink/?linkid=2027110 (WHCP-Components-Peripherals-Specification-1809.pdf file, page 169).


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Closing this bz to replace with a RHEL-AV bz - https://bugzilla.redhat.com/show_bug.cgi?id=1878465

*** This bug has been marked as a duplicate of bug 1878465 ***