Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"Wang, Qingshun" <qingshun.wang@linux.intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: ixgbe probe failure on Proxmox 8
Date: Wed, 14 Feb 2024 21:35:08 +0000	[thread overview]
Message-ID: <F7D2F429-F330-4BAB-8876-196CA639DA76@intel.com> (raw)
In-Reply-To: <20240213235231.GA1235066@bhelgaas>


--
Jesse Brandeburg


> On Feb 13, 2024, at 3:52 PM, Bjorn Helgaas <helgaas@kernel.org> wrote:
> 
> Just a heads-up about an ixgbe probe failure seen with Proxmox 8.  I
> suspect this is a PCI core problem, probably not an ixgbe problem.
> 
> The ixgbe device logs an Advisory Non-Fatal Error and it seems like
> subsequent reads from the device return ~0:
> 
>  pcieport 0000:00:03.1: AER: Corrected error received: 0000:05:00.0

Why does the user or bios configure corrected errors as fatal or requiring a reset? 

Seems like a self inflicted wound. 

>  pci 0000:05:00.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
>  pci 0000:05:00.0:   device [8086:1563] error status/mask=00002000/00000000
>  pci 0000:05:00.0:    [13] NonFatalErr
> 
>  ixgbe 0000:05:00.0: enabling device (0000 -> 0002)
>  ixgbe 0000:05:00.0: Adapter removed
> 
> The user report is at
> https://forum.proxmox.com/threads/proxmox-8-kernel-6-2-16-4-pve-ixgbe-driver-fails-to-load-due-to-pci-device-probing-failure.131203/post-633851.
> 
> I opened a bugzilla with complete dmesg log at
> https://bugzilla.kernel.org/show_bug.cgi?id=218491 with some
> speculation about what might have caused this, e.g., an ACS
> configuration error or something.  It's lame, I know, so this is just
> a shot in the dark.

I’ll look a little more at this tomorrow. I remember lots of inconsistent behaviors around this stuff with early ixgbe and when this PCI capabilities was first enabled. Most of these issues have been resolved since and I haven’t heard of one for a long time. 


> 
> Bjorn
> 

      reply	other threads:[~2024-02-14 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 23:52 ixgbe probe failure on Proxmox 8 Bjorn Helgaas
2024-02-14 21:35 ` Brandeburg, Jesse [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=F7D2F429-F330-4BAB-8876-196CA639DA76@intel.com \
    --to=jesse.brandeburg@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=helgaas@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=qingshun.wang@linux.intel.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