On Thu, May 11, 2000 at 12:54:59AM +1000, Andrew Morton wrote:
> Tim Hockin wrote:
> >
> > > We're seeing a stack of stalls with the eepro100
> >
> > We're having lots of trouble with eepro100 and Cisco switches - apparently
> > after some quiescent period, the eepro stops responding until outgoing
> > traffic is generated. We're working on isolating it, but I don't know if
> > it is actually an eepro issue, or a cisco issue yet. Just thought I'd
> > throw it out for anyone to add a "me too!", or more info.
> >
>
> Interesting. There are several identical reports for the 3com drivers.
> The so-called "sleepy NIC" problem, where a NIC which is completely idle
> for 20-30 minutes loses its ability to receive.
This isn't our problem. The NICs are very active (running remote
xapps mostly) when we see stalls. We use eepro100, though, so it looks
like two seperate but equal bugs here.
Sean
> Some people have resorted to a cron job which pings another machine once
> every ten minutes.
>
> I wonder if it is due to the switch? Or perhaps some Linux problem
> above the device driver? Or common to the MII transceiver h/w or
> driver?
>
> I'll shake a few more details out of the 3com uers who have observed
> this behaviour.
>
> --
> -akpm-
>
> -
> 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/
>
-
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 : Mon May 15 2000 - 21:00:17 EST