Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: "Yury M." <yurypm@arista.com>
Cc: bhelgaas@google.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] PCI/AER: Clear non-fatal errors on AER recovery failure
Date: Wed, 20 May 2026 11:02:12 +0200	[thread overview]
Message-ID: <ag14lCLsYhyssY2v@wunner.de> (raw)
In-Reply-To: <3633b587-5782-4cfa-b967-997de86866bb@arista.com>

On Tue, May 19, 2026 at 05:05:20PM +0100, Yury M. wrote:
> [ 476.224325] pci 0000:46:00.1: AER: can't recover (no error_detected callback)
> [ 476.224333] pci 0000:46:00.2: AER: can't recover (no error_detected callback)
> [ 476.224335] pci 0000:46:00.3: AER: can't recover (no error_detected callback)
> [ 476.224338] pci 0000:46:00.4: AER: can't recover (no error_detected callback)
> [ 476.224371] pcieport 0000:06:07.0: AER: device recovery failed

One more thing, recovery is failing here because those four devices
on bus 46 are unbound.  I've got two patches under development to
allow error recovery for unbound devices.  You may want to try those
and see if error recovery succeeds:

https://github.com/l1k/linux/commits/aer_unbound

Thanks,

Lukas

      parent reply	other threads:[~2026-05-20  9:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 13:23 [PATCH] PCI/AER: Clear non-fatal errors on AER recovery failure Yury Murashka
2026-05-18 20:29 ` Bjorn Helgaas
2026-05-18 20:49   ` Yury M.
2026-05-19  9:53 ` Lukas Wunner
2026-05-19 16:05   ` Yury M.
2026-05-20  8:43     ` Lukas Wunner
2026-05-20 10:00       ` Yury M.
2026-05-20  9:02     ` Lukas Wunner [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=ag14lCLsYhyssY2v@wunner.de \
    --to=lukas@wunner.de \
    --cc=bhelgaas@google.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=oohall@gmail.com \
    --cc=yurypm@arista.com \
    /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