Date: Fri, 09 Jul 2004 14:15:21 +0000 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Brian Fundakowski Feldman <green@freebsd.org> Cc: "'current@freebsd.org'" <current@freebsd.org> Subject: Re: sysctl lock, system lockup Message-ID: <1089382521.910.16.camel@localhost> In-Reply-To: <20040625131635.GD1149@green.homeunix.org> References: <FE045D4D9F7AED4CBFF1B3B813C85337051D8DEF@mail.sandvine.com> <20040531042234.GA13724@cat.robbins.dropbear.id.au> <1088164637.895.9.camel@localhost> <20040625131635.GD1149@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1089382521.910.16.camel>