Re: via-rhine: NETDEV WATCHDOG: eth0: transmit timed out

From: Marco Colombo (marco@esi.it)
Date: Tue Jun 06 2000 - 12:30:47 EST


On Tue, 6 Jun 2000, Urban Widmark wrote:

> On Mon, 5 Jun 2000, Marco Colombo wrote:
>
> > On Sun, 4 Jun 2000, Urban Widmark wrote:
> >
> > > Does it send anything at all? (sbin/ifconfig, TX packets)
> > > Do you get any interrupts counted in /proc/interrupts?
> >
> > Sorry for being unclear. The empty line means quite a lot of time.
>
> No problem, but you didn't answer my question :) The /proc/interrupts
> question was just to see if it is the same "behaviour" as a different
> problem (the misaligned buffer). If the driver gets no interrupts it will
> never consider the packets as sent, this will fill the transmit buffer
> and it will soon stop sending anything and it will also trigger the
> watchdog.

Yes there were interrupts reported (I thought it was obviuos, since
the card worked with most low load operations). It pinged, i could telnet
into it, i could open a gnome-terminal on it with X output to a remote X
server...

>
> > I run into this problem a few months ago, I believe on a K6, Asus P5A
> > system. It worked fine, but a large FTP transfers triggered the same
>
> What kernel version? 2.3.x x = { 40-ish? < x < 51 (52?) } can easily be
> made to crash in the via-rhine driver (but runs fine when the traffic is
> low). No, wait, you don't test that many 2.3's so you get this with
> 2.2. Hmm, I don't know.

2.2.xx sure.

> > It happens with X traffic. I just open a gnome-terminal with
> > DISPLAY=some.host:0, choose Preference, Colors, fire the color picker,
> > and start moving the color point around with the mouse button held down
> > (this makes all the color indicators and the bars move). After a few
> > seconds the card hangs. I've managed to get this also playing with the
>
> Can't make it happen here (but then my other box is an old x86). Do you
> have a graphics card using the same irq or so?

I don't have info handy (it's running on the GA-71XE, right now)
but I'm pretty sure the card was not sharing IRQs. The K7V manual has
info on which PCI slots share INTs, and I put the card into the 2nd
PCI slot, which is marked INT-B 'not shared'.

> I'm a little bit out of my depth here, but I think that hardware sharing
> resources (irqs) can have a few quirks (ie some hardware/driver doesn't
> work well in that mode). Does 'lspci -v' show anything remotely like
> that? That win2k also crashes could be a hint that there is a hw cfg
> problem. Any funny BIOS settings to play with?

win2k is not one issue of mine. B-)

The K7V has a default setting of PCI latency timer of `32' (whatever
it means exactly) and the card driver reported to raise it to `64'.
I set that value on the BIOS settings, and the card seemed fine
with it. But it timed out on transmission the same way.
The GA-71XE has a default value of `64', BTW.

> Oh, and you have the card in a bus-master PCI slot? It's not supposed to
> work otherwise.

I think so... there is no info on which slots are bus-master or not.
I think they are all capable of receiving bus-mastering cards.

> > Now I'll swap the Asus MB with a GA-71XE.
>
> And you got it to work ... could be a hw problem, or just that now things
> (irqs) get assigned differently.

I suspect some PCI issues. After all, both the P5A and the K7V are from
the same manufacturer. I'll try to get another brand soon.

> /Urban

.TM.

-- 
      ____/  ____/   /
     /      /       /			Marco Colombo
    ___/  ___  /   /		      Technical Manager
   /          /   /			 ESI s.r.l.
 _____/ _____/  _/		       Colombo@ESI.it

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



This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:25 EST