From: Andi Kleen <andi@firstfloor.org>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
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: Sun, 17 Aug 2008 04:25:58 +0200 [thread overview]
Message-ID: <20080817022558.GO19125@one.firstfloor.org> (raw)
In-Reply-To: <6453C3CB8E2B3646B0D020C112613273C5AC71@sausexmb4.amd.com>
> 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?
Mark, can you please put a printk
printk("mce_cpu_callback action %lu cpu %u\n", action, cpu);
into arch/x86/kernel/cpu/mcheck/mce_64.c:mce_cpu_callback()
and post the log including the warning?
That would verify my theory.
-Andi
next prev parent reply other threads:[~2008-08-17 2:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 22:00 Warning in during hotplug on 2.6.27-rc2-git5 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 [this message]
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
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=20080817022558.GO19125@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.