Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754516AbYHRQjW (ORCPT ); Mon, 18 Aug 2008 12:39:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751696AbYHRQjO (ORCPT ); Mon, 18 Aug 2008 12:39:14 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:45858 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751418AbYHRQjO (ORCPT ); Mon, 18 Aug 2008 12:39:14 -0400 From: "Rafael J. Wysocki" To: "Langsdorf, Mark" Subject: Re: Warning in during hotplug on 2.6.27-rc2-git5 Date: Mon, 18 Aug 2008 18:42:24 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: "Andi Kleen" , linux-kernel@vger.kernel.org, "Greg KH" , "Ingo Molnar" , "Andrew Morton" References: <200808141753.58547.rjw@sisk.pl> <200808181638.37707.rjw@sisk.pl> <6453C3CB8E2B3646B0D020C112613273C5AC7D@sausexmb4.amd.com> In-Reply-To: <6453C3CB8E2B3646B0D020C112613273C5AC7D@sausexmb4.amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200808181842.26099.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1297 Lines: 34 On Monday, 18 of August 2008, Langsdorf, Mark wrote: > > > > > I'm still seeing it on 2.6.27-rc2, even with the > > > > > patch here http://lkml.org/lkml/2008/7/30/171 and the > > > > > wbinvd_halt code patch applied. Maybe something else > > > > > broke in some of the recent hotplug changes? > > > > I have a couple of questions, then: > > - Does it fail identically for all CPUs or for CPU4 and above only? > > - Did previous kernels, most importantly 2.6.26, work correctly? > > It turns out 2.6.26 also fails. OK, so I'll drop the bug from the list of recent regressions. > It is only failing for CPU4+, I'm not sure why that would be significant. Because I cannot reproduce it on a single-socket AMD quad-core. :-) > > Also, can you please attach dmesg output, including the > > offlining of a CPU that would later lead to the problem > > with cpu_up(), to the Bugzilla entry at > > http://bugzilla.kernel.org/show_bug.cgi?id=11337 ? > > I did. Thanks. I think we can further debug this using Bugzilla if you don't mind. Best, 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/