Re: sockets stuck in CLOSE state 2.2.12

Dave Airlie (airlied@csn.ul.ie)
Fri, 8 Oct 1999 12:57:45 +0100 (IST)

Just to add more information again, I don't remember seeing this problems
with a 2.0.36 kernel on the same machine, with the *same* driver (c file)
(i.e. Donalds driver for 3c590 is for both 2.0.36 and 2.2.12,

Just to see if this helps people any..

Dave.

> > frame:2925
> > TX packets:8406389 errors:0 dropped:0 overruns:6 carrier:6
> > collisions:22574 txqueuelen:100
> > Interrupt:10 Base address:0x6100
> >
> > Could those errors on RX packets have anything to do with it?
>
> Normally RX errors shouldn't be able to cause that (because the network stack
> never sees them as packets), but maybe it is a secondary effect of the driver
> bug that is causing the problem (so far it looks like a driver bug).
> So what driver are you using?
>
>
> -Andi
>
> 

-- 
------------ David Airlie, David.Airlie@ul.ie,airlied@skynet --------
Telecommunications Research Centre, ECE Dept, University of Limerick \
http://www.csn.ul.ie/~airlied	-- Telecommunications Researcher      \
--- TEL: +353-61-202695 -----------------------------------------------




-
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/