netdev - ixgbe probe failure on Proxmox 8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date: Tue, 13 Feb 2024 17:52:31 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: "Wang, Qingshun" <qingshun.wang@...ux.intel.com>,
	intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
	linux-pci@...r.kernel.org
Subject: ixgbe probe failure on Proxmox 8

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
  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.

Bjorn