From: Ben Greear <greearb@candelatech.com>
To: Tom Herbert <therbert@google.com>, David Miller <davem@davemloft.net>
Cc: John Fastabend <john.r.fastabend@intel.com>,
netdev <netdev@vger.kernel.org>,
e1000-devel list <e1000-devel@lists.sourceforge.net>
Subject: Re: [E1000-devel] e1000e tx queue timeout in 3.3.0 (bisected to BQL support for e1000e)
Date: Tue, 01 May 2012 14:10:43 -0700 [thread overview]
Message-ID: <4FA05153.1010903@candelatech.com> (raw)
In-Reply-To: <4F91DB7B.7060601@candelatech.com>
On 04/20/2012 02:56 PM, Ben Greear wrote:
> On 04/20/2012 02:21 PM, Tom Herbert wrote:
>> Thanks John for pointers to those. Ben, are you running a kernel with
>> these patches?
>
> I just tested this on my e1000e and igb machine. With these patches,
> I can no longer reproduce the problem.
>
> So, please make sure those are queued up for 3.3 stable!
Dave: I think these patches below should go to 3.3 stable.
They are not queued for stable yet as far as I can tell.
Thanks,
Ben
>
> Thanks,
> Ben
>
>>
>> Tom
>>
>>>
>>> Tom, did you see these two patches? Maybe this is resolved by
>>> the second patch.
>>>
>>> We needed these to fixup ixgbe and igb (i didn't test e1000e)
>>> looks like we might want to push these at stable. I don't
>>> believe they are in 3.3.
>>>
>>> commit b37c0fbe3f6dfba1f8ad2aed47fb40578a254635
>>> Author: Alexander Duyck<alexander.h.duyck@intel.com>
>>> Date: Tue Feb 7 02:29:06 2012 +0000
>>>
>>> net: Add memory barriers to prevent possible race in byte queue limits
>>>
>>> This change adds a memory barrier to the byte queue limit code to address a
>>> possible race as has been seen in the past with the
>>> netif_stop_queue/netif_wake_queue logic.
>>>
>>> Signed-off-by: Alexander Duyck<alexander.h.duyck@intel.com>
>>> Tested-by: Stephen Ko<stephen.s.ko@intel.com>
>>> Signed-off-by: Jeff Kirsher<jeffrey.t.kirsher@intel.com>
>>>
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b37c0fbe3f6dfba1f8ad2aed47fb40578a254635
>>>
>>>
>>> commit 5c4903549c05bbb373479e0ce2992573c120654a
>>> Author: Alexander Duyck<alexander.h.duyck@intel.com>
>>> Date: Tue Feb 7 02:29:01 2012 +0000
>>>
>>> net: Fix issue with netdev_tx_reset_queue not resetting queue from XOFF state
>>>
>>> We are seeing dev_watchdog hangs on several drivers. I suspect this is due
>>> to the __QUEUE_STATE_STACK_XOFF bit being set prior to a reset for link
>>> change, and then not being cleared by netdev_tx_reset_queue. This change
>>> corrects that.
>>>
>>> In addition we were seeing dev_watchdog hangs on igb after running the
>>> ethtool tests. We found this to be due to the fact that the ethtool test
>>> runs the same logic as ndo_start_xmit, but we were never clearing the XOFF
>>> flag since the loopback test in ethtool does not do byte queue accounting.
>>>
>>> Signed-off-by: Alexander Duyck<alexander.h.duyck@intel.com>
>>> Tested-by: Stephen Ko<stephen.s.ko@intel.com>
>>> Signed-off-by: Jeff Kirsher<jeffrey.t.kirsher@intel.com>
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5c4903549c05bbb373479e0ce2992573c120654a
>>>
>>>
>
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-05-01 21:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 23:27 e1000e tx queue timeout in 3.3.0 (bisected to BQL support for e1000e) Ben Greear
2012-04-20 2:39 ` Tom Herbert
2012-04-20 6:44 ` Ying Cai
2012-04-20 19:00 ` Ben Greear
2012-04-20 19:05 ` Tom Herbert
2012-04-20 19:13 ` Ben Greear
2012-04-20 19:44 ` John Fastabend
2012-04-20 21:21 ` Tom Herbert
2012-04-20 21:24 ` Ben Greear
2012-04-20 21:56 ` Ben Greear
2012-05-01 21:10 ` Ben Greear [this message]
2012-05-01 21:49 ` David Miller
2012-05-01 22:08 ` Ben Greear
2012-05-01 22:42 ` [E1000-devel] " Jeff Kirsher
2012-05-01 22:46 ` David Miller
2012-05-01 22:52 ` [E1000-devel] " Jeff Kirsher
2012-04-20 6:46 ` Dave, Tushar N
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=4FA05153.1010903@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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).