[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6453C3CB8E2B3646B0D020C112613273C5AC7D@sausexmb4.amd.com>
Date: Mon, 18 Aug 2008 11:29:15 -0500
From: "Langsdorf, Mark" <mark.langsdorf@....com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
CC: "Andi Kleen" <andi@...stfloor.org>, <linux-kernel@...r.kernel.org>,
"Greg KH" <greg@...ah.com>, "Ingo Molnar" <mingo@...e.hu>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: RE: Warning in during hotplug on 2.6.27-rc2-git5
> > > > 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. It is only failing for CPU4+,
I'm not sure why that would be significant.
> 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.
-Mark Langsdorf
Operating System Research Center
AMD
--
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/
Powered by blists - more mailing lists