From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: "Andi Kleen" <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, "Greg KH" <greg@kroah.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: Warning in during hotplug on 2.6.27-rc2-git5
Date: Mon, 18 Aug 2008 18:42:24 +0200 [thread overview]
Message-ID: <200808181842.26099.rjw@sisk.pl> (raw)
In-Reply-To: <6453C3CB8E2B3646B0D020C112613273C5AC7D@sausexmb4.amd.com>
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
prev parent reply other threads:[~2008-08-18 16:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 22:00 Mark Langsdorf
2008-08-14 15:53 ` Rafael J. Wysocki
2008-08-14 16:06 ` Langsdorf, Mark
2008-08-14 16:34 ` Andi Kleen
2008-08-14 18:35 ` Langsdorf, Mark
2008-08-16 19:28 ` Rafael J. Wysocki
2008-08-16 20:18 ` Greg KH
2008-08-16 21:34 ` Rafael J. Wysocki
2008-08-18 15:32 ` Langsdorf, Mark
2008-08-17 2:23 ` Andi Kleen
2008-08-17 17:25 ` Rafael J. Wysocki
2008-08-17 19:23 ` Rafael J. Wysocki
2008-08-17 2:25 ` Andi Kleen
2008-08-17 21:53 ` Rafael J. Wysocki
2008-08-18 13:11 ` Langsdorf, Mark
2008-08-18 14:38 ` Rafael J. Wysocki
2008-08-18 16:29 ` Langsdorf, Mark
2008-08-18 16:42 ` Rafael J. Wysocki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200808181842.26099.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®