From: Don Fry <brazilnut@us.ibm.com>
To: Perolo Silantico <per.sil@gmx.it>
Cc: Stephen Hemminger <shemminger@osdl.org>,
john.ronciak@intel.com, ganesh.venkatesan@intel.com,
scott.feldman@intel.com, netdev@oss.sgi.com
Subject: Re: [Bug 3440] New: eth0 freezes: "NETDEV WATCHDOG: eth0: transmit timed out "
Date: Wed, 22 Sep 2004 10:50:39 -0700 [thread overview]
Message-ID: <20040922175039.GA14542@us.ibm.com> (raw)
In-Reply-To: <BJEDLIFMBCLIGJJBNCLJGECPCPAA.per.sil@gmx.it>
In looking at the dmesg log for bug 3440, it looks like eth0 is a
RealTek adapter and eth1 is an eepro100.
"8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xd0842000, 00:50:fc:4c:d6:9b, IRQ 9
eth0: Identified 8139 chip type 'RTL-8139C'"
"eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<saw@saw.sw.com.sg> and others
eth1: 0000:00:0e.0, 00:A0:C9:43:8C:E4, IRQ 15."
Another way to verify which driver is associated with a device name is
to use 'ethtool -i eth0'. This will report the driver name and version
of the driver.
If the same problems happens with the pcnet32 driver, I can help you
debug the problem with the pcnet32.
On Wed, Sep 22, 2004 at 06:45:12PM +0200, Perolo Silantico wrote:
> Same behaviour for drivers:
> - 8139too (kernel 2.6.8.1 and 2.6.8)
> - e100 (kernel 2.6.8)
> - eepro100 (kernel 2.6.8.1)
>
> I have tried with all these drivers. Therefore it seemed to me, that this is not related to any specific driver. But to be sure, I will grab a 3com 905C from another server and try with that one and will try with the PCNet32 too.
>
> >
> > From: Stephen Hemminger [mailto:shemminger@osdl.org]
> > Sent: Mittwoch, 22. September 2004 18:27
> > To: per.sil@gmx.it; john.ronciak@intel.com; ganesh.venkatesan@intel.com;
> > scott.feldman@intel.com
> > Cc: netdev@oss.sgi.com
> > Subject: Re: [Bug 3440] New: eth0 freezes: "NETDEV WATCHDOG: eth0:
> > transmit timed out "
> >
> >
> > This is an ethernet driver related problem. Which of the
> > ethernet cars (PCNet32 or E100)
> > is assigned to eth0? And which of the two e100 drivers (e100 or
> > eepro100) are you using?
> >
> >
> > On Tue, 21 Sep 2004 09:42:06 -0700
> > bugme-daemon@osdl.org wrote:
> >
> > > http://bugme.osdl.org/show_bug.cgi?id=3440
> > >
> > > Summary: eth0 freezes: "NETDEV WATCHDOG: eth0:
> > transmit timed out
> > > "
> > > Kernel Version: 2.6.8.1
> > > Status: NEW
> > > Severity: high
> > > Owner: shemminger@osdl.org
> > > Submitter: per.sil@gmx.it
> > >
> > >
--
Don Fry
brazilnut@us.ibm.com
next prev parent reply other threads:[~2004-09-22 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409211642.i8LGg6Uq012224@fire-1.osdl.org>
2004-09-22 16:27 ` [Bug 3440] New: eth0 freezes: "NETDEV WATCHDOG: eth0: transmit timed out " Stephen Hemminger
2004-09-22 16:45 ` AW: " Perolo Silantico
2004-09-22 17:50 ` Don Fry [this message]
2004-09-22 20:22 ` Francois Romieu
2004-09-22 21:03 ` Perolo Silantico
2004-09-22 21:19 ` Stephen Hemminger
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=20040922175039.GA14542@us.ibm.com \
--to=brazilnut@us.ibm.com \
--cc=ganesh.venkatesan@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@oss.sgi.com \
--cc=per.sil@gmx.it \
--cc=scott.feldman@intel.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).