From: Christian Hoffmann <email@christianhoffmann.info>
To: paulmck@linux.vnet.ibm.com
Cc: Josh Boyer <jwboyer@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: scheduling while atomic: swapper/0/0x10000002
Date: Mon, 12 Sep 2011 18:43:17 +0200 [thread overview]
Message-ID: <4E6E36A5.2030702@christianhoffmann.info> (raw)
In-Reply-To: <20110910195820.GC4118@linux.vnet.ibm.com>
On 09/10/2011 09:58 PM, Paul E. McKenney wrote:
> On Sat, Sep 10, 2011 at 07:17:53PM +0200, Christian Hoffmann wrote:
>> On 09/10/2011 06:44 PM, Josh Boyer wrote:
>>> On Sat, Sep 10, 2011 at 9:29 AM, Christian Hoffmann
>>> <email@christianhoffmann.info> wrote:
>>>> Hi,
>>>>
>>>> I can see the following bug report in the kernel 3.1 rc5 dmesg:
>>>>
>>>> [ 0.000008] BUG: scheduling while atomic: swapper/0/0x10000002
>>>> [ 0.000012] Modules linked in:
>>>> [ 0.000015] Pid: 0, comm: swapper Not tainted 3.1.0-rc5-ch+ #2
>>>> [ 0.000017] Call Trace:
>>>> [ 0.000024] [<ffffffff81052cb6>] __schedule_bug+0x66/0x70
>>>> [ 0.000028] [<ffffffff8160329d>] schedule+0x99d/0x9b0
>>>> [ 0.000032] [<ffffffff81cf22b5>] ? pidmap_init+0x9f/0xdf
>>>> [ 0.000035] [<ffffffff8105cc7a>] __cond_resched+0x2a/0x40
>>>> [ 0.000038] [<ffffffff81603541>] _cond_resched+0x31/0x40
>>>> [ 0.000041] [<ffffffff8115fb63>] kmem_cache_alloc_trace+0x53/0x160
>>>> [ 0.000043] [<ffffffff81cf22b5>] pidmap_init+0x9f/0xdf
>>>> [ 0.000046] [<ffffffff81cd9b8a>] start_kernel+0x333/0x3c8
>>>> [ 0.000049] [<ffffffff81cd9347>] x86_64_start_reservations+0x132/0x136
>>>> [ 0.000051] [<ffffffff81cd944c>] x86_64_start_kernel+0x101/0x110
>>>
>>> Paul McKenney has a patch that solves this oops. You can find it here:
>>>
>>> http://marc.info/?l=linux-kernel&m=131537669921538&w=2
>>>
>>> We had discussed getting this into 3.1, but apparently that didn't
>>> happen (yet?). I thought it had been sent upstream with my tested-by,
>>> but I don't see it included in Linus' tree.
>>
>> Hi,
>>
>> the patch up there doesn't seem to apply cleanly to 3.1 rc5, as it
>> misses the rename done in "[PATCH tip/core/rcu 23/55] rcu: Simplify
>> quiescent-state accounting"
>> (http://marc.info/?l=linux-kernel&m=131537654621392&w=2).
>
> For 3.1-rc5, you will be wanting this one:
>
> https://lkml.org/lkml/2011/8/19/355
Hi,
yes, this applies and makes the stack disappear.
Thanks,
Chris
next prev parent reply other threads:[~2011-09-12 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 13:29 scheduling while atomic: swapper/0/0x10000002 Christian Hoffmann
2011-09-10 16:44 ` Josh Boyer
2011-09-10 17:17 ` Christian Hoffmann
2011-09-10 19:58 ` Paul E. McKenney
2011-09-12 16:43 ` Christian Hoffmann [this message]
2011-09-12 17:16 ` 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=4E6E36A5.2030702@christianhoffmann.info \
--to=email@christianhoffmann.info \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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