From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: INFO: suspicious RCU usage. on 3.3.0-rc7-next-20120316
Date: Sun, 18 Mar 2012 10:42:33 -0700 [thread overview]
Message-ID: <4F661E89.5050000@gmail.com> (raw)
In-Reply-To: <20120318155401.GA8045@dhcp-172-17-108-109.mtv.corp.google.com>
On 03/18/2012 08:54 AM, Tejun Heo wrote:
> On Sun, Mar 18, 2012 at 08:36:26AM -0700, Justin P. Mattock wrote:
>> with the current linux-next I am seeing this in dmesg..:
>>
>> [ 3.643089] isapnp: No Plug& Play device found
>> [ 3.643690] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
>> [ 3.673061]
>> [ 3.699307] ===============================
>> [ 3.725757] [ INFO: suspicious RCU usage. ]
>> [ 3.752134] 3.3.0-rc7-next-20120316 #1 Not tainted
>> [ 3.778508] -------------------------------
>> [ 3.778510] kernel/cgroup.c:1719 suspicious
>> rcu_dereference_check() usage!
>> [ 3.778512]
>> [ 3.778512] other info that might help us debug this:
>> [ 3.778513]
>> [ 3.778515]
>> [ 3.778515] rcu_scheduler_active = 1, debug_locks = 1
>> [ 3.778517] no locks held by swapper/0/1.
>> [ 3.778517]
>> [ 3.778518] stack backtrace:
>> [ 3.778519] Pid: 1, comm: swapper/0 Not tainted
>> 3.3.0-rc7-next-20120316 #1
>> [ 3.778521] Call Trace:
>> [ 3.778528] [<c158cc21>] ? printk+0x1d/0x1f
>> [ 3.778534] [<c10a822a>] lockdep_rcu_suspicious+0xca/0x100
>> [ 3.778536] [<c10bedea>] cgroup_path+0x17a/0x1c0
>
> Known problem. The following pending patchset should fix the problem.
>
> http://thread.gmane.org/gmane.linux.kernel/1263989
>
> Jens?
>
> Thakns.
>
cool thanks for the info..
I went and applied your patches(all 5) and there is fuzz, and some
errors with linux-next.
seems the suspicious message is still there, but the system boots up
just fine with the patches in.
maybe manually applying them by hand is what I need to do for -next so
I dont miss anything important with the patch that takes care of the
suspicious message.
Justin P. Mattock
next prev parent reply other threads:[~2012-03-18 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 15:36 INFO: suspicious RCU usage. on 3.3.0-rc7-next-20120316 Justin P. Mattock
2012-03-18 15:54 ` Tejun Heo
2012-03-18 17:42 ` Justin P. Mattock [this message]
2012-03-19 17:01 ` Tejun Heo
2012-03-20 6:04 ` Justin P. Mattock
[not found] ` <CAKFRV=N5cF7MTuSpOjySmGgJNnW2b1tBZeF5W4XckA7dMSXysg@mail.gmail.com>
2012-03-23 4:23 ` Justin P. Mattock
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=4F661E89.5050000@gmail.com \
--to=justinmattock@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.