From owner-freebsd-current@FreeBSD.ORG Fri Jul 9 14:15:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1DC816A4CE; Fri, 9 Jul 2004 14:15:26 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4250443D5E; Fri, 9 Jul 2004 14:15:26 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.34; FreeBSD) id 1Biw9q-00018P-Re; Fri, 09 Jul 2004 18:15:22 +0400 From: Vladimir Grebenschikov To: Brian Fundakowski Feldman In-Reply-To: <20040625131635.GD1149@green.homeunix.org> References: <20040531042234.GA13724@cat.robbins.dropbear.id.au> <1088164637.895.9.camel@localhost> <20040625131635.GD1149@green.homeunix.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Fri, 09 Jul 2004 14:15:21 +0000 Message-Id: <1089382521.910.16.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 1.5.9.2FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: "'current@freebsd.org'" Subject: Re: sysctl lock, system lockup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2004 14:15:26 -0000 On Fri, 2004-06-25 at 09:16 -0400, Brian Fundakowski Feldman wrote: > On Fri, Jun 25, 2004 at 11:57:16AM +0000, Vladimir Grebenschikov wrote: > > On Mon, 2004-05-31 at 14:22 +1000, Tim Robbins wrote: > > > > > I'm not sure where to go from here. A deadlock doesn't seem likely, but > > > it's possible that background fsck could lock up the system for quite > > > some time by using this sysctl. How long did you wait before dropping to > > > ddb (approximately)? > > > > Not sure, probably my problem is related or same (I have posted the > > message to current@ before): > > > > -- > > About 3-5 time per day recent current lockup on my notebook. > > > > Symptoms: > > system responsive, not locked processes works, I can switch X to sc0 > > and back. > > > > processes locked on 'sysctl lock' (see below) > > allways there is one process sleeping on allproc > > > > usually it is related with high activity (this case evolution gets bunch > > of night mail and pass it through spam-assassin) > > Could you possibly do "show locks" from the DDB prompt? This is > essential as it will tell us where something is holding the sysctl > lock hostage. Do not see this problem for about month. It it will appear again I will provide show locks. -- Vladimir B. Grebenchikov vova@fbsd.ru