All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Robert Love <rml@tech9.net>
Cc: Duncan Sands <duncan.sands@math.u-psud.fr>,
	Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.8-pre2: preempt: exits with preempt_count 1
Date: Wed, 10 Apr 2002 15:07:15 -0700	[thread overview]
Message-ID: <20020410150715.A1550@figure1.int.wirex.com> (raw)
In-Reply-To: <E16vHbV-0000M5-00@baldrick> <1018463295.6681.18.camel@phantasy>

* Robert Love (rml@tech9.net) wrote:
> On Wed, 2002-04-10 at 08:53, Duncan Sands wrote:
> 
> > error: halt[411] exited with preempt_count 1
> > 
> > This was after about 24 hours of up time.  What can I do to help
> > track down this locking problem?
> 
> It is not a big deal.  The issue is that in the system shutdown code,
> something does not release a lock but just figures "the system is going
> down, what is the point?"  It is probably the BKL ...
> 
> For the sake of code readability and having nothing quit with a nonzero
> preempt_count, we should explicitly drop the lock, but it is not hurting
> anything (now, if you get this message elsewhere, there may be a
> problem).

ditto with nfs.  doesn't require a system shutdown, just stopping the
nfs server.

error: nfsd[983] exited with preempt_count 1
error: rpciod[994] exited with preempt_count 1
error: lockd[993] exited with preempt_count 1

cheers,
-chris

  parent reply	other threads:[~2002-04-10 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 12:53 2.5.8-pre2: preempt: exits with preempt_count 1 Duncan Sands
2002-04-10 18:28 ` Robert Love
2002-04-10 18:42   ` Pierre Rousselet
2002-04-10 19:21     ` Duncan Sands
2002-04-10 22:07   ` Chris Wright [this message]
2002-04-10 22:14   ` Bongani
2002-04-10 18:40 ` Skip Ford
2002-04-10 19:20   ` Duncan Sands

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020410150715.A1550@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=duncan.sands@math.u-psud.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.