linux-kernel - Re: [migration_cpu_stop] WARNING: CPU: 0 PID: 11 at kernel/sched/core.c:1187 set_task

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: <20171121133403.GH3165@worktop.lehotels.local>
Date:   Tue, 21 Nov 2017 14:34:03 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Fengguang Wu <fengguang.wu@...el.com>
Cc:     Jiri Olsa <jolsa@...hat.com>, Ingo Molnar <mingo@...hat.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        Luca Abeni <luca.abeni@...tannapisa.it>,
        Tejun Heo <tj@...nel.org>,
        Matt Fleming <matt@...eblueprint.co.uk>,
        Nicolas Pitre <nicolas.pitre@...aro.org>,
        linux-kernel@...r.kernel.org, lkp@...org,
        "Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: [migration_cpu_stop] WARNING: CPU: 0 PID: 11 at
 kernel/sched/core.c:1187 set_task_cpu+0x257/0x6b6

On Tue, Nov 21, 2017 at 08:04:20PM +0800, Fengguang Wu wrote:
> Hello,
> 
> FYI this happens in mainline kernel 4.14.0-00902-g43ff2f4.
> It happens since 4.13.
> 
> It occurs in 7 out of 36 boots.
> 
> [   58.171538] no ifx modem active;
> [   58.211860] ACPI: Preparing to enter system sleep state S5
> [   58.216823] reboot: Power down
> [   58.244526] acpi_power_off called
> [   61.460467] ------------[ cut here ]------------
> [   61.465481] WARNING: CPU: 0 PID: 11 at kernel/sched/core.c:1187 set_task_cpu+0x257/0x6b6:
> 						set_task_cpu at kernel/sched/core.c:1187

Never seen that before.. but I can't even figure out how CPUs end up
offline in that reboot path :/

So far I just get lost in the callback maze... Rafael any clues?