All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Sebor <petr@scssoft.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.x] e1000: NETDEV WATCHDOG: eth0: transmit timed out
Date: Tue, 27 Jan 2004 14:59:05 +0100	[thread overview]
Message-ID: <40166EA9.9040806@scssoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401261625210.3324-100000@localhost.localdomain>

Feldman, Scott wrote:

>Petr, sorry for the suspense.  Here's a patch against 2.6.2-rc2 that fixes 
>a race in the Tx path of e1000 that you may be exposing with TSO on.  The 
>race is:
>
>Tx queue		Tx clean (interrupt context)
>
>...
>if(h/w Q full)         | clean h/w Q
>        ...        <---| if(s/w Q stopped) 
>        stop s/w Q     |       wake s/w Q
>
>
>So let's try this patch with TSO back on.
>  
>
Scott,

thanks for the patch. Again, 3/4 of working day with moderate server 
load resulted in no
WATCHDOG barking with the patched kernel and tso's turned on. I dare say 
that this is it! :-)
(Little more testing here won't harm though)

If nothing, the stability of the e1000 has vastly improved

Thanks a lot!

Regards,
Petr


  reply	other threads:[~2004-01-27 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C6F5CF431189FA4CBAEC9E7DD5441E01036EA9DA@orsmsx402.jf.intel.com>
2004-01-27  0:37 ` [2.6.x] e1000: NETDEV WATCHDOG: eth0: transmit timed out Feldman, Scott
2004-01-27 13:59   ` Petr Sebor [this message]
2004-01-23 22:28 Feldman, Scott
2004-01-24 19:36 ` Sergey S. Kostyliov
2004-01-26 10:33 ` Petr Sebor
  -- strict thread matches above, loose matches on Subject: below --
2004-01-23 21:43 Petr Sebor

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=40166EA9.9040806@scssoft.com \
    --to=petr@scssoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott.feldman@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.