lkml.org 
[lkml]   [1999]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: sockets stuck in CLOSE state 2.2.12

And in the worst style of following up on oneself ..

from my ifconfig eth0

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?

Dave.

On Mon, 4 Oct 1999, Alan Cox wrote:

> > all client processes hang in CLOSE at the end of an individual "run".
> > The happens to me on all 2.2.X Alpha kernels. This does not happen
> > on Intel.
>
> I think this is different. Dave's dump is showing buffer leakage. WHat
> network card
>

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

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.056 / U:8.456 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site