From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 21:18:19 2008 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D49CD1065674 for ; Tue, 23 Sep 2008 21:18:19 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id AAEF58FC17 for ; Tue, 23 Sep 2008 21:18:19 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id 4439146B46; Tue, 23 Sep 2008 17:18:19 -0400 (EDT) Date: Tue, 23 Sep 2008 22:18:19 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Mikhail Teterin In-Reply-To: <48D955EE.3090108@aldan.algebra.com> Message-ID: References: <48D92589.8000200@aldan.algebra.com> <48D955EE.3090108@aldan.algebra.com> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="621616949-1052563692-1222204699=:68287" Cc: stable@FreeBSD.org Subject: Re: 7.0-stable: a hung process - scheduler bug? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2008 21:18:19 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --621616949-1052563692-1222204699=:68287 Content-Type: TEXT/PLAIN; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 23 Sep 2008, Mikhail Teterin wrote: > Robert Watson ΞΑΠΙΣΑΧ(ΜΑ): >> Could you try procstat -kk on the process, does that shed any light? > When I was trying `procstat -k', I was getting the message: > > PID TID COMM TDNAME KSTACK > procstat: sysctl: kern.proc.kstack unavailable > procstat: options DDB or options STACK required in kernel > > That was with a single `-k'. I can't do anything now, because -- after an > attempt to start `systat 1 -vm' -- the system hosed and would not start new > processes. The existing ones, such as the cvs-over ssh are stuck in: > > load: 0.00 cmd: ssh 59098 [proctree] 0.41u 0.17s 0% 0k Sounds a lot like a lock leak/deadlock. Other than DDB output or a crashdump, which would allow us to explore some more, there's probably not much to be done with the box at this point other than reset. Sorry about that. Robert N M Watson Computer Laboratory University of Cambridge --621616949-1052563692-1222204699=:68287--