Re: eth1: Transmit timed out, status 0000, PHY status 0000

richard.morgan9 (richard.morgan9@ntlworld.com)
Tue, 16 Jan 2001 22:40:24 -0000


>> On Sun, 14 Jan 2001, Urban Widmark wrote:
>>
>> >> eth1: Transmit timed out, status 0000, PHY status 0000,
>> >> resetting...
>> >[snip]
>> >> Keeps going nonstop until I ifdown eth1.
>> >>
>> >> Card worked fine 2 days ago...
>> >
>> >So what did you change?
>>
>> Nothing.
>>
>> >Has the machine been up since then?
>>
>> No. I rebooted to W98 a few times. W98 doesn't have a driver
>> installed for that card though - and wont.
>>
>>
>>
>> >Someone else with the same symptoms (in 2.4)
>> > http://www.uwsg.iu.edu/hypermail/linux/net/0011.0/0027.html
>> >
>> >Becker's reply
>> > http://www.uwsg.iu.edu/hypermail/linux/net/0011.0/0032.html
>> >
>> >"Try unplugging the system and doing a really cold boot. A soft-off does
>> > not reset the chip.
>>
>> Tried that too.. didn't work. I switched PCI slots and whatnot
>> though and it works again.. <shrug>
>>
>
>> > If this solves the problem, we will have to add code to re-load the
>> > EEPROM info into the chip."
>>
>> If the problem recurs I will try to test it out more and report
>> to the list.
>>
>> FWIW it is a DLink DFE 530TX.
>>
snip

I have the same problem as Urban with a recent DLink 530tx
(rhine2). Pulling the power cable from my atx psu (while the
computer was "off") fixed the card, until my next reboot from
win98.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/