netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related t

from [Jeff Garzik] [Permanent Link][Original]
To: Shawn Starr <shawn.starr@xxxxxxxxxx>
Subject: Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?
From: Jeff Garzik <jgarzik@xxxxxxxxx>
Date: Sun, 11 Apr 2004 17:01:58 -0400
Cc: "'Len Brown'" <len.brown@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <000001c42000$dd6e78f0$0200080a@panic>
References: <000001c42000$dd6e78f0$0200080a@panic>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
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





[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [PATCH 2.6.6-rc1] pcnet32 transmit performance fix, Don Fry
Next by Date:  Re: IMQ / new Dummy device post., jamal
Previous by Thread:  RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?, Shawn Starr
Next by Thread:  RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?, Shawn Starr
Indexes:  [Date] [Thread] [Top] [All Lists]