From owner-freebsd-hackers@FreeBSD.ORG  Thu Apr  3 15:03:59 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 89A069A9
 for <freebsd-hackers@freebsd.org>; Thu,  3 Apr 2014 15:03:59 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 616338D3
 for <freebsd-hackers@freebsd.org>; Thu,  3 Apr 2014 15:03:59 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id A6AAAB980;
 Thu,  3 Apr 2014 11:03:55 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: Karl Pielorz <kpielorz_lst@tdx.co.uk>
Subject: Re: Stuck CLOSED sockets / sshd / zombies...
Date: Thu, 3 Apr 2014 11:03:40 -0400
User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; )
References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk>
 <201404021405.56878.jhb@freebsd.org>
 <9FDC091D98AB2CF92DE4399F@Mail-PC.tdx.co.uk>
In-Reply-To: <9FDC091D98AB2CF92DE4399F@Mail-PC.tdx.co.uk>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201404031103.41171.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Thu, 03 Apr 2014 11:03:55 -0400 (EDT)
Cc: freebsd-hackers@freebsd.org
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 15:03:59 -0000

On Thursday, April 03, 2014 4:02:21 am Karl Pielorz wrote:
>=20
> --On 02 April 2014 14:05 -0400 John Baldwin <jhb@freebsd.org> wrote:
>=20
> > Grr, I guess that's what I should have expected.  Was sort of hoping to
> > be able to see which socket it was blocked on.  Can you run 'kgdb' as r=
oot
> > (no args), then do 'proc 4346' and 'bt'?  If you are familiar with gdb,
> > walk up to the frame that in sys_read and do 'p *uap' so we can see whi=
ch
> > fd is being read.
>=20
> Ok, think I've done this right (if not, let me know what I should be doin=
g=20
> :)
>=20
> "
> ...
> (kgdb) up
> #9  0xffffffff80903133 in sys_read (td=3D<value optimized out>, uap=3D<va=
lue=20
> optimized out>) at ../../../kern/sys_generic.c:171
> 171             error =3D kern_readv(td, uap->fd, &auio);
> (kgdb) p *uap
> $1 =3D {fd_l_ =3D 0xfffff800238bb920 "\b\021I\201=C3=BF=C3=BF=C3=BF=C3=BF=
", fd =3D -2125917944,=20
> fd_r_ =3D "=C3=BF=C3=BF=C3=BF=C3=BF", buf_l_ =3D 0xfffff800238bb928 "", b=
uf =3D=20
> 0xfffff800237a1000,
>   buf_r_ =3D 0xfffff800238bb930 "", nbyte_l_ =3D 0xfffff800238bb930 "", n=
byte =3D=20
> 0, nbyte_r_ =3D 0xfffff800238bb938 "\020\020z#"}

Hmm, that fd value doesn't make any sense now.  Do you have the backtrace f=
or
that process?  The fd may show up in the arguments to kern_readv().

=2D-=20
John Baldwin