From owner-freebsd-current@FreeBSD.ORG Fri Jun 25 13:16:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 26E9C16A4CE; Fri, 25 Jun 2004 13:16:37 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i5PDGaCO004362; Fri, 25 Jun 2004 09:16:36 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i5PDGZCR004361; Fri, 25 Jun 2004 09:16:35 -0400 (EDT) (envelope-from green) Date: Fri, 25 Jun 2004 09:16:35 -0400 From: Brian Fundakowski Feldman To: Vladimir Grebenschikov Message-ID: <20040625131635.GD1149@green.homeunix.org> References: <20040531042234.GA13724@cat.robbins.dropbear.id.au> <1088164637.895.9.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1088164637.895.9.camel@localhost> User-Agent: Mutt/1.5.6i cc: "'current@freebsd.org'" Subject: Re: sysctl lock, system lockup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 13:16:37 -0000 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. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\