linux-kernel - Re: Warnings about tasks on CPU 1 during STR

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1264423859.4283.1725.camel@laptop>
Date:	Mon, 25 Jan 2010 13:50:59 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Warnings about tasks on CPU 1 during STR

On Mon, 2010-01-25 at 05:42 +0100, Frans Pop wrote:
> With 2.6.33-rc5 during suspend to RAM I'm getting a bunch of warnings
> I've not seen with earlier kernel versions:
> 
> PM: late suspend of devices complete after 28.784 msecs
> ACPI: Preparing to enter system sleep state S3
> Disabling non-boot CPUs ...
> CPU 1 is now offline
> SMP alternatives: switching to UP code
> Task events/1 (pid = 10) is on cpu 1 (state = 1, flags = 84208040)
> Task khelper (pid = 11) is on cpu 1 (state = 1, flags = 80208040)
> Task sync_supers (pid = 77) is on cpu 1 (state = 1, flags = 80208040)
> Task bdi-default (pid = 79) is on cpu 1 (state = 2, flags = 80a15040)
> Task kblockd/1 (pid = 81) is on cpu 1 (state = 1, flags = 84208040)
> [...]
> Task pm-suspend (pid = 29782) is on cpu 1 (state = 2, flags = 414000)
> Extended CMOS year: 2000
> Back to C!
> 
> All the "Task X is on cpu 1" messages (76 in total) are new. Bug or
> intentional? As it is a warning, I suspect a bug.

http://lkml.org/lkml/2010/1/21/175

--
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/