[PATCH] Re: 2.2.19: d-link dfe530-tx, Transmit timed out

From: Dennis Bjorklund (db@zigo.dhs.org)
Date: Sat Aug 18 2001 - 04:13:40 EST


On Fri, 17 Aug 2001, Urban Widmark wrote:

> > kernel: eth1: Transmit timed out, status 0000, PHY status 782d, resetting..
>
> Since you run on 2.2 the drivers from www.scyld.com are an option (not
> sure what the 2.4 status is on those). They are similar to the in-kernel
> version but not identical. If you do test, any difference in behaviour is
> intresting.

I haven't tried that, but I looked at tx_timeout() and it looks like it
does the same thing as the driver in the kernel

I did however take a look at the 2.4.x driver and noticed that there is
some logic to reset the card when we get to tx_timeout(). While the card
froze with the current 2.2.19 driver when we get there it now, after I
have backported the 2.4.x logic, resets and works again after it gets to
tx_timeout().

I have some questions and comments about the patch that I have attached.
Most of the patch is (init)stuff that I moved out to their own functions
so it can be called again to reset the card.

The 2.4.x driver have some spinlocks that seems necessary for SMP but it
looks like there are spinlocks missing already in the old 2.2.19 driver if
one compares with the 2.4.x driver. I didn't fix any of these things since
I don't understand all the issues. My feeling is that it is as good or bad
now as before.

I have used it and loaded the network to trigger the bug, and every time
where it froze before it works now and the card resets. For light load it
worked before. To trigger the bug I let the computers on my network send
constantly for an hour or two. Before it used to freeze efter 2-3 weeks of
normal load so it's not easy to trigger.

For me it means I don't have to buy a new network card. I use the card in
a server without keyboard or screen. So every time it freezes it's a pain.
I can't prove that this fixes it but it sure looks like it. It prints the
timout message in the log as before, but continues working.

The last question is what to do with the version string, and what to do to
get this into 2.2.20 (if it's wanted).

-- 
/Dennis


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



This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:27 EST