From: "Shawn Starr" <shawn.starr@rogers.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>
Cc: "'Len Brown'" <len.brown@intel.com>,
<linux-kernel@vger.kernel.org>, <netdev@oss.sgi.com>
Subject: RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?
Date: Tue, 13 Apr 2004 01:16:33 -0400 [thread overview]
Message-ID: <000001c42116$7d00fb70$0200080a@panic> (raw)
In-Reply-To: <4079B246.4070107@pobox.com>
Might be, I have since not had any issues with timeouts. Though, I don't
know where it is doing this. It is an IBM machine so some things are
proprietary.
-----Original Message-----
From: Jeff Garzik
Sent: Sunday, April 11, 2004 05:02 PM
To: Shawn Starr
Cc: 'Len Brown'; linux-kernel@; netdev@
Subject: Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout
-Related to i2c interface?
Shawn Starr wrote:
> Ok, this is strange, I put in an external 10/100 PRO S Adaptor, and im
> not getting anymore eth0 timeouts, I would only get eth0 timeouts on
> the ONBOARD nic if I enabled the lm80 sensor driver.. I don't know
> what to say, the onboard nic would work fine without lm80 being
> loaded?
>
> Is there some sort of race condition that the onboard 10/100 PRO is
> doing ?
If i2c is killing the network, sounds like it's diddling something on
the motherboard it shouldn't...
Jeff
next prev parent reply other threads:[~2004-04-13 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1081671742.2844.0.camel@dhcppc4>
2004-04-11 20:09 ` [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr
2004-04-11 21:01 ` Jeff Garzik
2004-04-13 5:16 ` Shawn Starr [this message]
2003-12-02 5:34 ` Fragmentation issue krupa
2004-04-13 5:16 ` [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr
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='000001c42116$7d00fb70$0200080a@panic' \
--to=shawn.starr@rogers.com \
--cc=jgarzik@pobox.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 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.