From: tabris <tabris@tabris.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>, jgarzik@mandrakesoft.com
Subject: Re: Failure report: tulip driver
Date: Tue, 4 Jun 2002 11:23:07 -0400 [thread overview]
Message-ID: <20020604152307.B8D81FB911@tabriel.tabris.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0206041555020.1201-100000@grignard>
On Tuesday 04 June 2002 10:18, Rasmus Bøg Hansen wrote:
> [1.] One line summary of the problem:
>
> tulip.o gives transmit timeouts and a reboot is needed.
I'd like to say I reported this same problem a couple months ago...
1) I think it might be partly a timing/temperature issue.
2) it is possible to recover simply by ifdown the interfaces, then rmmod
the module (assuming it is compiled as module...), then ifup the ifaces
again.
3) I'm cc'ing this to Jeff Garzik, as I think he is the current
maintainer of the tulip driver.
--
tabris
next prev parent reply other threads:[~2002-06-04 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 14:18 Failure report: tulip driver Rasmus Bøg Hansen
2002-06-04 15:23 ` tabris [this message]
2002-06-04 16:16 ` Rasmus Bøg Hansen
2002-06-04 18:18 ` Francois Romieu
2002-06-06 16:12 ` tabris
2002-06-06 16:57 ` Rasmus Bøg Hansen
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=20020604152307.B8D81FB911@tabriel.tabris.net \
--to=tabris@tabris.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moffe@amagerkollegiet.dk \
/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