Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751889Ab2HRRuZ (ORCPT ); Sat, 18 Aug 2012 13:50:25 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:36806 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750903Ab2HRRuW (ORCPT ); Sat, 18 Aug 2012 13:50:22 -0400 MIME-Version: 1.0 In-Reply-To: <1344862344-27434-1-git-send-email-chenhc@lemote.com> References: <1344862344-27434-1-git-send-email-chenhc@lemote.com> Date: Sat, 18 Aug 2012 10:50:20 -0700 Message-ID: Subject: Re: [PATCH V2] MIPS: Fix poweroff failure when HOTPLUG_CPU configured. From: Kevin Cernekee To: Linux MIPS Mailing List , Ralf Baechle Cc: linux-kernel@vger.kernel.org, Fuxin Zhang , Zhangjin Wu , Hongliang Tao , Hua Yan , Yong Zhang , stable@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1300 Lines: 28 On Mon, Aug 13, 2012 at 5:52 AM, Huacai Chen wrote: > When poweroff machine, kernel_power_off() call disable_nonboot_cpus(). > And if we have HOTPLUG_CPU configured, disable_nonboot_cpus() is not an > empty function but attempt to actually disable the nonboot cpus. Since > system state is SYSTEM_POWER_OFF, play_dead() won't be called and thus > disable_nonboot_cpus() hangs. Therefore, we make this patch to avoid > poweroff failure. I have seen the same problem; sometimes it causes a kernel oops too. > #ifdef CONFIG_HOTPLUG_CPU > - if (!cpu_online(cpu) && !cpu_isset(cpu, cpu_callin_map) && > - (system_state == SYSTEM_RUNNING || > - system_state == SYSTEM_BOOTING)) > + if (!cpu_online(cpu) && !cpu_isset(cpu, cpu_callin_map)) > play_dead(); This fix works for me. Acked-by: Kevin Cernekee I do see SMP boot problems ("Attempted to kill the idle task!" panic) on a 4-way box if the !cpu_isset() check is removed. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/