From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 16 06:36:29 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4500B37B401 for ; Wed, 16 Jul 2003 06:36:29 -0700 (PDT) Received: from godel.mtl.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87E2343F3F for ; Wed, 16 Jul 2003 06:36:28 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: from godel.mtl.distributel.net (localhost [127.0.0.1]) h6G9eYEH013486; Wed, 16 Jul 2003 09:40:34 GMT (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by godel.mtl.distributel.net (8.12.9/8.12.9/Submit) id h6G9eXBY013485; Wed, 16 Jul 2003 09:40:33 GMT X-Authentication-Warning: godel.mtl.distributel.net: bmilekic set sender to bmilekic@technokratis.com using -f Date: Wed, 16 Jul 2003 09:40:33 +0000 From: Bosko Milekic To: Josh Brooks Message-ID: <20030716094033.GA13330@technokratis.com> References: <20030715223653.Y36933-100000@mail.econolodgetulsa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030715223653.Y36933-100000@mail.econolodgetulsa.com> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org Subject: Re: running 5.1-RELEASE with no procfs mounted (lockups?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 13:36:29 -0000 On Tue, Jul 15, 2003 at 10:43:19PM -0700, Josh Brooks wrote: [...] > One of the systems, the one I am doing all the work on, is an SMP system, > and it keeps locking up on me - the lockups are always the same - things > are going fine, and suddenly a process fails to complete - maybe it is > "pwd", maybe I type :q! in "vi" and it just sticks there - either > way, randomly, processes just begin to lock up ... if I log in on another > session, I can see the PID, but I cannot kill it - I can kill -9 (PID) 100 > times and it will still exist. Eventually the entire system will lock up, > although you can always ping the system. When this happens and you start another session to kill the original process, can you perhaps run 'ps -l' and get the MWCHAN column? The process could be stuck blocking somewhere in the kernel, which is why your signal is not being delivered. Anyway, this is just one possibility. See if all the processes you describe as 'frozen' have the same MWCHAN and, if so, what is it? -- Bosko Milekic * bmilekic@technokratis.com * bmilekic@FreeBSD.org TECHNOkRATIS Consulting Services * http://www.technokratis.com/