From: Robert Love <rml@tech9.net>
To: Thunder from the hill <thunder@lightweight.ods.org>
Cc: Arador <diegocg@teleline.es>,
dag@newtech.fi, linux-kernel@vger.kernel.org, conman@kolivas.net
Subject: Re: Preempt note in the logs
Date: 24 Aug 2002 13:48:03 -0400 [thread overview]
Message-ID: <1030211284.1935.4991.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0208241109210.3234-100000@hawkeye.luckynet.adm>
On Sat, 2002-08-24 at 13:12, Thunder from the hill wrote:
> We have to check
> 1. process kicking code
> 2. process killing code
> 3. memory allocation code
> 4. read/write code
The problem can be anywhere, actually. #4 (and other file I/O) is the
best bet though, I suspect.
It is caused by any mismatched locking - it is a good debugging check
regardless of preemption.
The only known place I or others see it now is on shutdown, since we
have kernel threads that do not drop the BKL and other locks when they
shutdown since the system is about to halt anyway.
There was some reports of XFS earlier... I thought they were fixed (I
talked to those guys). Maybe some other rogue module...
Robert Love
next prev parent reply other threads:[~2002-08-24 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 8:52 Dag Nygren
2002-08-24 9:45 ` Thunder from the hill
2002-08-24 9:58 ` Preempt note in the logs (and patch) Dag Nygren
2002-08-24 16:15 ` Preempt note in the logs Robert Love
2002-08-24 17:02 ` Arador
2002-08-24 17:12 ` Thunder from the hill
2002-08-24 17:48 ` Robert Love [this message]
2002-08-24 18:01 ` Thunder from the hill
2002-08-24 18:11 ` Robert Love
2002-08-24 18:18 ` Thunder from the hill
2002-08-24 18:20 ` Thunder from the hill
2002-08-24 18:55 ` Dag Nygren
2002-08-24 21:15 ` Thunder from the hill
2002-08-24 23:03 ` conman
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=1030211284.1935.4991.camel@phantasy \
--to=rml@tech9.net \
--cc=conman@kolivas.net \
--cc=dag@newtech.fi \
--cc=diegocg@teleline.es \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@lightweight.ods.org \
/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
all inboxes | Powered by JetHome®