Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755023Ab3HIRTP (ORCPT ); Fri, 9 Aug 2013 13:19:15 -0400 Received: from mail-ie0-f179.google.com ([209.85.223.179]:53373 "EHLO mail-ie0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754324Ab3HIRTN (ORCPT ); Fri, 9 Aug 2013 13:19:13 -0400 MIME-Version: 1.0 From: Bjorn Helgaas Date: Fri, 9 Aug 2013 11:18:51 -0600 Message-ID: Subject: 3.11-rc4 ixgbevf: endless "Last Request of type 00 to PF Nacked" messages To: "e1000-devel@lists.sourceforge.net" Cc: "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1301 Lines: 32 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/