| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 22 Dec 2009 18:20:31 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Pedro Ribeiro <pedrib@...il.com> Cc: linux-kernel@...r.kernel.org, Nigel Cunningham <nigel@...onice.net> Subject: Re: WARN_ON at line 380 in kernel/smp.c under 2.6.32.2 + TuxOnIce + KDB 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists