From: Thomas Gleixner <tglx@linutronix.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Ingo Molnar <mingo@elte.hu>,
Fabio Comolli <fabio.comolli@gmail.com>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
mingo@redhat.com, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.17-mm5: lockdep prevents suspend to disk
Date: Wed, 05 Jul 2006 00:05:28 +0200 [thread overview]
Message-ID: <1152050728.24611.59.camel@localhost.localdomain> (raw)
In-Reply-To: <20060704212910.GA11872@elf.ucw.cz>
On Tue, 2006-07-04 at 23:29 +0200, Pavel Machek wrote:
> Hi!
>
> > > > Jul 4 21:48:08 tycho kernel: rt-test-4
> > > > Jul 4 21:48:08 tycho kernel: rt-test-5
> > > > Jul 4 21:48:08 tycho kernel: rt-test-6
> > > > Jul 4 21:48:08 tycho kernel: rt-test-7
> > >
> > > Are rt-test-X tasks kernel threads or userspace programs? (Kernel
> > > threads need explicit try_to_freeze in them to allow suspend).
> > >
> > > Are they normally killable?
> >
> > hm, that's not lockdep but due to CONFIG_RT_MUTEX_TESTER.
>
> I'm pretty sure RT_MUTEX_TESTER is the problem, then. It should either
> end its threads when testing is no longer needed, or maybe add
The tests are stimulated from userspace, we need the kernel threads to
test the correctness of the PI bits in the kernel. So we don't know when
the tests are done.
> try_to_freeze() somewhere inside so that those threads can be frozen.
will look into it tomorrow.
tglx
next prev parent reply other threads:[~2006-07-04 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 19:58 2.6.17-mm5: lockdep prevents suspend to disk Fabio Comolli
2006-07-04 18:32 ` Pavel Machek
2006-07-04 21:08 ` Ingo Molnar
2006-07-04 21:29 ` Pavel Machek
2006-07-04 22:05 ` Thomas Gleixner [this message]
2006-07-04 20:21 ` Ingo Molnar
2006-07-04 18:30 ` Pavel Machek
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=1152050728.24611.59.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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