From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: ixgbe funkiness after OOM
Date: Tue, 08 Dec 2009 22:47:20 -0800 [thread overview]
Message-ID: <1260341240.2239.18.camel@localhost> (raw)
In-Reply-To: <4B1EEB86.4030903@candelatech.com>
On Tue, 2009-12-08 at 17:12 -0700, Ben Greear wrote:
> Kernel: 2.6.31.7, plus hacks
> Fedora 11, 64-bit
> ixgbe NIC is 82699 chipset, 5GT/s 8-lane pcie, not manufactured by Intel.
> CPU: Intel(R) Core(TM) i7 CPU 965 @ 3.20GHz
>
> I've been running some tests with 10k tcp connections (to self), over
> a 2-port ixgbe NIC. First..I managed to OOM my 12GB system..perhaps because
> I have tcp memory settings too high or something (though I was not actually
> setting the tcp rcv/tx buffers for the sockets.) ixgbe was unable to do
> order 0 allocations.
>
> When this happened, the ixgbe NICs got into a state where they could not
> tx any packets: tshark showed ARPs going out on eth2, but the tx pkt counters
> for that NIC did not increase and the peer (eth3, other port on this NIC),
> did not show any rx pkts.
>
> I tried doing ifdown/ifup, but that didn't have much affect (eth3 bumped it's tx counter by 1).
>
> I then tried to rmmod the NIC and re-load the driver. This time, it really looks unhappy:
>
>
> Dec 8 15:27:57 localhost kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 2.0.34-k2
> Dec 8 15:27:57 localhost kernel: ixgbe: Copyright (c) 1999-2009 Intel Corporation.
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.0: HW Init failed: -12
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.0: PCI INT A disabled
> Dec 8 15:27:57 localhost kernel: ixgbe: probe of 0000:03:00.0 failed with error -12
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> Dec 8 15:27:57 localhost kernel: ixgbe: 0000:03:00.1: ixgbe_init_interrupt_scheme: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.1: (PCI Express:5.0Gb/s:Width x4) 00:0c:bd:00:90:19
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.1: MAC: 2, PHY: 9, SFP+: 5, PBA No: ffffff-0ff
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.1: PCI-Express bandwidth available for this card is not sufficient for optimal performance.
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.1: For optimal performance a x8 PCI-Express slot is required.
> Dec 8 15:27:57 localhost kernel: ixgbe 0000:03:00.1: Intel(R) 10 Gigabit Network Connection
>
>
> At this point, there is 8GB of free RAM, and no obvious OOM issues showing up in the logs.
>
> It looks like error -12 means:
>
> IXGBE_ERR_MASTER_REQUESTS_PENDING
>
We have a fix coming for this issue. Basically we have PCIe
transactions that haven't completed when a reset shows up, and are
wedged in the PCIe block. We have a way to whack the hardware the right
way to get these pending transactions cleared, which allows the device
to finish its reset correctly.
I'll try and get that patch fast-tracked through our testing. But if
this issue is easily reproducible for you, I can send you the patch in
the meantime to see if it helps your situation, while we finish our test
pass and push to netdev.
Cheers,
-PJ
>
> I tried rmmod/modprobe several more times...each time I get the same error for
> that device. The one that fails is eth2, the same that could not tx earlier.
>
> Everything came up fine on reboot.
>
> Anyway, this is mostly just for information in case someone else is hitting similar
> issues.
>
> Thanks,
> Ben
>
>
next prev parent reply other threads:[~2009-12-09 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 0:12 ixgbe funkiness after OOM Ben Greear
2009-12-09 6:47 ` Peter P Waskiewicz Jr [this message]
2009-12-09 6:57 ` Ben Greear
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=1260341240.2239.18.camel@localhost \
--to=peter.p.waskiewicz.jr@intel.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).