Date: Tue, 23 Sep 2008 22:18:19 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Mikhail Teterin <mi+mill@aldan.algebra.com> Cc: stable@FreeBSD.org Subject: Re: 7.0-stable: a hung process - scheduler bug? Message-ID: <alpine.BSF.1.10.0809232217081.68287@fledge.watson.org> In-Reply-To: <48D955EE.3090108@aldan.algebra.com> References: <48D92589.8000200@aldan.algebra.com> <alpine.BSF.1.10.0809232136130.68287@fledge.watson.org> <48D955EE.3090108@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0809232217081.68287>