Re: sockets stuck in CLOSE state 2.2.12
Dave Airlie (airlied@csn.ul.ie)
Thu, 7 Oct 1999 10:57:19 +0100 (IST)
> >
> > eth0 Link encap:Ethernet HWaddr 00:A0:24:B5:E3:AB
> > inet addr:136.201.105.3 Bcast:136.201.255.255 Mask:255.255.0.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:17720994 errors:2925 dropped:2925 overruns:3080
> > 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?
I'm using the 3c590 Vortex Card with the standard 3c59x.c 0.99H from
2.2.12
With the NETDEBUG switch on I am getting loads of
Socket destroy delayed (r=0 w=6928)
Socket destroy delayed (r=0 w=3360)
type messages..
Dave.
>
>
> -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/