Re: linux-kernel-digest V1 #105

Alan Cox (iialan@iifeak.swan.ac.uk)
Wed, 5 Jul 1995 09:24:54 +0100 (BST)


> From: Thomas.Koenig@ciw.uni-karlsruhe.de (=?ISO-8859-1?Q?Thomas_K=F6nig?=)
> Date: Sat, 1 Jul 1995 02:19:27 +0200 (MET DST)
> Subject: 1.3.5: spurious 'connection refused'
>
> I just had a spurious 'connection refused' in 1.3.5, I don't really know
> where this came from.
>
> I'm running a script which transfers xauth data via rsh, then
> does an rlogin; the error message I got was:
>
> $ pc66
> rcmd: connect: mvmampc66.ciw.uni-karlsruhe.de: Connection refused

You got a sequence space collision. The local end thought the socket was
free, the remote was still in TIME_WAIT.

Its a feature of TCP.

> From: greg@wind.rmcc.com (G.W. Wettstein)
> Date: Mon, 3 Jul 1995 17:49:32 CDT
> Subject: Failure of 1.3.6, Cyclades implicated again.
>
> Address decomposition:
>
> EIP:
> 00138824 T _dev_alloc_skb
>
> If there is any other additional information that would be useful
> please feel free to give me a holler. Take care, have a pleasant
> remainder of the week.

That looks like something stamped on memory that it didnt own. I don't know
if that helps anyone debug it.

Alan