From: Andi Kleen <ak@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Ming Lei <tom.leiming@gmail.com>,
Djalal Harouni <tixxdz@opendz.org>,
Borislav Petkov <borislav.petkov@amd.com>,
Tony Luck <tony.luck@intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
Kay Sievers <kay.sievers@vrfy.org>,
gouders@et.bocholt.fh-gelsenkirchen.de,
Marcos Souza <marcos.mage@gmail.com>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"tglx@linutronix.de" <tglx@linutronix.de>,
prasad@linux.vnet.ibm.com, justinmattock@gmail.com,
Jeff Chua <jeff.chua.linux@gmail.com>
Subject: Re: x86/mce: machine check warning during poweroff
Date: Fri, 13 Jan 2012 15:13:52 -0800 [thread overview]
Message-ID: <4F10BAB0.70308@linux.intel.com> (raw)
In-Reply-To: <4F10A0FD.9040504@linux.intel.com>
> Assuming the problem is with the multiple devices (not fully sure):
>
> The redundant devices don't make much sense anyways, they are all
> mirrors of each other
> (state changes always affect all CPUs) Could just collapse down to a
> single device and symlink
> the others.
Checking again it seems like the AMD threshold code reports per CPU
counters so it would
still need per CPU devices.
All the other code is just a single instance I believe and doesn't
actually need all the
complicated per CPU code.
-Andi
next prev parent reply other threads:[~2012-01-13 23:13 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 0:00 x86/mce: machine check warning during poweroff Djalal Harouni
2012-01-12 14:22 ` Ming Lei
2012-01-13 20:22 ` Srivatsa S. Bhat
2012-01-13 20:34 ` Justin P. Mattock
2012-01-13 20:37 ` Linus Torvalds
2012-01-13 20:53 ` Srivatsa S. Bhat
2012-01-13 21:08 ` Linus Torvalds
2012-01-13 21:24 ` Andi Kleen
2012-01-13 21:38 ` Justin P. Mattock
2012-01-13 22:06 ` Srivatsa S. Bhat
2012-01-13 22:17 ` Alan Stern
2012-01-13 22:18 ` Srivatsa S. Bhat
2012-01-13 23:13 ` Andi Kleen [this message]
2012-01-14 0:44 ` Dirk Gouders
2012-01-13 23:02 ` Linus Torvalds
2012-01-13 23:27 ` Srivatsa S. Bhat
2012-01-14 0:05 ` Linus Torvalds
2012-01-14 2:41 ` Srivatsa S. Bhat
2012-01-14 2:53 ` Linus Torvalds
2012-01-14 3:05 ` Srivatsa S. Bhat
2012-01-14 3:10 ` Linus Torvalds
2012-01-14 3:18 ` Srivatsa S. Bhat
2012-01-14 3:41 ` Linus Torvalds
2012-01-14 5:15 ` Tony Luck
2012-01-14 14:49 ` Greg KH
2012-01-14 16:30 ` Alan Stern
2012-01-14 20:45 ` Jeff Chua
2012-01-15 2:05 ` Tony Luck
2012-01-15 2:34 ` Greg KH
2012-01-15 3:36 ` Alan Stern
2012-01-16 18:15 ` Greg KH
2012-01-16 18:11 ` Greg KH
2012-01-16 18:27 ` Luck, Tony
2012-01-16 18:34 ` Greg KH
2012-01-16 18:42 ` Kay Sievers
2012-01-17 2:21 ` Suresh Siddha
2012-01-17 9:52 ` Srivatsa S. Bhat
2012-01-17 16:15 ` Jeff Chua
2012-01-17 16:36 ` Srivatsa S. Bhat
2012-01-18 3:17 ` Suresh Siddha
2012-01-18 10:19 ` Srivatsa S. Bhat
2012-01-18 13:15 ` Srivatsa S. Bhat
2012-01-18 13:32 ` Sergey Senozhatsky
2012-01-18 22:08 ` Suresh Siddha
2012-01-19 7:50 ` Sergey Senozhatsky
2012-01-19 12:02 ` Srivatsa S. Bhat
2012-01-20 2:28 ` Suresh Siddha
2012-01-23 8:43 ` Peter Zijlstra
2012-01-26 20:27 ` [tip:sched/urgent] sched/nohz: Fix nohz cpu idle load balancing state with cpu hotplug tip-bot for Suresh Siddha
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=4F10BAB0.70308@linux.intel.com \
--to=ak@linux.intel.com \
--cc=borislav.petkov@amd.com \
--cc=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=gregkh@suse.de \
--cc=jeff.chua.linux@gmail.com \
--cc=justinmattock@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcos.mage@gmail.com \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.com \
--cc=rjw@sisk.pl \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=tixxdz@opendz.org \
--cc=tom.leiming@gmail.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).