| To: | "'Jeff Garzik'" <jgarzik@xxxxxxxxx> |
|---|---|
| Subject: | RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? |
| From: | "Shawn Starr" <shawn.starr@xxxxxxxxxx> |
| Date: | Tue, 13 Apr 2004 01:16:33 -0400 |
| Cc: | "'Len Brown'" <len.brown@xxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx> |
| Importance: | Normal |
| In-reply-to: | <4079B246.4070107@xxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Any plan for inclusion of linux-wlan-ng ?, Jouni Malinen |
|---|---|
| Next by Date: | RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?, Shawn Starr |
| Previous by Thread: | Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?, Jeff Garzik |
| Next by Thread: | Fragmentation issue, krupa |
| Indexes: | [Date] [Thread] [Top] [All Lists] |