From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Aristeu Rozanski <aris@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [sb_edac] 50d1bb93672: EDAC sbridge: ECC is disabled. Aborting
Date: Wed, 7 Jan 2015 08:27:14 -0200 [thread overview]
Message-ID: <20150107082714.65fcdddf@concha.lan> (raw)
In-Reply-To: <1420616586.6201.74.camel@intel.com>
Em Wed, 07 Jan 2015 15:43:06 +0800
Huang Ying <ying.huang@intel.com> escreveu:
> On Mon, 2015-01-05 at 09:06 -0500, Aristeu Rozanski wrote:
> > Hi,
> > On Fri, Dec 19, 2014 at 01:26:59PM +0800, Huang Ying wrote:
> > > In fact, I am not complaining :-), just FYI. As I said, this may be a
> > > expected behavior because this is a Haswell machine and the Haswell
> > > support was added in this patch.
> > >
> > > > From the above, what looks weird, from EDAC driver PoV, is:
> > > > [ 12.506298] EDAC sbridge: ECC is disabled. Aborting
> > >
> > > This is what I want help from you to confirm whether it is abnormal.
> > >
> > > > Does it used to work before? If so, was there any BIOS setting change?
> > > > Does the memories used on this machine have ECC?
> > >
> > > This is a high-end desktop, there is something as below in dmidecode
> > > output. Is there some other way to tell whether the memories have ECC?
> > >
> > > Handle 0x0018, DMI type 16, 23 bytes
> > > Physical Memory Array
> > > Location: System Board Or Motherboard
> > > Use: System Memory
> > > Error Correction Type: Multi-bit ECC
> > > Maximum Capacity: 128 GB
> > > Error Information Handle: Not Provided
> > > Number Of Devices: 4
> > >
> > > Handle 0x001A, DMI type 17, 34 bytes
> > > Memory Device
> > > Array Handle: 0x0018
> > > Error Information Handle: Not Provided
> > > Total Width: 72 bits
> > > Data Width: 72 bits
> > > Size: 8192 MB
> > > Form Factor: DIMM
> > > Set: None
> > > Locator: DIMM_A1
> > > Bank Locator: CPU 0
> > > Type: <OUT OF SPEC>
> > > Type Detail: Synchronous
> > > Speed: 1067 MHz
> > > Manufacturer: 0x11
> > > Serial Number: Unknown
> > > Asset Tag: Unknown
> > > Part Number: Unknown
> > > Rank: 1
> > > Configured Clock Speed: Unknown
> >
> > unfortunately with this I can't say :(
> > Do you mind checking on EFI or maybe looking at the memory modules' part
> > number?
>
> Do not find memory modules' part number in EFI menu. Some information
> about memory is:
>
> 2133MT/s Micron DRx8 8GB UDIMM
This doesn't help much. You'll need then to open your machine and check
the model number there physically at the DIMMs.
Also, you need to check if the specific CPU model that you have supports
ECC or not. Not sure about Haswell, but, on Sandy Bridge, not all CPU
models support it.
Regards,
Mauro
>
> Best Regards,
> Huang, Ying
>
>
--
Cheers,
Mauro
next prev parent reply other threads:[~2015-01-07 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 8:13 [LKP] [sb_edac] 50d1bb93672: EDAC sbridge: ECC is disabled. Aborting Huang Ying
2014-12-18 11:05 ` Mauro Carvalho Chehab
2014-12-19 5:26 ` Huang Ying
2015-01-05 14:06 ` Aristeu Rozanski
2015-01-07 7:43 ` Huang Ying
2015-01-07 10:27 ` Mauro Carvalho Chehab [this message]
2015-01-07 14:13 ` Aristeu Rozanski
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=20150107082714.65fcdddf@concha.lan \
--to=mchehab@osg.samsung.com \
--cc=aris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@intel.com \
/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).