From: Thomas Gleixner <tglx@linutronix.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [ANNOUNCE] 3.0-rt4
Date: Thu, 28 Jul 2011 21:36:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1107282123380.2660@ionos> (raw)
In-Reply-To: <4E31B59F.1000607@localhost>
On Thu, 28 Jul 2011, Fernando Lopez-Lezcano wrote:
> On 07/27/2011 02:37 PM, Thomas Gleixner wrote:
> > Dear RT Folks,
> >
> > I'm pleased to announce the 3.0-rt4 release.
>
> Testing rt5 (lenovo dual core laptop running fc15, kernel based on koji's
> 3.0.0 build plus rt5)...
> ----
> [ 0.000000] =============================================
> [ 0.000000] [ INFO: possible recursive locking detected ]
> [ 0.000000] 3.0.0-1.rt5.1.fc15.ccrma.i686.rtPAE #1
> [ 0.000000] ---------------------------------------------
> [ 0.000000] swapper/0 is trying to acquire lock:
> [ 0.000000] (&parent->list_lock){+.+...}, at: [<c04fb406>]
> __cache_free+0x43/0xc3
> [ 0.000000]
> [ 0.000000] but task is already holding lock:
> [ 0.000000] (&parent->list_lock){+.+...}, at: [<c04fc538>]
> do_tune_cpucache+0xf2/0x2bb
> [ 0.000000]
> [ 0.000000] other info that might help us debug this:
> [ 0.000000] Possible unsafe locking scenario:
> [ 0.000000]
> [ 0.000000] CPU0
> [ 0.000000] ----
> [ 0.000000] lock(&parent->list_lock);
> [ 0.000000] lock(&parent->list_lock);
That's a know issue. Fix is being worked on. I can't find the thread
right now, but it's weird some interaction of debug options
(DEBUG_OBJECTS, DEBUG_SLAB ...) Peter ???
> (I guess because HIGHMEM is disabled the computer only finds 800M+ of LOWMEM
> and that is all top reports - total installed is 4G)
Yes, that's the state for now until someone fixes it :)
Thanks,
tglx
next prev parent reply other threads:[~2011-07-28 19:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 21:37 [ANNOUNCE] 3.0-rt4 Thomas Gleixner
2011-07-27 21:57 ` Frank Rowand
2011-07-27 22:05 ` Thomas Gleixner
2011-07-27 22:27 ` Frank Rowand
2011-07-28 7:33 ` Nikita V. Youshchenko
2011-07-28 8:06 ` Thomas Gleixner
2011-07-28 8:24 ` Nikita V. Youshchenko
2011-07-28 8:44 ` Peter Zijlstra
2011-07-28 8:51 ` Nikita V. Youshchenko
2011-07-28 9:37 ` Thomas Gleixner
2011-07-28 8:43 ` Peter Zijlstra
2011-07-28 9:41 ` Yong Zhang
2011-07-28 9:49 ` Thomas Gleixner
2011-07-28 11:22 ` N, Mugunthan V
2011-07-28 11:36 ` Thomas Gleixner
2011-07-28 15:59 ` hermann
2011-07-28 17:41 ` Paul E. McKenney
2011-07-28 17:43 ` Thomas Gleixner
2011-07-28 18:32 ` Paul E. McKenney
2011-07-28 19:05 ` Thomas Gleixner
2011-07-28 19:34 ` Paul E. McKenney
2011-07-28 20:29 ` Paul E. McKenney
2011-07-28 17:42 ` Jason Wessel
2011-07-28 17:49 ` Thomas Gleixner
2011-07-28 19:16 ` Fernando Lopez-Lezcano
2011-07-28 19:36 ` Thomas Gleixner [this message]
2011-07-29 0:13 ` Fernando Lopez-Lezcano
2011-07-28 21:22 ` Peter Zijlstra
2011-07-28 22:55 ` Pekka Enberg
2011-07-29 0:17 ` Fernando Lopez-Lezcano
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=alpine.LFD.2.02.1107282123380.2660@ionos \
--to=tglx@linutronix.de \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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