From: Peter Zijlstra <peterz@infradead.org>
To: Pedro Ribeiro <pedrib@gmail.com>
Cc: linux-kernel@vger.kernel.org, Nigel Cunningham <nigel@tuxonice.net>
Subject: Re: WARN_ON at line 380 in kernel/smp.c under 2.6.32.2 + TuxOnIce + KDB
Date: Tue, 22 Dec 2009 18:20:31 +0100 [thread overview]
Message-ID: <1261502431.4937.38.camel@laptop> (raw)
In-Reply-To: <74fd948d0912220851v354b1704xa55fc3c88e1c300c@mail.gmail.com>
On Tue, 2009-12-22 at 16:51 +0000, Pedro Ribeiro wrote:
> Hi all,
>
> I've been asked by Nigel Cunningham of TuxOnIce to forward this bug here.
>
> While resuming from hibernate (using TuxOnIce) I'm seeing the WARN_ON
> at line 380 in kernel/smp.c trigger from a kmap_high call right after
> secondary processors have been brought down (the previous message is
> "CPU1 is down").
>
> I only have pictures of the backtrace (readable but not very good
> quality, sorry).
> http://img51.imageshack.us/img51/2312/stacktrace1.jpg
> http://img195.imageshack.us/img195/3646/stacktrace2.jpg
>
> At first I thought this was related to my battery saving script
> messing with /proc/sys/vm/dirty_writeback_centisecs, but I'm not sure
> right now, it still happens with the default value, so I'm clueless.
>
> Mind you, this does not impede the resume - it just dumps this stack
> trace and continues resuming happily.
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.
next prev parent reply other threads:[~2009-12-22 17:20 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 [this message]
2009-12-22 19:16 ` Pedro Ribeiro
2009-12-22 19:27 ` Peter Zijlstra
2009-12-22 21:58 ` Nigel Cunningham
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=1261502431.4937.38.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@tuxonice.net \
--cc=pedrib@gmail.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