Re: [E1000-devel] 3.11-rc4 ixgbevf: endless "Last Request of type 00to PF Nacked" messages

[Bjorn Helgaas]

On Tue, Aug 13, 2013 at 3:54 PM, Skidmore, Donald C
<donald.c.skidmore@xxxxxxxxx> wrote:

> We were unable to recreate your failure here locally so I have some additional questions.  First off you mentioned it was failing as far back as v3.9, was it ever working for you?  If so bisecting would be really helpful as I mentioned we have been unable to cause the failure in house.

I'm not aware of any working version.  I'm exercising in the sysfs
SR-IOV configuration, which I think appeared in v3.8 or so.

>  If not could you see if the problem still occurs without the external Magma PCIe expansion chassis, this is of course assuming that you can plug the X540 into your system without it.

I played with this a little more and found this:

1) Magma card in z420, connected to chassis containing X540: fails
(original report)
2) X540 in z420, Magma card in z420, connected to empty chassis: fails
3) X540 in z420, Magma card in z420 but no cable to chassis: works

The only difference I've noticed so far between configs 2 & 3 are
different bus numbers and different IRQ assignments:

Config 2 (failing):
  pci 0000:0c:00.0: [8086:1528] type 00 class 0x020000
  pci 0000:0c:00.0: reg 0x10: [mem 0xdac00000-0xdadfffff 64bit pref]
  ixgbe 0000:0c:00.0: irq 82 for MSI/MSI-X
  IRQ 79: 79
  IRQ 80: eth0
  IRQ 81: snd_hda_intel
  IRQ: 82-93 eth1-TxRx-0 through eth1-TxRx-11
  IRQ 94: eth1

Config 3 (working):
  pci 0000:04:00.0: [8086:1528] type 00 class 0x020000
  pci 0000:04:00.0: reg 0x10: [mem 0xdac00000-0xdadfffff 64bit pref]
  ixgbe 0000:04:00.0: irq 75 for MSI/MSI-X
  IRQ 72: ahci
  IRQ 73: eth0
  IRQ 74: snd_hda_intel
  IRQ 75-86: eth1-TxRx-0 through eth1-TxRx-11
  IRQ 87: eth1

I'll try to narrow this down a little more; I'm just giving you this
preliminary info in case it rings any bells for you.

>> -----Original Message-----
>> From: Bjorn Helgaas [mailto:bhelgaas@xxxxxxxxxx]
>> Sent: Friday, August 09, 2013 10:19 AM
>> To: e1000-devel@xxxxxxxxxxxxxxxxxxxxx
>> Cc: linux-pci@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
>> Subject: [E1000-devel] 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
>>
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clk
>> trk
>> _______________________________________________
>> E1000-devel mailing list
>> E1000-devel@xxxxxxxxxxxxxxxxxxxxx
>> https://lists.sourceforge.net/lists/listinfo/e1000-devel
>> To learn more about Intel&#174; Ethernet, visit
>> http://communities.intel.com/community/wired
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/