From: Robert Love <rml@tech9.net>
To: Alex Riesen <riesen@synopsys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-pre7+preempt: rpciod[178] exited with preempt_count 1
Date: 17 Apr 2002 23:58:19 -0400 [thread overview]
Message-ID: <1019102300.5395.33.camel@phantasy> (raw)
In-Reply-To: <20020417224222.A184@steel>
On Wed, 2002-04-17 at 16:42, Alex Riesen wrote:
> just tried your preempt-kernel-rml-2.4.19-pre7-1.patch.
> I'm using automount (v4) here and am getting this in syslog:
>
> Apr 17 22:32:26 steel kernel: lockd[190] exited with preempt_count 1
> Apr 17 22:32:26 steel kernel: rpciod[189] exited with preempt_count 1
>
> Every time automounter decides to drop an nfs mount.
> Some time ago i've read on lkml that such kind of messages aren't very
> good to see, so decided to drop you a note.
It is most likely caused by nfs neglecting to drop a lock when it exits
- it is not a problem. The error message is there to catch cases where
a task's preempt_count (consider it a task's eligibility to be
preempted) is nonzero when it exists. It should always be zero.
In this case it is probably harmless since the count isn't off until the
task exits. This test may not be worth it with these false positives...
> P.S.
> didn't see them with 2.4.19-pre2-ac2
> interactive feel quiet acceptable, although 2.4.19-pre2-ac2
> 'feels' still better, maybe because of O(1) scheduler, dunno.
> No skips/clicks in xmms while compiling kernel and opening
> a pile of images with gimp. Besides the messages in syslog
> nothing happened
Good to hear.
Robert Love
next prev parent reply other threads:[~2002-04-18 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 20:42 2.4.19-pre7+preempt: rpciod[178] exited with preempt_count 1 Alex Riesen
2002-04-18 3:58 ` Robert Love [this message]
2002-04-18 7:06 ` Trond Myklebust
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=1019102300.5395.33.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riesen@synopsys.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox