netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Keehan <mike_keehan@yahoo.com>
To: Scott Feldman <scott.feldman@intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: e100 NETDEV WATCHDOG transmit timeout since 2.6.4
Date: Wed, 21 Apr 2004 06:20:17 -0700 (PDT)	[thread overview]
Message-ID: <20040421132017.68243.qmail@web12305.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0404201559290.7794@snichols-desk.amr.corp.intel.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 3077 bytes --]

HI Scott,

That's a lot better.  

I've been running OK for about four hours on the half duplex network.
The only time that the wathcdog timed out was when I was using
KDE's Konqueror to look at files on a SMB mounted directory
(from an NT 4 system).

Previously the network connection would fail within minutes when
using ssh or ftp to another Linux box.  Now, they have worked
consistently for hours.

Cheers,

   Mike.

--- Scott Feldman <scott.feldman@intel.com> wrote:
> 
> 
> On Tue, 20 Apr 2004, Mike Keehan wrote:
> 
> > I am getting these too in recent kernels, but only on a
> > 10Mhz half-duplex network. I have to manually down
> > and up the interface to recover.
> >
> > On a 100Mhz switched network, the e100 is OK (at least 12hours+).
> 
> 
> Mike/Eamonn,
> 
> Give this patch a try.  This adds a required workaround for ICH when
> working at 10/Half.  (Guessing you have an ICH system).
> 
> --- linux-2.5/drivers/net/e100.c	2004-04-20 15:52:24.000000000 -0700
> +++ linux-2.5/drivers/net/e100.c.mod	2004-04-20 15:55:32.000000000
> -0700
> @@ -287,6 +287,7 @@ enum scb_cmd_hi {
>  };
> 
>  enum scb_cmd_lo {
> +	cuc_nop        = 0x00,
>  	ruc_start      = 0x01,
>  	ruc_load_base  = 0x06,
>  	cuc_start      = 0x10,
> @@ -514,10 +515,11 @@ struct nic {
>  	/* End: frequently used values: keep adjacent for cache effect */
> 
>  	enum {
> -		ich           = (1 << 0),
> -		promiscuous   = (1 << 1),
> -		multicast_all = (1 << 2),
> -		wol_magic     = (1 << 3),
> +		ich                = (1 << 0),
> +		promiscuous        = (1 << 1),
> +		multicast_all      = (1 << 2),
> +		wol_magic          = (1 << 3),
> +		ich_10h_workaround = (1 << 4),
>  	} flags					____cacheline_aligned;
> 
>  	enum mac mac;
> @@ -1225,6 +1227,12 @@ static void e100_watchdog(unsigned long
>  		/* Issue a multicast command to workaround a 557 lock up */
>  		e100_set_multicast_list(nic->netdev);
> 
> +	if(nic->flags & ich && cmd.speed==SPEED_10 &&
> cmd.duplex==DUPLEX_HALF)
> +		/* Need SW workaround for ICH[x] 10Mbps/half duplex Tx hang. */
> +		nic->flags |= ich_10h_workaround;
> +	else
> +		nic->flags &= ~ich_10h_workaround;
> +
>  	mod_timer(&nic->watchdog, jiffies + E100_WATCHDOG_PERIOD);
>  }
> 
> @@ -1244,7 +1252,17 @@ static inline void e100_xmit_prepare(str
>  static int e100_xmit_frame(struct sk_buff *skb, struct net_device
> *netdev)
>  {
>  	struct nic *nic = netdev->priv;
> -	int err = e100_exec_cb(nic, skb, e100_xmit_prepare);
> +	int err;
> +
> +	if(nic->flags & ich_10h_workaround) {
> +		/* SW workaround for ICH[x] 10Mbps/half duplex Tx hang.
> +		   Issue a NOP command followed by a 1us delay before
> +		   issuing the Tx command. */
> +		e100_exec_cmd(nic, cuc_nop, 0);
> +		udelay(1);
> +	}
> +
> +	err = e100_exec_cb(nic, skb, e100_xmit_prepare);
> 
>  	switch(err) {
>  	case -ENOSPC:
> 



	
		
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash

  parent reply	other threads:[~2004-04-21 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C6F5CF431189FA4CBAEC9E7DD5441E0103E9A4E6@orsmsx402.jf.intel.com>
2004-04-20 23:04 ` e100 NETDEV WATCHDOG transmit timeout since 2.6.4 Scott Feldman
2004-04-21  9:42   ` Eamonn Hamilton
2004-04-21 13:20   ` Mike Keehan [this message]
     [not found] <20040420155903.GA16152@zarquon.at.home>
2004-04-20 16:08 ` Mike Keehan

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=20040421132017.68243.qmail@web12305.mail.yahoo.com \
    --to=mike_keehan@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --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 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).