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]
Message-ID: <CAErSpo53L3-feEw0qZvBTmRrY+SXpGrGU6oxZg3wVjH1M8JDXg@mail.gmail.com>
Date:	Fri, 9 Aug 2013 11:18:51 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>
Cc:	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: 3.11-rc4 ixgbevf: endless "Last Request of type 00 to PF Nacked" messages

When I enable VFs via sysfs on an Intel X540-AT, I see an endless stream of

    ixgbevf 0000:08:10.2: Last Request of type 03 to PF Nacked

messages.  This on an HP z420 with the Intel X540-AT in external Magma
PCIe expansion chassis.  No cable is attached to the X540-AT.

ixgbe is built as a module and is auto-loaded during boot, with no VFs
enabled.  The "Last request Nacked" messages start when I enable VFs
with:

    # echo -n 8 > /sys/bus/pci/devices/0000:08:00.0/sriov_numvfs
    ixgbe 0000:08:00.0 eth1: SR-IOV enabled with 8 VFs
    pci 0000:08:10.0: [8086:1515] type 00 class 0x020000
    pci 0000:08:10.2: [8086:1515] type 00 class 0x020000
    ...
    ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network
Driver - version 2.7.12-k
    ...
    ixgbevf 0000:08:10.2: Last Request of type 03 to PF Nacked
    ...

This happens with v3.11-rc4, v3.10, and v3.9, which is as far back as
I checked.  Complete console log and lspci output are here:

    http://helgaas.com/linux/ixgbe/z420.log
    http://helgaas.com/linux/ixgbe/lspci
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ