From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Giangiacomo Mariotti <gg.mariotti@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [HW PROBLEM] Intel I7 MCE. Erratum or not?
Date: Mon, 08 Dec 2008 16:42:28 +0900 [thread overview]
Message-ID: <493CCFE4.2080802@jp.fujitsu.com> (raw)
In-Reply-To: <12bfabe40812072248n3c931ce0hf030b3ac758026d4@mail.gmail.com>
Giangiacomo Mariotti wrote:
> I noticed something else, which though may be due to my inexperience
> with mce messages. In my directory /sys/devices/system/machinecheck
> there are machinecheck0-7(one for each logical cpu of my system I
> presume). Having received the MCE log always for cpu 0, I went to look
> inside dir machinecheck0 and I found bank0-5ctl. So now my question
> is, why do I receive MCE logs about bank 6, if my cpus don't have a
> bank 6? Does that count start from 1? Or am I missing something else?
Answer would be in the following commit:
> commit 8edc5cc5ec880c96de8e6686fb0d7a5231e91c05
> Author: Venki Pallipadi <venkatesh.pallipadi@intel.com>
> Date: Mon May 12 15:43:34 2008 +0200
>
> x86: remove 6 bank limitation in 64 bit MCE reporting code
(snip)
> The patch below does not create sysfs control (bankNctl) for banks
> higher than 6 as well. That needs some pre-cleanup in /sysfs mce layout,
> removal of per cpu /sysfs entries for bankctl as they are really global
> system level control today. That change will follow. This basic change
> is critical to report the detailed errors on banks higher than 6.
So there are 6 sysfs control(bank0-5ctl) even if your cpu have more banks.
Old kernel with bank limitation will say:
"MCE: warning: using only %d banks\n"
And it seems that old kernel will ignore records in banks higher than 6.
Thanks,
H.Seto
next prev parent reply other threads:[~2008-12-08 7:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 12:21 [HW PROBLEM] Intel I7 MCE. Erratum or not? Giangiacomo Mariotti
2008-12-06 20:58 ` Robert Hancock
2008-12-06 21:43 ` Giangiacomo Mariotti
2008-12-06 21:47 ` Robert Hancock
2008-12-06 22:16 ` Giangiacomo Mariotti
2008-12-07 3:25 ` Robert Hancock
2008-12-07 3:42 ` Giangiacomo Mariotti
2008-12-07 21:55 ` Giangiacomo Mariotti
2008-12-07 22:13 ` Arjan van de Ven
2008-12-07 23:21 ` Giangiacomo Mariotti
2008-12-08 6:48 ` Giangiacomo Mariotti
2008-12-08 7:42 ` Hidetoshi Seto [this message]
2008-12-08 8:04 ` Giangiacomo Mariotti
2008-12-08 9:36 ` Hidetoshi Seto
2008-12-08 9:56 ` Andi Kleen
2008-12-08 10:02 ` Eric Dumazet
2008-12-08 10:18 ` Andi Kleen
2008-12-08 10:26 ` Hidetoshi Seto
2008-12-08 10:53 ` Giangiacomo Mariotti
2008-12-08 11:10 ` Hidetoshi Seto
2008-12-08 11:16 ` Giangiacomo Mariotti
2008-12-08 12:04 ` Andi Kleen
2008-12-08 12:37 ` Giangiacomo Mariotti
2008-12-09 5:54 ` Giangiacomo Mariotti
2008-12-09 11:31 ` Andi Kleen
2008-12-09 11:57 ` Giangiacomo Mariotti
2008-12-15 20:59 ` Giangiacomo Mariotti
[not found] ` <alpine.DEB.1.10.0812081314010.18782@uplift.swm.pp.se>
[not found] ` <493D296B.1080205@linux.intel.com>
[not found] ` <alpine.DEB.1.10.0812081724080.18782@uplift.swm.pp.se>
[not found] ` <493D6FB4.9090909@linux.intel.com>
[not found] ` <alpine.DEB.1.10.0812082145410.18782@uplift.swm.pp.se>
[not found] ` <12bfabe40812082146r3ea000em7a8f725101a50bd5@mail.gmail.com>
[not found] ` <alpine.DEB.1.10.0812090737410.18782@uplift.swm.pp.se>
2008-12-09 7:37 ` OFFLIST " Giangiacomo Mariotti
[not found] ` <12bfabe40812082319x4ed6c9m5b744e51cdd3d838@mail.gmail.com>
[not found] ` <alpine.DEB.1.10.0812090857590.18782@uplift.swm.pp.se>
2008-12-09 8:30 ` Giangiacomo Mariotti
2008-12-09 8:34 ` Giangiacomo Mariotti
2008-12-08 10:26 ` Giangiacomo Mariotti
2008-12-08 10:57 ` Hidetoshi Seto
2008-12-08 11:14 ` Giangiacomo Mariotti
2008-12-06 22:37 ` Giangiacomo Mariotti
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=493CCFE4.2080802@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=ak@linux.intel.com \
--cc=arjan@infradead.org \
--cc=gg.mariotti@gmail.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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 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.