All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Uziel <uzi@uzix.org>
To: Kieran <kieran@esperi.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ultrasparc 1 network freeze
Date: Sun, 11 Aug 2002 15:30:11 -0700	[thread overview]
Message-ID: <20020811223010.GB16890@uzix.org> (raw)
In-Reply-To: <Pine.LNX.4.43.0208112110500.391-100000@amaterasu.srvr.nix>

* Kieran <kieran@esperi.demon.co.uk> [020811 13:58]:
> I've got an ultra 1 with on-board HME that I'm trying to install linux
> on via the serial console.
...
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out, resetting
> eth0: Happy Status 03030000 TX[000003ff:00000101]
... 
> Reboot seems to cure the problem (via break on the console and then
> issuing a boot command at the prom monitor), until further stress is
> applied.

Yep... known issue with the sunhme driver.  AFAIK, it only affects the
HME onboard the U1E systems and no other HMEs.  The quick band-aid
work-around is at the end of this email... seems to be some weirdo
timing issue.  This patch has resolved the issue for several people with
U1E's.  (E == enterprise... UPA (for a Creator3D), wide scsi and hme
(insted of an le on the non-E models)).

--- drivers/net/sunhme.c.orig	Mon Jul 15 02:38:27 2002
+++ drivers/net/sunhme.c	Mon Jul 15 03:09:03 2002
@@ -1983,6 +1983,7 @@
 	}
 	hp->tx_old = elem;
 	TXD((">"));
+	udelay(1);
 
 	if (netif_queue_stopped(dev) &&
 	    TX_BUFFS_AVAIL(hp) > (MAX_SKB_FRAGS + 1))


  reply	other threads:[~2002-08-11 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-11 20:55 Ultrasparc 1 network freeze Kieran
2002-08-11 22:30 ` Joshua Uziel [this message]
2002-08-12  1:29   ` David S. Miller
2002-08-12  5:09     ` Joshua Uziel
2002-08-12  7:11       ` Joshua Uziel
2002-08-12  7:53         ` David S. Miller

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=20020811223010.GB16890@uzix.org \
    --to=uzi@uzix.org \
    --cc=kieran@esperi.demon.co.uk \
    --cc=linux-kernel@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 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.