From owner-freebsd-current  Sun Jun 16 11:10:55 2002
Delivered-To: freebsd-current@freebsd.org
Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP
	id D5D7837B403; Sun, 16 Jun 2002 11:10:38 -0700 (PDT)
Received: (from jhay@localhost)
	by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g5GIASV35012;
	Sun, 16 Jun 2002 20:10:28 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@icomtek.csir.co.za>
Message-Id: <200206161810.g5GIASV35012@zibbi.icomtek.csir.co.za>
Subject: could sleep with "inp" locked
To: hsu@freebsd.org
Date: Sun, 16 Jun 2002 20:10:28 +0200 (SAT)
Cc: current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

After the recent locking working in netinet, I get this message everytime
I login to the -current machine using ssh over ipv6. I don't see it if I
use ipv4.

../../../vm/uma_core.c:1327: could sleep with "inp" locked from ../../../netinet/tcp_usrreq.c:536

PS. That don't mean there are not hundreds of other "could sleep" messages.
There are, but the inp one is new.

John
-- 
John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message