sysctl lock, system lockup

Brian Fundakowski Feldman green at
Fri Jun 25 06:16:37 PDT 2004

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 at                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\

More information about the freebsd-current mailing list