Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757338AbXI1NaT (ORCPT ); Fri, 28 Sep 2007 09:30:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750878AbXI1NaG (ORCPT ); Fri, 28 Sep 2007 09:30:06 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:46720 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750743AbXI1NaE (ORCPT ); Fri, 28 Sep 2007 09:30:04 -0400 From: "Rafael J. Wysocki" To: Mark Lord Subject: Re: Problems with SMP & ACPI powering off Date: Fri, 28 Sep 2007 15:44:29 +0200 User-Agent: KMail/1.9.5 Cc: Len Brown , Linux Kernel , simon.derr@bull.net References: <46FC20B7.4000606@rtr.ca> <200709281455.29069.rjw@sisk.pl> <46FD001A.3070309@rtr.ca> In-Reply-To: <46FD001A.3070309@rtr.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709281544.30497.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1515 Lines: 37 On Friday, 28 September 2007 15:22, Mark Lord wrote: > Rafael J. Wysocki wrote: > > On Friday, 28 September 2007 06:57, Len Brown wrote: > >> On Thursday 27 September 2007 18:00, Rafael J. Wysocki wrote: > >>> On Thursday, 27 September 2007 23:29, Mark Lord wrote: > >>>> Question: do we disable all CPUs except 0 when doing ACPI power off? > >>> No, but we should. > >> We used to. > >> It is absolutely mandatory -- else it confuses the BIOS on some boards > >> b/c it isn't expecting SMM to get entered from other than cpu0. > > > > Can we use the CPU hotplug for that, like in the suspend/hibernation case? > > Well, so far it's working: about ten poweroffs since I patched it, > and no issues with any of them. Prior to that, it seemed like about > one in five poweroffs wouldn't (power off). > > It'll take a lot more testing to confirm, though. > > What can I call to determine if more than one CPU is enabled, anyway? > > Here's the hack I'm using here, very situation (2 cores) specific, > and it still has some printk's leftover with a sleep so I have time > to read them before the lights go out. :) Well, we have disable_nonboot_cpus() that we use for suspend and that is supposed to be general. The question is when to call it. Greetings, Rafael - 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/