[PATCH 0/4] pci: implement "pci=aer_panic"
Hans Zhang
18255117159 at 163.com
Tue May 20 00:21:12 AEST 2025
On 2025/5/17 02:10, Sathyanarayanan Kuppuswamy wrote:
>
> On 5/16/25 9:55 AM, Hans Zhang wrote:
>> The following series introduces a new kernel command-line option
>> aer_panic
>> to enhance error handling for PCIe Advanced Error Reporting (AER) in
>> mission-critical environments. This feature ensures deterministic recover
>> from fatal PCIe errors by triggering a controlled kernel panic when
>> device
>> recovery fails, avoiding indefinite system hangs.
>
> Why would a device recovery failure lead to a system hang? Worst case
> that device may not be accessible, right? Any real use case?
>
Dear Sathyanarayanan,
Due to Synopsys and Cadence PCIe IP, their AER interrupts are usually
SPI interrupts, not INTx/MSI/MSIx interrupts. (Some customers will
design it as an MSI/MSIx interrupt, e.g.: RK3588, but not all customers
have designed it this way.) For example, when many mobile phone SoCs of
Qualcomm handle AER interrupts and there is a link down, that is, a
fatal problem occurs in the current PCIe physical link, the system
cannot recover. At this point, a system restart is needed to solve the
problem.
And our company design of SOC: http://radxa.com/products/orion/o6/, it
has 5 road PCIe port.
There is also the same problem. If there is a problem with one of the
PCIe ports, it will cause the entire system to hang. So I hope linux OS
can offer an option that enables SOC manufacturers to choose to restart
the system in case of fatal hardware errors occurring in PCIe.
There are also products such as mobile phones and tablets. We don't
want to wait until the battery is completely used up before restarting them.
For the specific code of Qualcomm, please refer to the email I sent.
Best regards,
Hans
>>
>> Problem Statement
>> In systems where unresolved PCIe errors (e.g., bus hangs) occur,
>> traditional error recovery mechanisms may leave the system unresponsive
>> indefinitely. This is unacceptable for high-availability environment
>> requiring prompt recovery via reboot.
>>
>> Solution
>> The aer_panic option forces a kernel panic on unrecoverable AER errors.
>> This bypasses prolonged recovery attempts and ensures immediate reboot.
>>
>> Patch Summary:
>> Documentation Update: Adds aer_panic to kernel-parameters.txt, explaining
>> its purpose and usage.
>>
>> Command-Line Handling: Implements pci=aer_panic parsing and state
>> management in PCI core.
>>
>> State Exposure: Introduces pci_aer_panic_enabled() to check if the panic
>> mode is active.
>>
>> Panic Trigger: Modifies recovery logic to panic the system when recovery
>> fails and aer_panic is enabled.
>>
>> Impact
>> Controlled Recovery: Reduces downtime by replacing hangs with immediate
>> reboots.
>>
>> Optional: Enabled via pci=aer_panic; no default behavior change.
>>
>> Dependency: Requires CONFIG_PCIEAER.
>>
>> For example, in mobile phones and tablets, when there is a problem with
>> the PCIe link and it cannot be restored, it is expected to provide an
>> alternative method to make the system panic without waiting for the
>> battery power to be completely exhausted before restarting the system.
>>
>> ---
>> For example, the sm8250 and sm8350 of qcom will panic and restart the
>> system when they are linked down.
>>
>> https://github.com/DOITfit/xiaomi_kernel_sm8250/blob/d42aa408e8cef14f4ec006554fac67ef80b86d0d/drivers/pci/controller/pci-msm.c#L5440
>>
>> https://github.com/OnePlusOSS/android_kernel_oneplus_sm8350/blob/13ca08fdf0979fdd61d5e8991661874bb2d19150/drivers/net/wireless/cnss2/pci.c#L950
>>
>>
>> Since the design schemes of each SOC manufacturer are different, the AXI
>> and other buses connected by PCIe do not have a design to prevent
>> hanging.
>> Once a FATAL error occurs in the PCIe link and cannot be restored, the
>> system needs to be restarted.
>>
>>
>> Dear Mani,
>>
>> I wonder if you know how other SoCs of qcom handle FATAL errors that
>> occur
>> in PCIe link.
>> ---
>>
>> Hans Zhang (4):
>> pci: implement "pci=aer_panic"
>> PCI/AER: Introduce aer_panic kernel command-line option
>> PCI/AER: Expose AER panic state via pci_aer_panic_enabled()
>> PCI/AER: Trigger kernel panic on recovery failure if aer_panic is set
>>
>> .../admin-guide/kernel-parameters.txt | 7 +++++++
>> drivers/pci/pci.c | 2 ++
>> drivers/pci/pci.h | 4 ++++
>> drivers/pci/pcie/aer.c | 18 ++++++++++++++++++
>> drivers/pci/pcie/err.c | 8 ++++++--
>> 5 files changed, 37 insertions(+), 2 deletions(-)
>>
>>
>> base-commit: fee3e843b309444f48157e2188efa6818bae85cf
>> prerequisite-patch-id: 299f33d3618e246cd7c04de10e591ace2d0116e6
>> prerequisite-patch-id: 482ad0609459a7654a4100cdc9f9aa4b671be50b
>
More information about the Linuxppc-dev
mailing list