From: Steven Rostedt <rostedt@goodmis.org>
To: "Alexander E. Patrakov" <patrakov@gmail.com>
Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: BUG: sleeping function called from invalid context at kernel/mutex.c:271
Date: Wed, 18 Apr 2012 09:48:21 -0400 [thread overview]
Message-ID: <1334756901.28106.38.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1334756757.1269.28.camel@fujitsu-laptop>
On Wed, 2012-04-18 at 19:45 +0600, Alexander E. Patrakov wrote:
> > Do you see the RT throttling message too? That's a bug with an RT task
> > going haywire. If that is happening, an RT task may be preventing an RCU
> > grace period to finish, and causing the RCU stalls.
>
> I am currently at home, writing this from a laptop with 3.3.1, and there
Have you seen the memory leaks on your laptop?
> are no such messages in dmesg (yet?). Also I don't know any RT tasks
> that may run on my computer, except pulseaudio, which has a built-in
There are kernel threads that run at RT priorities too.
> safeguard against this. As for the work computer, should I check
> tomorrow, and with which kernel version?
>
I'm only interested in the kernel version that happens to leak. If other
versions don't leak then we don't need to worry about them ;-)
Perhaps the problem has already been fixed in later kernels.
-- Steve
next prev parent reply other threads:[~2012-04-18 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 7:27 Alexander E. Patrakov
2012-04-18 2:56 ` Steven Rostedt
2012-04-18 4:06 ` Paul E. McKenney
2012-04-18 4:51 ` Alexander E. Patrakov
2012-04-18 12:08 ` Steven Rostedt
2012-04-18 13:45 ` Alexander E. Patrakov
2012-04-18 13:48 ` Steven Rostedt [this message]
2012-04-18 15:21 ` Alexander E. Patrakov
2012-04-18 16:19 ` Alexander E. Patrakov
2012-04-18 13:51 ` Paul E. McKenney
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=1334756901.28106.38.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@gmail.com \
--cc=paulmck@linux.vnet.ibm.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
all inboxes | Powered by JetHome®