From: Huang Ying <ying.huang@intel.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.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: Fri, 19 Dec 2014 13:26:59 +0800 [thread overview]
Message-ID: <1418966819.26403.33.camel@intel.com> (raw)
In-Reply-To: <20141218090536.0d671dca@recife.lan>
On Thu, 2014-12-18 at 09:05 -0200, Mauro Carvalho Chehab wrote:
> Hi Huang,
>
> Em Thu, 18 Dec 2014 16:13:26 +0800
> Huang Ying <ying.huang@intel.com> escreveu:
>
> > FYI, we noticed the below changes on
> >
> > commit 50d1bb93672fa2f42cec6e06ce799fbe864f57e9 ("sb_edac: add support for Haswell based systems")
> >
> > Something new in kernel log. This may be expected. Just FYI.
> >
> > [ 12.490615] EDAC sbridge: Seeking for: PCI ID 8086:2fa0
> > [ 12.491031] EDAC sbridge: Seeking for: PCI ID 8086:2fa0
> > [ 12.491454] EDAC sbridge: Seeking for: PCI ID 8086:2ffc
> > [ 12.491865] EDAC sbridge: Seeking for: PCI ID 8086:2ffc
> > [ 12.492284] EDAC sbridge: Seeking for: PCI ID 8086:2ffd
> > [ 12.492698] EDAC sbridge: Seeking for: PCI ID 8086:2ffd
> > [ 12.493110] EDAC sbridge: Seeking for: PCI ID 8086:2f60
> > [ 12.493528] EDAC sbridge: Seeking for: PCI ID 8086:2fa8
> > [ 12.493943] EDAC sbridge: Seeking for: PCI ID 8086:2fa8
> > [ 12.494359] EDAC sbridge: Seeking for: PCI ID 8086:2f71
> > [ 12.494789] EDAC sbridge: Seeking for: PCI ID 8086:2f71
> > [ 12.495206] EDAC sbridge: Seeking for: PCI ID 8086:2faa
> > [ 12.495622] EDAC sbridge: Seeking for: PCI ID 8086:2faa
> > [ 12.496040] EDAC sbridge: Seeking for: PCI ID 8086:2fab
> > [ 12.496462] EDAC sbridge: Seeking for: PCI ID 8086:2fab
> > [ 12.496878] EDAC sbridge: Seeking for: PCI ID 8086:2fac
> > [ 12.497297] EDAC sbridge: Seeking for: PCI ID 8086:2fac
> > [ 12.497714] EDAC sbridge: Seeking for: PCI ID 8086:2fad
> > [ 12.497923] IOAPIC[0]: Set routing entry (8-22 -> 0xb3 -> IRQ 22 Mode:1 Active:1 Dest:1)
> > [ 12.497927] IOAPIC[0]: Set IRTE entry (P:1 FPD:0 Dst_Mode:1 Redir_hint:1 Trig_Mode:0 Dlvry_Mode:1 Avail:0 Vector:B3 Dest:00000001 SID:F0FF SQ:0 SVT:1)
> > [ 12.497981] snd_hda_intel 0000:00:1b.0: irq 75 for MSI/MSI-X
> > [ 12.498086] IOAPIC[1]: Set routing entry (9-12 -> 0xe3 -> IRQ 36 Mode:1 Active:1 Dest:1)
> > [ 12.498089] IOAPIC[1]: Set IRTE entry (P:1 FPD:0 Dst_Mode:1 Redir_hint:1 Trig_Mode:0 Dlvry_Mode:1 Avail:0 Vector:E3 Dest:00000001 SID:002C SQ:0 SVT:1)
> > [ 12.498093] snd_hda_intel 0000:02:00.1: Disabling MSI
> > [ 12.498109] snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
> > [ 12.502542] EDAC sbridge: Seeking for: PCI ID 8086:2fad
> > [ 12.502956] EDAC sbridge: Seeking for: PCI ID 8086:2fbd
> > [ 12.503365] EDAC sbridge: Seeking for: PCI ID 8086:2f68
> > [ 12.503781] EDAC sbridge: Seeking for: PCI ID 8086:2f68
> > [ 12.504197] EDAC sbridge: Seeking for: PCI ID 8086:2f79
> > [ 12.504620] EDAC sbridge: Seeking for: PCI ID 8086:2f6a
> > [ 12.505041] EDAC sbridge: Seeking for: PCI ID 8086:2f6b
> > [ 12.505452] EDAC sbridge: Seeking for: PCI ID 8086:2f6c
> > [ 12.505869] EDAC sbridge: Seeking for: PCI ID 8086:2f6d
> > [ 12.506298] EDAC sbridge: ECC is disabled. Aborting
> > [ 12.506718] EDAC sbridge: Couldn't find mci handler
>
> Not sure about what are you complaining, since you didn't show how was
> the log before.
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
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2014-12-19 5: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 [this message]
2015-01-05 14:06 ` Aristeu Rozanski
2015-01-07 7:43 ` Huang Ying
2015-01-07 10:27 ` Mauro Carvalho Chehab
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=1418966819.26403.33.camel@intel.com \
--to=ying.huang@intel.com \
--cc=aris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mchehab@osg.samsung.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).