From: shawvrana@gmail.com
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: kernel@linuxace.com, jesse.brandeburg@intel.com, netdev@vger.kernel.org
Subject: Re: e1000 TX unit hang (redux)
Date: Tue, 11 Jul 2006 14:53:27 -0700 [thread overview]
Message-ID: <200607111453.27427.shaw@vranix.com> (raw)
In-Reply-To: <44B4139B.7060907@intel.com>
Hi Auke,
On Tuesday 11 July 2006 14:09, Auke Kok wrote:
>
> > that seems to address this problem by creating a
> >
> > tx_timeout_factor relative to the speed of the NIC. However, there is no
> > mention of this workaround/fix on the bug at the link above and I haven't
> > found any discussion of it here on netdev.
>
> I wouldn't even know what patch you are talking about (?!)
Ok, well, the patch is in 2.6.17.4 and looks to have been announced in the
2.6.16-c2 changelog -- http://lwn.net/Articles/170529/ -- and written by Jeff
Kirsher. I haven't been able to find a link to the original patch submission
anywhere. The code looks something like this now:
/* Detect a transmit hang in hardware, this serializes the
* check with the clearing of time_stamp and movement of i */
adapter->detect_tx_hung = FALSE;
if (tx_ring->buffer_info[eop].dma &&
time_after(jiffies, tx_ring->buffer_info[eop].time_stamp +
(adapter->tx_timeout_factor * HZ))
&& !(E1000_READ_REG(&adapter->hw, STATUS) &
E1000_STATUS_TXOFF)) {
..where the tx_timeout_factor has been added and is set in the watchdog code
based on the link speed.
> that's not only impossible but also unlikely - we don't push changes to 2.4
> kernels anymore a lot, I think the last change is likely older than 2.4.28.
I'm sure you're right. Jumped to conclusions on a patch I saw posted at
redhat.. I'll be more careful next time :)
I'll also try to get some better debugging info from my side.
Thanks.
Shaw
prev parent reply other threads:[~2006-07-11 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 18:16 e1000 TX unit hang (redux) shaw
2006-07-11 21:09 ` Auke Kok
2006-07-11 21:53 ` shawvrana [this message]
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=200607111453.27427.shaw@vranix.com \
--to=shawvrana@gmail.com \
--cc=auke-jan.h.kok@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kernel@linuxace.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).