From: Hans Zhang <18255117159@163.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: bhelgaas@google.com, tglx@linutronix.de, kw@linux.com,
mahesh@linux.ibm.com, oohall@gmail.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/4] pci: implement "pci=aer_panic"
Date: Fri, 23 May 2025 00:01:29 +0800 [thread overview]
Message-ID: <403949d7-7c36-4b9a-a079-60a5aa985dd1@163.com> (raw)
In-Reply-To: <e2iu7w3sn7m4zwo6ork2mbfjcfixo5jn5ydshkefezsgtquvh6@kjdvxgiapbjj>
On 2025/5/22 19:47, Manivannan Sadhasivam wrote:
> On Sat, May 17, 2025 at 12:55:14AM +0800, 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.
>>
>> 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.
>>
>
> You should not panic the kernel when a PCI error occurs (even if it is a fatal
> one). You should instead try to reset the root complex. For that you need this
> series that got merged recently:
> https://lore.kernel.org/all/20250508-pcie-reset-slot-v4-0-7050093e2b50@linaro.org
>
> PS: You need to populate the slot_reset callback in your controller driver to
> reset the controller in the event of a fatal AER error or link down.
Dear Mani,
Thank you for your reply. I will take a look at the submission record
you provided.
Best regards,
Hans
prev parent reply other threads:[~2025-05-22 16:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 16:55 Hans Zhang
2025-05-16 16:55 ` [PATCH 1/4] " Hans Zhang
2025-05-16 16:55 ` [PATCH 2/4] PCI/AER: Introduce aer_panic kernel command-line option Hans Zhang
2025-05-16 16:55 ` [PATCH 3/4] PCI/AER: Expose AER panic state via pci_aer_panic_enabled() Hans Zhang
2025-05-17 4:07 ` Sathyanarayanan Kuppuswamy
2025-05-19 14:03 ` Hans Zhang
2025-05-16 16:55 ` [PATCH 4/4] PCI/AER: Trigger kernel panic on recovery failure if aer_panic is set Hans Zhang
2025-05-16 18:10 ` [PATCH 0/4] pci: implement "pci=aer_panic" Sathyanarayanan Kuppuswamy
2025-05-19 14:21 ` Hans Zhang
2025-05-19 14:39 ` Hans Zhang
2025-05-19 14:41 ` Hans Zhang
2025-05-20 16:09 ` Sathyanarayanan Kuppuswamy
2025-05-21 14:54 ` Hans Zhang
2025-05-21 16:17 ` Sathyanarayanan Kuppuswamy
2025-05-22 9:33 ` Hans Zhang
2025-05-19 22:03 ` Bjorn Helgaas
2025-05-20 15:11 ` Hans Zhang
2025-05-22 11:47 ` Manivannan Sadhasivam
2025-05-22 16:01 ` Hans Zhang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403949d7-7c36-4b9a-a079-60a5aa985dd1@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=oohall@gmail.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®