From: Nigel Cunningham <nigel@tuxonice.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Pedro Ribeiro <pedrib@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: WARN_ON at line 380 in kernel/smp.c under 2.6.32.2 + TuxOnIce + KDB
Date: Wed, 23 Dec 2009 08:58:00 +1100 [thread overview]
Message-ID: <4B3140E8.5080104@tuxonice.net> (raw)
In-Reply-To: <1261510020.4937.73.camel@laptop>
Hi.
Peter Zijlstra wrote:
> On Tue, 2009-12-22 at 19:16 +0000, Pedro Ribeiro wrote:
>> On Tue, Dec 22, 2009 at 5:20 PM, Peter Zijlstra <peterz@infradead.org> wrote:
>
>>> If you'd enable frame pointers the strack traces would be clearer, but
>>> it looks like a bug in tux on ice, doing kmap_high() with IRQs disabled
>>> or something like that.
>
>> I enabled frame pointers, is this more useful?
>> http://img684.imageshack.us/img684/5118/dsc01206m.jpg
>> http://img96.imageshack.us/img96/5493/dsc01207k.jpg
>> http://img33.imageshack.us/img33/7470/dsc01208lp.jpg
>
> Those read more clearly indeed, thanks!
>
> It really looks like what I said above, in that tux on ice is calling
> kmap() from an inappropriate context.
Ah, I know now what's going on now. You're right. In working around a
reported problem, I've triggered the warning. I'll give it some more
consideration.
Nigel
next prev parent reply other threads:[~2009-12-22 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 16:51 WARN_ON at line 380 in kernel/smp.c under 2.6.32.2 + TuxOnIce + KDB Pedro Ribeiro
2009-12-22 17:20 ` Peter Zijlstra
2009-12-22 19:16 ` Pedro Ribeiro
2009-12-22 19:27 ` Peter Zijlstra
2009-12-22 21:58 ` Nigel Cunningham [this message]
2010-01-27 23:03 ` Nigel Cunningham
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=4B3140E8.5080104@tuxonice.net \
--to=nigel@tuxonice.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pedrib@gmail.com \
--cc=peterz@infradead.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