From: Thomas Dodd <ted@cypress.com>
To: Adam Schrotenboer <adam@tabris.net>
Cc: linux-kernel@vger.kernel.org, jgarzik@mandrakesoft.com
Subject: Re: [Repost] Tulip Bug ?
Date: Wed, 13 Mar 2002 18:26:18 -0600 [thread overview]
Message-ID: <3C8FEE2A.8030905@cypress.com> (raw)
In-Reply-To: <20020313203530.8FDABFB911@tabriel.tabris.net>
Adam Schrotenboer wrote:
> (I can't tell if it made its way to the list......)
It made it both times :)
> I also have some more information. This ethdev is connected to a
> Efficient Networks Speedstream 5260, which may be the cause of the
> problems (the modem came w/ a D-Link RTL8139C ethdev, but I replaced
> both of my ethdevs w/ tulips.) Maybe I need to find out how to program
> the EEPROM for 10Mbps half duplex ?????
>
> I am currently running 2.4.18-pre9-mjc2, but this also happens w/
> 2.4.18-pre9 (and 2.4.18-pre7-mjc, maybe others)
I see it a lot on a Netgear FA310TX
( detected as Lite-On 82c168 PNIC rev 33)
With both v 1.1.8(June 16,2001) and
v 0.9.15-pre9(Nov 6, 2001)
kernel is 2.4.19-pre2-ac2 but it's been a problem for
months.
> I am getting NETDEV Watchdog timeouts
I only get the NETDEV messages.
> I have been getting this at largely unpredictable intervals. The
> solutions seems to be to ifdown the ethdevs, and rmmod the driver. then
> ifup the ethdevs (which also means I have to stop my PPPoE-DSL
> connection).
Using xfs top serve fonts to a Solaris8 box was impossible.
too many timeouts. Same for NFS mounted $HOME (from Solaris)
making it impossible to use the box.
-Thomas
prev parent reply other threads:[~2002-03-14 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 20:35 [Repost] Tulip Bug ? Adam Schrotenboer
2002-03-14 0:26 ` Thomas Dodd [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=3C8FEE2A.8030905@cypress.com \
--to=ted@cypress.com \
--cc=adam@tabris.net \
--cc=jgarzik@mandrakesoft.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox