* Module loads but has error. @ 2009-10-20 17:03 Colbert, Rusty 2009-10-20 21:05 ` Doug Thompson 0 siblings, 1 reply; 14+ messages in thread From: Colbert, Rusty @ 2009-10-20 17:03 UTC (permalink / raw) To: bluesmoke ML [-- Attachment #1.1: Type: text/plain, Size: 608 bytes --] EDAC i7core: Device not found: dev 03.0 PCI ID 8086:2c18 This would seem to be the PCI_DEVICE_ID_INTEL_I7_MCR The modules are loaded, but I think this error may have caused them to be ineffective. There are no files under /sys/devices/system/edac/mc as in older edac enabled kernels. I have access to multiple platforms and can acquire DIMMs with ECC errors, but I don't see the point in installing them if the driver is not installing properly. I am currently running on an HP ProLiant DL360. It has Intel Xeon CPUs X5550. Any pointers on how I should approach debugging this? [-- Attachment #1.2: Type: text/html, Size: 2669 bytes --] [-- Attachment #2: Type: text/plain, Size: 399 bytes --] ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference [-- Attachment #3: Type: text/plain, Size: 176 bytes --] _______________________________________________ bluesmoke-devel mailing list bluesmoke-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Module loads but has error. 2009-10-20 17:03 Module loads but has error Colbert, Rusty @ 2009-10-20 21:05 ` Doug Thompson 2009-10-20 21:18 ` Keith Mannthey 0 siblings, 1 reply; 14+ messages in thread From: Doug Thompson @ 2009-10-20 21:05 UTC (permalink / raw) To: bluesmoke ML, RustyColbert Copying Mauro on this one as he has the lead on it. He is currently in Japan for a few days for the kernel summit doug t --- On Tue, 10/20/09, Colbert, Rusty <rusty.colbert@hp.com> wrote: > From: Colbert, Rusty <rusty.colbert@hp.com> > Subject: Module loads but has error. > To: "bluesmoke ML" <bluesmoke-devel@lists.sourceforge.net> > Date: Tuesday, October 20, 2009, 11:03 AM > > EDAC > i7core: Device not > found: dev 03.0 PCI ID 8086:2c18 > > > > This would seem to be the > PCI_DEVICE_ID_INTEL_I7_MCR > > > > The modules are loaded, but I think this > error may have caused them to > be ineffective. There are no files under > /sys/devices/system/edac/mc as in > older edac enabled kernels. > > > > I have access to multiple platforms and > can acquire DIMMs with ECC > errors, but I don't see the point in installing them if > the driver is not > installing properly. > > > > I am currently running on an HP ProLiant DL360. It > has > Intel Xeon CPUs X5550. > > Any pointers on how I should approach > debugging this? > > > > > > > > -----Inline Attachment Follows----- > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference > in SF, CA > is the only developer event you need to attend this year. > Jumpstart your > developing skills, take BlackBerry mobile applications to > market and stay > ahead of the curve. Join us from November 9 - 12, 2009. > Register now! > http://p.sf.net/sfu/devconference > -----Inline Attachment Follows----- > > _______________________________________________ > bluesmoke-devel mailing list > bluesmoke-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Module loads but has error. 2009-10-20 21:05 ` Doug Thompson @ 2009-10-20 21:18 ` Keith Mannthey 2009-10-20 22:47 ` Mauro Carvalho Chehab 0 siblings, 1 reply; 14+ messages in thread From: Keith Mannthey @ 2009-10-20 21:18 UTC (permalink / raw) To: Doug Thompson; +Cc: bluesmoke ML On Tue, 2009-10-20 at 14:05 -0700, Doug Thompson wrote: > Copying Mauro on this one as he has the lead on it. He is currently in Japan for a few days for the kernel summit > > doug t > > --- On Tue, 10/20/09, Colbert, Rusty <rusty.colbert@hp.com> wrote: > > > From: Colbert, Rusty <rusty.colbert@hp.com> > > Subject: Module loads but has error. > > To: "bluesmoke ML" <bluesmoke-devel@lists.sourceforge.net> > > Date: Tuesday, October 20, 2009, 11:03 AM > > > > EDAC > > i7core: Device not > > found: dev 03.0 PCI ID 8086:2c18 Rusty, Are you using the current i7core git tree? What version of the kernel are you using? How many sockets do you have in your system? Are there any other edac printk statements? Could you enable EDAC_DEBUG and see if you get any more output? After you try and load the driver what does lspci show? Thanks, Keith Mannthey LTC Real-Time > > > > > > This would seem to be the > > PCI_DEVICE_ID_INTEL_I7_MCR > > > > > > > > The modules are loaded, but I think this > > error may have caused them to > > be ineffective. There are no files under > > /sys/devices/system/edac/mc as in > > older edac enabled kernels. > > > > > > > > I have access to multiple platforms and > > can acquire DIMMs with ECC > > errors, but I don't see the point in installing them if > > the driver is not > > installing properly. > > > > > > > > I am currently running on an HP ProLiant DL360. It > > has > > Intel Xeon CPUs X5550. > > > > Any pointers on how I should approach > > debugging this? > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry(R) Developer Conference > > in SF, CA > > is the only developer event you need to attend this year. > > Jumpstart your > > developing skills, take BlackBerry mobile applications to > > market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. > > Register now! > > http://p.sf.net/sfu/devconference > > -----Inline Attachment Follows----- > > > > _______________________________________________ > > bluesmoke-devel mailing list > > bluesmoke-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > bluesmoke-devel mailing list > bluesmoke-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Module loads but has error. 2009-10-20 21:18 ` Keith Mannthey @ 2009-10-20 22:47 ` Mauro Carvalho Chehab 2009-10-21 14:13 ` Colbert, Rusty 2009-10-21 17:55 ` Colbert, Rusty 0 siblings, 2 replies; 14+ messages in thread From: Mauro Carvalho Chehab @ 2009-10-20 22:47 UTC (permalink / raw) To: RustyColbert; +Cc: Doug Thompson, bluesmoke ML Hi Rusty, Em Tue, 20 Oct 2009 14:18:20 -0700 Keith Mannthey <kmannth@us.ibm.com> escreveu: > On Tue, 2009-10-20 at 14:05 -0700, Doug Thompson wrote: > > Copying Mauro on this one as he has the lead on it. He is currently in Japan for a few days for the kernel summit > > > > doug t > > > > --- On Tue, 10/20/09, Colbert, Rusty <rusty.colbert@hp.com> wrote: > > > > > From: Colbert, Rusty <rusty.colbert@hp.com> > > > Subject: Module loads but has error. > > > To: "bluesmoke ML" <bluesmoke-devel@lists.sourceforge.net> > > > Date: Tuesday, October 20, 2009, 11:03 AM > > > > > > EDAC > > > i7core: Device not > > > found: dev 03.0 PCI ID 8086:2c18 > > Rusty, > Are you using the current i7core git tree? What version of the kernel > are you using? > > How many sockets do you have in your system? > > Are there any other edac printk statements? Could you enable > EDAC_DEBUG and see if you get any more output? > > After you try and load the driver what does lspci show? Probably it didn't recognize the PCI buses 0xff and 0xfe. Be sure to be using the linux-next branch from my -git tree (or from the official linux-next tree), since it has all needed patches and fixes needed for PCI device for it to work. One of the tests machine is a Xeon 5550 (motherboard uses a Supermicro model X8DTN with Intel(R) Xeon(R) CPU X5550 @ 2.67GHz CPUs - not sure whose manufactured it, since I'm using it remotely), so I'm pretty sure that it works on such CPU's. Those are the expected results: # dmesg|grep -i edac [ 23.866982] EDAC MC: Ver: 2.1.0 Oct 19 2009 [ 23.867007] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867030] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867054] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867077] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867097] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867117] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867137] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867157] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867178] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867199] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867219] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867239] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867258] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867277] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867295] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867315] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867334] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867353] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867372] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867391] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867409] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867428] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867447] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867466] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867502] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867532] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867562] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867593] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867625] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867702] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867734] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867765] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867797] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867837] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867871] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867904] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867937] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867970] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868006] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868040] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868079] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868116] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868151] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868186] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868225] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868264] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868422] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 1028: edac_sysfs_setup_mc_kset() [ 23.868553] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 1045: edac_sysfs_setup_mc_kset() Registered '.../edac/mc' kobject [ 23.917015] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 2030: MC: drivers/edac/i7core_edac.c: i7core_init() [ 23.952493] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.0 PCI ID 8086:2c18 [ 23.952585] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.0 PCI ID 8086:2c18 [ 23.952723] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.1 PCI ID 8086:2c19 [ 23.952778] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.1 PCI ID 8086:2c19 [ 23.952898] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.2 PCI ID 8086:2c1a [ 23.952964] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.2 PCI ID 8086:2c1a [ 23.953159] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.4 PCI ID 8086:2c1c [ 23.953224] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.4 PCI ID 8086:2c1c [ 23.953357] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.0 PCI ID 8086:2c20 [ 23.953407] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.0 PCI ID 8086:2c20 [ 23.953546] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.1 PCI ID 8086:2c21 [ 23.953621] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.1 PCI ID 8086:2c21 [ 23.953750] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.2 PCI ID 8086:2c22 [ 23.953796] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.2 PCI ID 8086:2c22 [ 23.953950] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.3 PCI ID 8086:2c23 [ 23.954006] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.3 PCI ID 8086:2c23 [ 23.954152] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.0 PCI ID 8086:2c28 [ 23.954195] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.0 PCI ID 8086:2c28 [ 23.954285] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.1 PCI ID 8086:2c29 [ 23.954330] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.1 PCI ID 8086:2c29 [ 23.954471] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.2 PCI ID 8086:2c2a [ 23.954539] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.2 PCI ID 8086:2c2a [ 23.954690] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.3 PCI ID 8086:2c2b [ 23.954748] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.3 PCI ID 8086:2c2b [ 23.954888] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.0 PCI ID 8086:2c30 [ 23.954947] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.0 PCI ID 8086:2c30 [ 23.955098] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.1 PCI ID 8086:2c31 [ 23.955153] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.1 PCI ID 8086:2c31 [ 23.955259] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.2 PCI ID 8086:2c32 [ 23.955315] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.2 PCI ID 8086:2c32 [ 23.955435] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.3 PCI ID 8086:2c33 [ 23.955488] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.3 PCI ID 8086:2c33 [ 23.955715] i7core_edac: detected a Nehalem Memory Controller [ 23.955724] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:00.0 PCI ID 8086:2c41 [ 23.955874] i7core_edac: detected a Nehalem Memory Controller [ 23.955886] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:00.0 PCI ID 8086:2c41 [ 23.956042] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 513: Number of active channels on socket 0: 2 [ 23.956077] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 670: edac_mc_register_sysfs_main_kobj() [ 23.956397] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 706: edac_mc_register_sysfs_main_kobj() Registered '.../edac/mc0' kobject [ 23.956409] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1821: MC: drivers/edac/i7core_edac.c: i7core_register_mci(): mci = ffff8801398e8000 [ 23.956435] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.0, dev = ffff88013e1cf000, socket 0 [ 23.956444] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.1, dev = ffff88013e1cf800, socket 0 [ 23.956452] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.2, dev = ffff88013e1cb000, socket 0 [ 23.956462] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.4, dev = ffff88013e1c8800, socket 0 [ 23.956483] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.0, dev = ffff88013c7df000, socket 0 [ 23.956490] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.1, dev = ffff88013c7df800, socket 0 [ 23.956499] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.2, dev = ffff88013c7de000, socket 0 [ 23.956508] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.3, dev = ffff88013c7de800, socket 0 [ 23.956515] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.0, dev = ffff88013c7dd000, socket 0 [ 23.956523] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.1, dev = ffff88013c7dd800, socket 0 [ 23.956529] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.2, dev = ffff88013a2d8000, socket 0 [ 23.956534] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.3, dev = ffff88013a2d8800, socket 0 [ 23.956541] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.0, dev = ffff88013a2d9000, socket 0 [ 23.956549] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.1, dev = ffff88013a2d9800, socket 0 [ 23.956555] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.2, dev = ffff88013a2da000, socket 0 [ 23.956561] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.3, dev = ffff88013a2da800, socket 0 [ 23.956566] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 0.0, dev = ffff88013e1c8000, socket 0 [ 23.956578] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 541: QPI 0 control=0x00000602 status=0x00000019 dod=0x00000090 map=0x00024489 [ 23.956583] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 545: ECC enabled with x8 SDCC [ 23.956590] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 564: DOD Max limits: DIMMS: 1, 1-ranked, 8-banked x4000 x 0x400 [ 23.956596] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 573: Channel 0 is not active [ 23.956614] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch1 phy rd1, wr1 (0x063ffc31): 2 ranks, RDIMMs [ 23.956620] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.956641] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [1] DIVBY3 REMOVED OFFSET [ 23.956646] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956651] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956657] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956661] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956665] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956673] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956680] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956685] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956695] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch2 phy rd3, wr3 (0x063ffc31): 2 ranks, RDIMMs [ 23.956705] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.956733] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [2] DIVBY3 REMOVED OFFSET [ 23.956740] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956748] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956754] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956760] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956767] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956774] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956780] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956785] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956793] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 473: edac_mc_add_mc() [ 23.956827] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 911: edac_create_sysfs_mci_device() idx=0 [ 23.956880] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.956885] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_section [ 23.956918] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_type [ 23.956953] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_eccmask [ 23.956993] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 818: edac_create_mci_instance_attributes() grp inject_addrmatch, mci ffff8801398e8000 [ 23.957074] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.957082] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file channel [ 23.957106] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file dimm [ 23.957132] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file rank [ 23.957159] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file bank [ 23.957183] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file page [ 23.957212] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file col [ 23.957246] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_enable [ 23.957878] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 296: edac_mc_workq_setup() [ 23.957892] EDAC MC0: Giving out device to 'i7core_edac.c' 'i7 core #0': DEV 0000:ff:03.0 [ 23.957899] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 49: edac_pci_alloc_ctl_info() [ 23.957920] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 346: edac_pci_add_device() [ 23.957946] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 126: add_edac_pci_to_global_list() [ 23.957953] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 101: find_edac_pci_by_dev() [ 23.957961] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 444: edac_pci_create_sysfs() idx=0 [ 23.957966] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 347: edac_pci_main_kobj_setup() [ 23.958246] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 394: Registered '.../edac/pci' kobject [ 23.958254] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 163: edac_pci_create_instance_kobj() [ 23.958436] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 186: edac_pci_create_instance_kobj() Register instance 'pci0' kobject [ 23.958468] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 274: edac_pci_workq_setup() [ 23.958474] EDAC PCI0: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:ff:03.0' (POLLED) [ 23.958511] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 513: Number of active channels on socket 1: 2 [ 23.958526] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 670: edac_mc_register_sysfs_main_kobj() [ 23.962494] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 706: edac_mc_register_sysfs_main_kobj() Registered '.../edac/mc1' kobject [ 23.962503] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1821: MC: drivers/edac/i7core_edac.c: i7core_register_mci(): mci = ffff8801398ea000 [ 23.962533] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.0, dev = ffff88013a2de000, socket 1 [ 23.962539] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.1, dev = ffff88013a2de800, socket 1 [ 23.962545] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.2, dev = ffff88013a2df000, socket 1 [ 23.962549] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.4, dev = ffff88013a2df800, socket 1 [ 23.962554] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.0, dev = ffff88013a2f0000, socket 1 [ 23.962561] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.1, dev = ffff88013a2f0800, socket 1 [ 23.962571] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.2, dev = ffff88013a2f1000, socket 1 [ 23.962582] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.3, dev = ffff88013a2f1800, socket 1 [ 23.962595] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.0, dev = ffff88013a2f2000, socket 1 [ 23.962609] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.1, dev = ffff88013a2f2800, socket 1 [ 23.962622] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.2, dev = ffff88013a2f3000, socket 1 [ 23.962630] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.3, dev = ffff88013a2f3800, socket 1 [ 23.962645] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.0, dev = ffff88013cfc2800, socket 1 [ 23.962653] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.1, dev = ffff88013cfc3000, socket 1 [ 23.962662] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.2, dev = ffff88013cfc1800, socket 1 [ 23.962674] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.3, dev = ffff88013cfc4800, socket 1 [ 23.962682] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 0.0, dev = ffff88013a2db000, socket 1 [ 23.962712] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 541: QPI 1 control=0x00000602 status=0x00000019 dod=0x00000090 map=0x00024489 [ 23.962724] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 545: ECC enabled with x8 SDCC [ 23.962737] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 564: DOD Max limits: DIMMS: 1, 1-ranked, 8-banked x4000 x 0x400 [ 23.962745] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 573: Channel 0 is not active [ 23.962766] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch1 phy rd1, wr1 (0x063ffc31): 2 ranks, RDIMMs [ 23.962779] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.962810] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [1] DIVBY3 REMOVED OFFSET [ 23.962822] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962830] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962836] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962845] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962853] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962860] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962869] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962876] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962894] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch2 phy rd3, wr3 (0x063ffc31): 2 ranks, RDIMMs [ 23.962903] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.962943] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [2] DIVBY3 REMOVED OFFSET [ 23.962954] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962966] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962978] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962987] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962995] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963005] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963012] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963021] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963033] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 473: edac_mc_add_mc() [ 23.963044] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 911: edac_create_sysfs_mci_device() idx=1 [ 23.963093] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.963105] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_section [ 23.963134] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_type [ 23.963161] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_eccmask [ 23.963202] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 818: edac_create_mci_instance_attributes() grp inject_addrmatch, mci ffff8801398ea000 [ 23.963278] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.963287] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file channel [ 23.963669] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file dimm [ 23.963713] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file rank [ 23.963749] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file bank [ 23.963786] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file page [ 23.963838] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file col [ 23.963878] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_enable [ 23.964601] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 296: edac_mc_workq_setup() [ 23.964613] EDAC MC1: Giving out device to 'i7core_edac.c' 'i7 core #1': DEV 0000:fe:03.0 [ 23.964624] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 49: edac_pci_alloc_ctl_info() [ 23.964644] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 346: edac_pci_add_device() [ 23.964655] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 126: add_edac_pci_to_global_list() [ 23.964663] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 101: find_edac_pci_by_dev() [ 23.964671] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 444: edac_pci_create_sysfs() idx=1 [ 23.964678] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 347: edac_pci_main_kobj_setup() [ 23.964689] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 163: edac_pci_create_instance_kobj() [ 23.964918] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 186: edac_pci_create_instance_kobj() Register instance 'pci1' kobject [ 23.964971] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 274: edac_pci_workq_setup() [ 23.964978] EDAC PCI1: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:fe:03.0' (POLLED) [ 23.964985] EDAC i7core: Driver loaded. Also, you should be able to see the PCI buses ff and fe: # lspci -n|grep ^f fe:00.0 0600: 8086:2c40 (rev 04) fe:00.1 0600: 8086:2c01 (rev 04) fe:02.0 0600: 8086:2c10 (rev 04) fe:02.1 0600: 8086:2c11 (rev 04) fe:02.4 0600: 8086:2c14 (rev 04) fe:02.5 0600: 8086:2c15 (rev 04) fe:03.0 0600: 8086:2c18 (rev 04) fe:03.1 0600: 8086:2c19 (rev 04) fe:03.2 0600: 8086:2c1a (rev 04) fe:03.4 0600: 8086:2c1c (rev 04) fe:04.0 0600: 8086:2c20 (rev 04) fe:04.1 0600: 8086:2c21 (rev 04) fe:04.2 0600: 8086:2c22 (rev 04) fe:04.3 0600: 8086:2c23 (rev 04) fe:05.0 0600: 8086:2c28 (rev 04) fe:05.1 0600: 8086:2c29 (rev 04) fe:05.2 0600: 8086:2c2a (rev 04) fe:05.3 0600: 8086:2c2b (rev 04) fe:06.0 0600: 8086:2c30 (rev 04) fe:06.1 0600: 8086:2c31 (rev 04) fe:06.2 0600: 8086:2c32 (rev 04) fe:06.3 0600: 8086:2c33 (rev 04) ff:00.0 0600: 8086:2c40 (rev 04) ff:00.1 0600: 8086:2c01 (rev 04) ff:02.0 0600: 8086:2c10 (rev 04) ff:02.1 0600: 8086:2c11 (rev 04) ff:02.4 0600: 8086:2c14 (rev 04) ff:02.5 0600: 8086:2c15 (rev 04) ff:03.0 0600: 8086:2c18 (rev 04) ff:03.1 0600: 8086:2c19 (rev 04) ff:03.2 0600: 8086:2c1a (rev 04) ff:03.4 0600: 8086:2c1c (rev 04) ff:04.0 0600: 8086:2c20 (rev 04) ff:04.1 0600: 8086:2c21 (rev 04) ff:04.2 0600: 8086:2c22 (rev 04) ff:04.3 0600: 8086:2c23 (rev 04) ff:05.0 0600: 8086:2c28 (rev 04) ff:05.1 0600: 8086:2c29 (rev 04) ff:05.2 0600: 8086:2c2a (rev 04) ff:05.3 0600: 8086:2c2b (rev 04) ff:06.0 0600: 8086:2c30 (rev 04) ff:06.1 0600: 8086:2c31 (rev 04) ff:06.2 0600: 8086:2c32 (rev 04) ff:06.3 0600: 8086:2c33 (rev 04) If you are not noticing the PCI devices starting with fe: and ff: and are using my latest tree, then it is likely that your motherboard BIOS is doing something weird to hide the Nehalem non-core PCI buses. > > Thanks, > Keith Mannthey > LTC Real-Time > > > > > > > > > > This would seem to be the > > > PCI_DEVICE_ID_INTEL_I7_MCR > > > > > > > > > > > > The modules are loaded, but I think this > > > error may have caused them to > > > be ineffective. There are no files under > > > /sys/devices/system/edac/mc as in > > > older edac enabled kernels. > > > > > > > > > > > > I have access to multiple platforms and > > > can acquire DIMMs with ECC > > > errors, but I don't see the point in installing them if > > > the driver is not > > > installing properly. > > > > > > > > > > > > I am currently running on an HP ProLiant DL360. It > > > has > > > Intel Xeon CPUs X5550. > > > > > > Any pointers on how I should approach > > > debugging this? > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > ------------------------------------------------------------------------------ > > > Come build with us! The BlackBerry(R) Developer Conference > > > in SF, CA > > > is the only developer event you need to attend this year. > > > Jumpstart your > > > developing skills, take BlackBerry mobile applications to > > > market and stay > > > ahead of the curve. Join us from November 9 - 12, 2009. > > > Register now! > > > http://p.sf.net/sfu/devconference > > > -----Inline Attachment Follows----- > > > > > > _______________________________________________ > > > bluesmoke-devel mailing list > > > bluesmoke-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > bluesmoke-devel mailing list > > bluesmoke-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > bluesmoke-devel mailing list > bluesmoke-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Module loads but has error. 2009-10-20 22:47 ` Mauro Carvalho Chehab @ 2009-10-21 14:13 ` Colbert, Rusty 2009-10-21 15:26 ` Keith Mannthey 2009-10-21 17:55 ` Colbert, Rusty 1 sibling, 1 reply; 14+ messages in thread From: Colbert, Rusty @ 2009-10-21 14:13 UTC (permalink / raw) To: Mauro Carvalho Chehab; +Cc: Doug Thompson, bluesmoke ML It was a linux-next tree and is identified as 2.6.32-rc4, and edac is: EDAC MC: Ver: 2.1.0 Oct 16 2009 There are 2 sockets in the system. I don't see those addresses in the output of lspci. It is looking glum, if my BIOS is hiding buses. However, once I verify that that is the case, I'll contact someone on the ROM team to check on that. If I look at another board with Nehalem, not running my kernel, should I see those buses? (does not show up on a DL380 G6 running SLES11 default kernel either) I could not get git to connect from my dev server. So I went to git and found your latest tree and clicked on it. http://git.kernel.org/?p=linux/kernel/git/mchehab/i7core.git;a=summary Then I went down to linux_next, clicked on it and grabbed a snapshot from the top of the tree. -----Original Message----- From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org] Sent: Tuesday, October 20, 2009 5:48 PM To: Colbert, Rusty Cc: Keith Mannthey; Doug Thompson; bluesmoke ML Subject: Re: Module loads but has error. Hi Rusty, Em Tue, 20 Oct 2009 14:18:20 -0700 Keith Mannthey <kmannth@us.ibm.com> escreveu: > On Tue, 2009-10-20 at 14:05 -0700, Doug Thompson wrote: > > Copying Mauro on this one as he has the lead on it. He is currently in Japan for a few days for the kernel summit > > > > doug t > > > > --- On Tue, 10/20/09, Colbert, Rusty <rusty.colbert@hp.com> wrote: > > > > > From: Colbert, Rusty <rusty.colbert@hp.com> > > > Subject: Module loads but has error. > > > To: "bluesmoke ML" <bluesmoke-devel@lists.sourceforge.net> > > > Date: Tuesday, October 20, 2009, 11:03 AM > > > > > > EDAC > > > i7core: Device not > > > found: dev 03.0 PCI ID 8086:2c18 > > Rusty, > Are you using the current i7core git tree? What version of the kernel > are you using? > > How many sockets do you have in your system? > > Are there any other edac printk statements? Could you enable > EDAC_DEBUG and see if you get any more output? > > After you try and load the driver what does lspci show? Probably it didn't recognize the PCI buses 0xff and 0xfe. Be sure to be using the linux-next branch from my -git tree (or from the official linux-next tree), since it has all needed patches and fixes needed for PCI device for it to work. One of the tests machine is a Xeon 5550 (motherboard uses a Supermicro model X8DTN with Intel(R) Xeon(R) CPU X5550 @ 2.67GHz CPUs - not sure whose manufactured it, since I'm using it remotely), so I'm pretty sure that it works on such CPU's. Those are the expected results: # dmesg|grep -i edac [ 23.866982] EDAC MC: Ver: 2.1.0 Oct 19 2009 [ 23.867007] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867030] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867054] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867077] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867097] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867117] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867137] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867157] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867178] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867199] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867219] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867239] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867258] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867277] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867295] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867315] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867334] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867353] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867372] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867391] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867409] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867428] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867447] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867466] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867502] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867532] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867562] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867593] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867625] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867702] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867734] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867765] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867797] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867837] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867871] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867904] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867937] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867970] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868006] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868040] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868079] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868116] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868151] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868186] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868225] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868264] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868422] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 1028: edac_sysfs_setup_mc_kset() [ 23.868553] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 1045: edac_sysfs_setup_mc_kset() Registered '.../edac/mc' kobject [ 23.917015] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 2030: MC: drivers/edac/i7core_edac.c: i7core_init() [ 23.952493] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.0 PCI ID 8086:2c18 [ 23.952585] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.0 PCI ID 8086:2c18 [ 23.952723] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.1 PCI ID 8086:2c19 [ 23.952778] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.1 PCI ID 8086:2c19 [ 23.952898] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.2 PCI ID 8086:2c1a [ 23.952964] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.2 PCI ID 8086:2c1a [ 23.953159] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.4 PCI ID 8086:2c1c [ 23.953224] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.4 PCI ID 8086:2c1c [ 23.953357] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.0 PCI ID 8086:2c20 [ 23.953407] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.0 PCI ID 8086:2c20 [ 23.953546] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.1 PCI ID 8086:2c21 [ 23.953621] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.1 PCI ID 8086:2c21 [ 23.953750] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.2 PCI ID 8086:2c22 [ 23.953796] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.2 PCI ID 8086:2c22 [ 23.953950] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.3 PCI ID 8086:2c23 [ 23.954006] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.3 PCI ID 8086:2c23 [ 23.954152] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.0 PCI ID 8086:2c28 [ 23.954195] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.0 PCI ID 8086:2c28 [ 23.954285] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.1 PCI ID 8086:2c29 [ 23.954330] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.1 PCI ID 8086:2c29 [ 23.954471] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.2 PCI ID 8086:2c2a [ 23.954539] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.2 PCI ID 8086:2c2a [ 23.954690] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.3 PCI ID 8086:2c2b [ 23.954748] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.3 PCI ID 8086:2c2b [ 23.954888] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.0 PCI ID 8086:2c30 [ 23.954947] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.0 PCI ID 8086:2c30 [ 23.955098] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.1 PCI ID 8086:2c31 [ 23.955153] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.1 PCI ID 8086:2c31 [ 23.955259] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.2 PCI ID 8086:2c32 [ 23.955315] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.2 PCI ID 8086:2c32 [ 23.955435] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.3 PCI ID 8086:2c33 [ 23.955488] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.3 PCI ID 8086:2c33 [ 23.955715] i7core_edac: detected a Nehalem Memory Controller [ 23.955724] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:00.0 PCI ID 8086:2c41 [ 23.955874] i7core_edac: detected a Nehalem Memory Controller [ 23.955886] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:00.0 PCI ID 8086:2c41 [ 23.956042] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 513: Number of active channels on socket 0: 2 [ 23.956077] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 670: edac_mc_register_sysfs_main_kobj() [ 23.956397] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 706: edac_mc_register_sysfs_main_kobj() Registered '.../edac/mc0' kobject [ 23.956409] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1821: MC: drivers/edac/i7core_edac.c: i7core_register_mci(): mci = ffff8801398e8000 [ 23.956435] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.0, dev = ffff88013e1cf000, socket 0 [ 23.956444] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.1, dev = ffff88013e1cf800, socket 0 [ 23.956452] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.2, dev = ffff88013e1cb000, socket 0 [ 23.956462] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.4, dev = ffff88013e1c8800, socket 0 [ 23.956483] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.0, dev = ffff88013c7df000, socket 0 [ 23.956490] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.1, dev = ffff88013c7df800, socket 0 [ 23.956499] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.2, dev = ffff88013c7de000, socket 0 [ 23.956508] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.3, dev = ffff88013c7de800, socket 0 [ 23.956515] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.0, dev = ffff88013c7dd000, socket 0 [ 23.956523] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.1, dev = ffff88013c7dd800, socket 0 [ 23.956529] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.2, dev = ffff88013a2d8000, socket 0 [ 23.956534] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.3, dev = ffff88013a2d8800, socket 0 [ 23.956541] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.0, dev = ffff88013a2d9000, socket 0 [ 23.956549] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.1, dev = ffff88013a2d9800, socket 0 [ 23.956555] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.2, dev = ffff88013a2da000, socket 0 [ 23.956561] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.3, dev = ffff88013a2da800, socket 0 [ 23.956566] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 0.0, dev = ffff88013e1c8000, socket 0 [ 23.956578] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 541: QPI 0 control=0x00000602 status=0x00000019 dod=0x00000090 map=0x00024489 [ 23.956583] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 545: ECC enabled with x8 SDCC [ 23.956590] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 564: DOD Max limits: DIMMS: 1, 1-ranked, 8-banked x4000 x 0x400 [ 23.956596] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 573: Channel 0 is not active [ 23.956614] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch1 phy rd1, wr1 (0x063ffc31): 2 ranks, RDIMMs [ 23.956620] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.956641] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [1] DIVBY3 REMOVED OFFSET [ 23.956646] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956651] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956657] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956661] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956665] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956673] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956680] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956685] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956695] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch2 phy rd3, wr3 (0x063ffc31): 2 ranks, RDIMMs [ 23.956705] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.956733] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [2] DIVBY3 REMOVED OFFSET [ 23.956740] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956748] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956754] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956760] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956767] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956774] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956780] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956785] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956793] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 473: edac_mc_add_mc() [ 23.956827] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 911: edac_create_sysfs_mci_device() idx=0 [ 23.956880] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.956885] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_section [ 23.956918] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_type [ 23.956953] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_eccmask [ 23.956993] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 818: edac_create_mci_instance_attributes() grp inject_addrmatch, mci ffff8801398e8000 [ 23.957074] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.957082] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file channel [ 23.957106] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file dimm [ 23.957132] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file rank [ 23.957159] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file bank [ 23.957183] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file page [ 23.957212] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file col [ 23.957246] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_enable [ 23.957878] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 296: edac_mc_workq_setup() [ 23.957892] EDAC MC0: Giving out device to 'i7core_edac.c' 'i7 core #0': DEV 0000:ff:03.0 [ 23.957899] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 49: edac_pci_alloc_ctl_info() [ 23.957920] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 346: edac_pci_add_device() [ 23.957946] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 126: add_edac_pci_to_global_list() [ 23.957953] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 101: find_edac_pci_by_dev() [ 23.957961] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 444: edac_pci_create_sysfs() idx=0 [ 23.957966] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 347: edac_pci_main_kobj_setup() [ 23.958246] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 394: Registered '.../edac/pci' kobject [ 23.958254] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 163: edac_pci_create_instance_kobj() [ 23.958436] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 186: edac_pci_create_instance_kobj() Register instance 'pci0' kobject [ 23.958468] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 274: edac_pci_workq_setup() [ 23.958474] EDAC PCI0: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:ff:03.0' (POLLED) [ 23.958511] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 513: Number of active channels on socket 1: 2 [ 23.958526] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 670: edac_mc_register_sysfs_main_kobj() [ 23.962494] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 706: edac_mc_register_sysfs_main_kobj() Registered '.../edac/mc1' kobject [ 23.962503] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1821: MC: drivers/edac/i7core_edac.c: i7core_register_mci(): mci = ffff8801398ea000 [ 23.962533] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.0, dev = ffff88013a2de000, socket 1 [ 23.962539] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.1, dev = ffff88013a2de800, socket 1 [ 23.962545] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.2, dev = ffff88013a2df000, socket 1 [ 23.962549] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.4, dev = ffff88013a2df800, socket 1 [ 23.962554] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.0, dev = ffff88013a2f0000, socket 1 [ 23.962561] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.1, dev = ffff88013a2f0800, socket 1 [ 23.962571] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.2, dev = ffff88013a2f1000, socket 1 [ 23.962582] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.3, dev = ffff88013a2f1800, socket 1 [ 23.962595] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.0, dev = ffff88013a2f2000, socket 1 [ 23.962609] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.1, dev = ffff88013a2f2800, socket 1 [ 23.962622] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.2, dev = ffff88013a2f3000, socket 1 [ 23.962630] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.3, dev = ffff88013a2f3800, socket 1 [ 23.962645] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.0, dev = ffff88013cfc2800, socket 1 [ 23.962653] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.1, dev = ffff88013cfc3000, socket 1 [ 23.962662] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.2, dev = ffff88013cfc1800, socket 1 [ 23.962674] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.3, dev = ffff88013cfc4800, socket 1 [ 23.962682] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 0.0, dev = ffff88013a2db000, socket 1 [ 23.962712] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 541: QPI 1 control=0x00000602 status=0x00000019 dod=0x00000090 map=0x00024489 [ 23.962724] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 545: ECC enabled with x8 SDCC [ 23.962737] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 564: DOD Max limits: DIMMS: 1, 1-ranked, 8-banked x4000 x 0x400 [ 23.962745] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 573: Channel 0 is not active [ 23.962766] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch1 phy rd1, wr1 (0x063ffc31): 2 ranks, RDIMMs [ 23.962779] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.962810] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [1] DIVBY3 REMOVED OFFSET [ 23.962822] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962830] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962836] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962845] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962853] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962860] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962869] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962876] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962894] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch2 phy rd3, wr3 (0x063ffc31): 2 ranks, RDIMMs [ 23.962903] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.962943] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [2] DIVBY3 REMOVED OFFSET [ 23.962954] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962966] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962978] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962987] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962995] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963005] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963012] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963021] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963033] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 473: edac_mc_add_mc() [ 23.963044] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 911: edac_create_sysfs_mci_device() idx=1 [ 23.963093] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.963105] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_section [ 23.963134] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_type [ 23.963161] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_eccmask [ 23.963202] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 818: edac_create_mci_instance_attributes() grp inject_addrmatch, mci ffff8801398ea000 [ 23.963278] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.963287] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file channel [ 23.963669] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file dimm [ 23.963713] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file rank [ 23.963749] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file bank [ 23.963786] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file page [ 23.963838] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file col [ 23.963878] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_enable [ 23.964601] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 296: edac_mc_workq_setup() [ 23.964613] EDAC MC1: Giving out device to 'i7core_edac.c' 'i7 core #1': DEV 0000:fe:03.0 [ 23.964624] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 49: edac_pci_alloc_ctl_info() [ 23.964644] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 346: edac_pci_add_device() [ 23.964655] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 126: add_edac_pci_to_global_list() [ 23.964663] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 101: find_edac_pci_by_dev() [ 23.964671] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 444: edac_pci_create_sysfs() idx=1 [ 23.964678] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 347: edac_pci_main_kobj_setup() [ 23.964689] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 163: edac_pci_create_instance_kobj() [ 23.964918] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 186: edac_pci_create_instance_kobj() Register instance 'pci1' kobject [ 23.964971] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 274: edac_pci_workq_setup() [ 23.964978] EDAC PCI1: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:fe:03.0' (POLLED) [ 23.964985] EDAC i7core: Driver loaded. Also, you should be able to see the PCI buses ff and fe: # lspci -n|grep ^f fe:00.0 0600: 8086:2c40 (rev 04) fe:00.1 0600: 8086:2c01 (rev 04) fe:02.0 0600: 8086:2c10 (rev 04) fe:02.1 0600: 8086:2c11 (rev 04) fe:02.4 0600: 8086:2c14 (rev 04) fe:02.5 0600: 8086:2c15 (rev 04) fe:03.0 0600: 8086:2c18 (rev 04) fe:03.1 0600: 8086:2c19 (rev 04) fe:03.2 0600: 8086:2c1a (rev 04) fe:03.4 0600: 8086:2c1c (rev 04) fe:04.0 0600: 8086:2c20 (rev 04) fe:04.1 0600: 8086:2c21 (rev 04) fe:04.2 0600: 8086:2c22 (rev 04) fe:04.3 0600: 8086:2c23 (rev 04) fe:05.0 0600: 8086:2c28 (rev 04) fe:05.1 0600: 8086:2c29 (rev 04) fe:05.2 0600: 8086:2c2a (rev 04) fe:05.3 0600: 8086:2c2b (rev 04) fe:06.0 0600: 8086:2c30 (rev 04) fe:06.1 0600: 8086:2c31 (rev 04) fe:06.2 0600: 8086:2c32 (rev 04) fe:06.3 0600: 8086:2c33 (rev 04) ff:00.0 0600: 8086:2c40 (rev 04) ff:00.1 0600: 8086:2c01 (rev 04) ff:02.0 0600: 8086:2c10 (rev 04) ff:02.1 0600: 8086:2c11 (rev 04) ff:02.4 0600: 8086:2c14 (rev 04) ff:02.5 0600: 8086:2c15 (rev 04) ff:03.0 0600: 8086:2c18 (rev 04) ff:03.1 0600: 8086:2c19 (rev 04) ff:03.2 0600: 8086:2c1a (rev 04) ff:03.4 0600: 8086:2c1c (rev 04) ff:04.0 0600: 8086:2c20 (rev 04) ff:04.1 0600: 8086:2c21 (rev 04) ff:04.2 0600: 8086:2c22 (rev 04) ff:04.3 0600: 8086:2c23 (rev 04) ff:05.0 0600: 8086:2c28 (rev 04) ff:05.1 0600: 8086:2c29 (rev 04) ff:05.2 0600: 8086:2c2a (rev 04) ff:05.3 0600: 8086:2c2b (rev 04) ff:06.0 0600: 8086:2c30 (rev 04) ff:06.1 0600: 8086:2c31 (rev 04) ff:06.2 0600: 8086:2c32 (rev 04) ff:06.3 0600: 8086:2c33 (rev 04) If you are not noticing the PCI devices starting with fe: and ff: and are using my latest tree, then it is likely that your motherboard BIOS is doing something weird to hide the Nehalem non-core PCI buses. > > Thanks, > Keith Mannthey > LTC Real-Time > > > > > > > > > > This would seem to be the > > > PCI_DEVICE_ID_INTEL_I7_MCR > > > > > > > > > > > > The modules are loaded, but I think this > > > error may have caused them to > > > be ineffective. There are no files under > > > /sys/devices/system/edac/mc as in > > > older edac enabled kernels. > > > > > > > > > > > > I have access to multiple platforms and > > > can acquire DIMMs with ECC > > > errors, but I don't see the point in installing them if > > > the driver is not > > > installing properly. > > > > > > > > > > > > I am currently running on an HP ProLiant DL360. It > > > has > > > Intel Xeon CPUs X5550. > > > > > > Any pointers on how I should approach > > > debugging this? > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > ------------------------------------------------------------------------------ > > > Come build with us! The BlackBerry(R) Developer Conference > > > in SF, CA > > > is the only developer event you need to attend this year. > > > Jumpstart your > > > developing skills, take BlackBerry mobile applications to > > > market and stay > > > ahead of the curve. Join us from November 9 - 12, 2009. > > > Register now! > > > http://p.sf.net/sfu/devconference > > > -----Inline Attachment Follows----- > > > > > > _______________________________________________ > > > bluesmoke-devel mailing list > > > bluesmoke-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > bluesmoke-devel mailing list > > bluesmoke-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > bluesmoke-devel mailing list > bluesmoke-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Module loads but has error. 2009-10-21 14:13 ` Colbert, Rusty @ 2009-10-21 15:26 ` Keith Mannthey 2009-10-21 20:03 ` Mauro Carvalho Chehab 0 siblings, 1 reply; 14+ messages in thread From: Keith Mannthey @ 2009-10-21 15:26 UTC (permalink / raw) To: Colbert, Rusty; +Cc: Doug Thompson, bluesmoke ML On Wed, 2009-10-21 at 14:13 +0000, Colbert, Rusty wrote: > It was a linux-next tree and is identified as 2.6.32-rc4, and edac is: > EDAC MC: Ver: 2.1.0 Oct 16 2009 > There are 2 sockets in the system. > I don't see those addresses in the output of lspci. It is looking glum, if my BIOS is hiding buses. However, once I verify that that is the case, I'll contact someone on the ROM team to check on that. You might ask someone on your ROM team. > If I look at another board with Nehalem, not running my kernel, should I see those buses? (does not show up on a DL380 G6 running SLES11 default kernel either) No. There is something weird going on with the Xeons. For some reason vendors are not listing the cpu pci busses in ACPI, when the kernel boots it will not know about the devices. The i7core driver created a hook to directly probe these device at module load time. Without loading the module you won't see the devices in lspci or any other place. After you load or attempt to load you should see the device if they are really there at 0xff and below. Thanks, Keith > I could not get git to connect from my dev server. So I went to git and found your latest tree and clicked on it. > http://git.kernel.org/?p=linux/kernel/git/mchehab/i7core.git;a=summary > > Then I went down to linux_next, clicked on it and grabbed a snapshot from the top of the tree. > > > > -----Original Message----- > From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org] > Sent: Tuesday, October 20, 2009 5:48 PM > To: Colbert, Rusty > Cc: Keith Mannthey; Doug Thompson; bluesmoke ML > Subject: Re: Module loads but has error. > > Hi Rusty, > > Em Tue, 20 Oct 2009 14:18:20 -0700 > Keith Mannthey <kmannth@us.ibm.com> escreveu: > > > On Tue, 2009-10-20 at 14:05 -0700, Doug Thompson wrote: > > > Copying Mauro on this one as he has the lead on it. He is currently in Japan for a few days for the kernel summit > > > > > > doug t > > > > > > --- On Tue, 10/20/09, Colbert, Rusty <rusty.colbert@hp.com> wrote: > > > > > > > From: Colbert, Rusty <rusty.colbert@hp.com> > > > > Subject: Module loads but has error. > > > > To: "bluesmoke ML" <bluesmoke-devel@lists.sourceforge.net> > > > > Date: Tuesday, October 20, 2009, 11:03 AM > > > > > > > > EDAC > > > > i7core: Device not > > > > found: dev 03.0 PCI ID 8086:2c18 > > > > Rusty, > > Are you using the current i7core git tree? What version of the kernel > > are you using? > > > > How many sockets do you have in your system? > > > > Are there any other edac printk statements? Could you enable > > EDAC_DEBUG and see if you get any more output? > > > > After you try and load the driver what does lspci show? > > Probably it didn't recognize the PCI buses 0xff and 0xfe. > > Be sure to be using the linux-next branch from my -git tree (or from the > official linux-next tree), since it has all needed patches and fixes needed for > PCI device for it to work. > > One of the tests machine is a Xeon 5550 (motherboard uses a Supermicro model > X8DTN with Intel(R) Xeon(R) CPU X5550 @ 2.67GHz CPUs - not sure whose manufactured > it, since I'm using it remotely), so I'm pretty sure that it works on such CPU's. > > Those are the expected results: > > # dmesg|grep -i edac > [ 23.866982] EDAC MC: Ver: 2.1.0 Oct 19 2009 > [ 23.867007] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867030] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867054] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867077] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867097] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867117] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867137] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867157] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867178] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867199] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867219] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867239] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867258] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867277] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867295] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867315] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867334] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867353] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867372] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867391] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867409] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867428] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867447] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867466] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867502] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867532] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867562] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867593] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867625] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867702] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867734] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867765] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867797] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867837] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867871] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867904] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867937] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.867970] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868006] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868040] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868079] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868116] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868151] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868186] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868225] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868264] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() > [ 23.868422] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 1028: edac_sysfs_setup_mc_kset() > [ 23.868553] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 1045: edac_sysfs_setup_mc_kset() Registered '.../edac/mc' kobject > [ 23.917015] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 2030: MC: drivers/edac/i7core_edac.c: i7core_init() > [ 23.952493] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.0 PCI ID 8086:2c18 > [ 23.952585] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.0 PCI ID 8086:2c18 > [ 23.952723] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.1 PCI ID 8086:2c19 > [ 23.952778] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.1 PCI ID 8086:2c19 > [ 23.952898] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.2 PCI ID 8086:2c1a > [ 23.952964] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.2 PCI ID 8086:2c1a > [ 23.953159] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.4 PCI ID 8086:2c1c > [ 23.953224] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.4 PCI ID 8086:2c1c > [ 23.953357] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.0 PCI ID 8086:2c20 > [ 23.953407] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.0 PCI ID 8086:2c20 > [ 23.953546] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.1 PCI ID 8086:2c21 > [ 23.953621] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.1 PCI ID 8086:2c21 > [ 23.953750] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.2 PCI ID 8086:2c22 > [ 23.953796] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.2 PCI ID 8086:2c22 > [ 23.953950] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.3 PCI ID 8086:2c23 > [ 23.954006] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.3 PCI ID 8086:2c23 > [ 23.954152] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.0 PCI ID 8086:2c28 > [ 23.954195] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.0 PCI ID 8086:2c28 > [ 23.954285] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.1 PCI ID 8086:2c29 > [ 23.954330] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.1 PCI ID 8086:2c29 > [ 23.954471] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.2 PCI ID 8086:2c2a > [ 23.954539] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.2 PCI ID 8086:2c2a > [ 23.954690] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.3 PCI ID 8086:2c2b > [ 23.954748] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.3 PCI ID 8086:2c2b > [ 23.954888] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.0 PCI ID 8086:2c30 > [ 23.954947] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.0 PCI ID 8086:2c30 > [ 23.955098] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.1 PCI ID 8086:2c31 > [ 23.955153] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.1 PCI ID 8086:2c31 > [ 23.955259] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.2 PCI ID 8086:2c32 > [ 23.955315] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.2 PCI ID 8086:2c32 > [ 23.955435] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.3 PCI ID 8086:2c33 > [ 23.955488] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.3 PCI ID 8086:2c33 > [ 23.955715] i7core_edac: detected a Nehalem Memory Controller > [ 23.955724] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:00.0 PCI ID 8086:2c41 > [ 23.955874] i7core_edac: detected a Nehalem Memory Controller > [ 23.955886] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:00.0 PCI ID 8086:2c41 > [ 23.956042] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 513: Number of active channels on socket 0: 2 > [ 23.956077] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 670: edac_mc_register_sysfs_main_kobj() > [ 23.956397] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 706: edac_mc_register_sysfs_main_kobj() Registered '.../edac/mc0' kobject > [ 23.956409] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1821: MC: drivers/edac/i7core_edac.c: i7core_register_mci(): mci = ffff8801398e8000 > [ 23.956435] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.0, dev = ffff88013e1cf000, socket 0 > [ 23.956444] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.1, dev = ffff88013e1cf800, socket 0 > [ 23.956452] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.2, dev = ffff88013e1cb000, socket 0 > [ 23.956462] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.4, dev = ffff88013e1c8800, socket 0 > [ 23.956483] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.0, dev = ffff88013c7df000, socket 0 > [ 23.956490] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.1, dev = ffff88013c7df800, socket 0 > [ 23.956499] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.2, dev = ffff88013c7de000, socket 0 > [ 23.956508] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.3, dev = ffff88013c7de800, socket 0 > [ 23.956515] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.0, dev = ffff88013c7dd000, socket 0 > [ 23.956523] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.1, dev = ffff88013c7dd800, socket 0 > [ 23.956529] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.2, dev = ffff88013a2d8000, socket 0 > [ 23.956534] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.3, dev = ffff88013a2d8800, socket 0 > [ 23.956541] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.0, dev = ffff88013a2d9000, socket 0 > [ 23.956549] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.1, dev = ffff88013a2d9800, socket 0 > [ 23.956555] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.2, dev = ffff88013a2da000, socket 0 > [ 23.956561] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.3, dev = ffff88013a2da800, socket 0 > [ 23.956566] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 0.0, dev = ffff88013e1c8000, socket 0 > [ 23.956578] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 541: QPI 0 control=0x00000602 status=0x00000019 dod=0x00000090 map=0x00024489 > [ 23.956583] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 545: ECC enabled with x8 SDCC > [ 23.956590] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 564: DOD Max limits: DIMMS: 1, 1-ranked, 8-banked x4000 x 0x400 > [ 23.956596] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 573: Channel 0 is not active > [ 23.956614] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch1 phy rd1, wr1 (0x063ffc31): 2 ranks, RDIMMs > [ 23.956620] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 > [ 23.956641] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [1] DIVBY3 REMOVED OFFSET > [ 23.956646] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956651] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956657] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956661] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956665] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956673] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956680] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956685] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956695] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch2 phy rd3, wr3 (0x063ffc31): 2 ranks, RDIMMs > [ 23.956705] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 > [ 23.956733] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [2] DIVBY3 REMOVED OFFSET > [ 23.956740] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956748] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956754] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956760] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956767] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956774] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956780] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956785] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.956793] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 473: edac_mc_add_mc() > [ 23.956827] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 911: edac_create_sysfs_mci_device() idx=0 > [ 23.956880] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() > [ 23.956885] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_section > [ 23.956918] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_type > [ 23.956953] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_eccmask > [ 23.956993] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 818: edac_create_mci_instance_attributes() grp inject_addrmatch, mci ffff8801398e8000 > [ 23.957074] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() > [ 23.957082] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file channel > [ 23.957106] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file dimm > [ 23.957132] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file rank > [ 23.957159] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file bank > [ 23.957183] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file page > [ 23.957212] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file col > [ 23.957246] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_enable > [ 23.957878] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 296: edac_mc_workq_setup() > [ 23.957892] EDAC MC0: Giving out device to 'i7core_edac.c' 'i7 core #0': DEV 0000:ff:03.0 > [ 23.957899] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 49: edac_pci_alloc_ctl_info() > [ 23.957920] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 346: edac_pci_add_device() > [ 23.957946] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 126: add_edac_pci_to_global_list() > [ 23.957953] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 101: find_edac_pci_by_dev() > [ 23.957961] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 444: edac_pci_create_sysfs() idx=0 > [ 23.957966] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 347: edac_pci_main_kobj_setup() > [ 23.958246] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 394: Registered '.../edac/pci' kobject > [ 23.958254] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 163: edac_pci_create_instance_kobj() > [ 23.958436] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 186: edac_pci_create_instance_kobj() Register instance 'pci0' kobject > [ 23.958468] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 274: edac_pci_workq_setup() > [ 23.958474] EDAC PCI0: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:ff:03.0' (POLLED) > [ 23.958511] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 513: Number of active channels on socket 1: 2 > [ 23.958526] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 670: edac_mc_register_sysfs_main_kobj() > [ 23.962494] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 706: edac_mc_register_sysfs_main_kobj() Registered '.../edac/mc1' kobject > [ 23.962503] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1821: MC: drivers/edac/i7core_edac.c: i7core_register_mci(): mci = ffff8801398ea000 > [ 23.962533] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.0, dev = ffff88013a2de000, socket 1 > [ 23.962539] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.1, dev = ffff88013a2de800, socket 1 > [ 23.962545] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.2, dev = ffff88013a2df000, socket 1 > [ 23.962549] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.4, dev = ffff88013a2df800, socket 1 > [ 23.962554] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.0, dev = ffff88013a2f0000, socket 1 > [ 23.962561] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.1, dev = ffff88013a2f0800, socket 1 > [ 23.962571] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.2, dev = ffff88013a2f1000, socket 1 > [ 23.962582] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.3, dev = ffff88013a2f1800, socket 1 > [ 23.962595] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.0, dev = ffff88013a2f2000, socket 1 > [ 23.962609] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.1, dev = ffff88013a2f2800, socket 1 > [ 23.962622] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.2, dev = ffff88013a2f3000, socket 1 > [ 23.962630] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.3, dev = ffff88013a2f3800, socket 1 > [ 23.962645] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.0, dev = ffff88013cfc2800, socket 1 > [ 23.962653] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.1, dev = ffff88013cfc3000, socket 1 > [ 23.962662] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.2, dev = ffff88013cfc1800, socket 1 > [ 23.962674] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.3, dev = ffff88013cfc4800, socket 1 > [ 23.962682] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 0.0, dev = ffff88013a2db000, socket 1 > [ 23.962712] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 541: QPI 1 control=0x00000602 status=0x00000019 dod=0x00000090 map=0x00024489 > [ 23.962724] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 545: ECC enabled with x8 SDCC > [ 23.962737] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 564: DOD Max limits: DIMMS: 1, 1-ranked, 8-banked x4000 x 0x400 > [ 23.962745] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 573: Channel 0 is not active > [ 23.962766] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch1 phy rd1, wr1 (0x063ffc31): 2 ranks, RDIMMs > [ 23.962779] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 > [ 23.962810] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [1] DIVBY3 REMOVED OFFSET > [ 23.962822] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962830] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962836] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962845] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962853] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962860] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962869] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962876] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962894] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch2 phy rd3, wr3 (0x063ffc31): 2 ranks, RDIMMs > [ 23.962903] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 > [ 23.962943] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [2] DIVBY3 REMOVED OFFSET > [ 23.962954] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962966] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962978] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962987] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.962995] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.963005] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.963012] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.963021] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 > [ 23.963033] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 473: edac_mc_add_mc() > [ 23.963044] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 911: edac_create_sysfs_mci_device() idx=1 > [ 23.963093] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() > [ 23.963105] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_section > [ 23.963134] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_type > [ 23.963161] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_eccmask > [ 23.963202] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 818: edac_create_mci_instance_attributes() grp inject_addrmatch, mci ffff8801398ea000 > [ 23.963278] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() > [ 23.963287] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file channel > [ 23.963669] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file dimm > [ 23.963713] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file rank > [ 23.963749] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file bank > [ 23.963786] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file page > [ 23.963838] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file col > [ 23.963878] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_enable > [ 23.964601] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 296: edac_mc_workq_setup() > [ 23.964613] EDAC MC1: Giving out device to 'i7core_edac.c' 'i7 core #1': DEV 0000:fe:03.0 > [ 23.964624] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 49: edac_pci_alloc_ctl_info() > [ 23.964644] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 346: edac_pci_add_device() > [ 23.964655] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 126: add_edac_pci_to_global_list() > [ 23.964663] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 101: find_edac_pci_by_dev() > [ 23.964671] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 444: edac_pci_create_sysfs() idx=1 > [ 23.964678] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 347: edac_pci_main_kobj_setup() > [ 23.964689] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 163: edac_pci_create_instance_kobj() > [ 23.964918] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 186: edac_pci_create_instance_kobj() Register instance 'pci1' kobject > [ 23.964971] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 274: edac_pci_workq_setup() > [ 23.964978] EDAC PCI1: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:fe:03.0' (POLLED) > [ 23.964985] EDAC i7core: Driver loaded. > > Also, you should be able to see the PCI buses ff and fe: > > # lspci -n|grep ^f > fe:00.0 0600: 8086:2c40 (rev 04) > fe:00.1 0600: 8086:2c01 (rev 04) > fe:02.0 0600: 8086:2c10 (rev 04) > fe:02.1 0600: 8086:2c11 (rev 04) > fe:02.4 0600: 8086:2c14 (rev 04) > fe:02.5 0600: 8086:2c15 (rev 04) > fe:03.0 0600: 8086:2c18 (rev 04) > fe:03.1 0600: 8086:2c19 (rev 04) > fe:03.2 0600: 8086:2c1a (rev 04) > fe:03.4 0600: 8086:2c1c (rev 04) > fe:04.0 0600: 8086:2c20 (rev 04) > fe:04.1 0600: 8086:2c21 (rev 04) > fe:04.2 0600: 8086:2c22 (rev 04) > fe:04.3 0600: 8086:2c23 (rev 04) > fe:05.0 0600: 8086:2c28 (rev 04) > fe:05.1 0600: 8086:2c29 (rev 04) > fe:05.2 0600: 8086:2c2a (rev 04) > fe:05.3 0600: 8086:2c2b (rev 04) > fe:06.0 0600: 8086:2c30 (rev 04) > fe:06.1 0600: 8086:2c31 (rev 04) > fe:06.2 0600: 8086:2c32 (rev 04) > fe:06.3 0600: 8086:2c33 (rev 04) > ff:00.0 0600: 8086:2c40 (rev 04) > ff:00.1 0600: 8086:2c01 (rev 04) > ff:02.0 0600: 8086:2c10 (rev 04) > ff:02.1 0600: 8086:2c11 (rev 04) > ff:02.4 0600: 8086:2c14 (rev 04) > ff:02.5 0600: 8086:2c15 (rev 04) > ff:03.0 0600: 8086:2c18 (rev 04) > ff:03.1 0600: 8086:2c19 (rev 04) > ff:03.2 0600: 8086:2c1a (rev 04) > ff:03.4 0600: 8086:2c1c (rev 04) > ff:04.0 0600: 8086:2c20 (rev 04) > ff:04.1 0600: 8086:2c21 (rev 04) > ff:04.2 0600: 8086:2c22 (rev 04) > ff:04.3 0600: 8086:2c23 (rev 04) > ff:05.0 0600: 8086:2c28 (rev 04) > ff:05.1 0600: 8086:2c29 (rev 04) > ff:05.2 0600: 8086:2c2a (rev 04) > ff:05.3 0600: 8086:2c2b (rev 04) > ff:06.0 0600: 8086:2c30 (rev 04) > ff:06.1 0600: 8086:2c31 (rev 04) > ff:06.2 0600: 8086:2c32 (rev 04) > ff:06.3 0600: 8086:2c33 (rev 04) > > If you are not noticing the PCI devices starting with fe: and ff: and are using > my latest tree, then it is likely that your motherboard BIOS is doing something > weird to hide the Nehalem non-core PCI buses. > > > > > > Thanks, > > Keith Mannthey > > LTC Real-Time > > > > > > > > > > > > > > This would seem to be the > > > > PCI_DEVICE_ID_INTEL_I7_MCR > > > > > > > > > > > > > > > > The modules are loaded, but I think this > > > > error may have caused them to > > > > be ineffective. There are no files under > > > > /sys/devices/system/edac/mc as in > > > > older edac enabled kernels. > > > > > > > > > > > > > > > > I have access to multiple platforms and > > > > can acquire DIMMs with ECC > > > > errors, but I don't see the point in installing them if > > > > the driver is not > > > > installing properly. > > > > > > > > > > > > > > > > I am currently running on an HP ProLiant DL360. It > > > > has > > > > Intel Xeon CPUs X5550. > > > > > > > > Any pointers on how I should approach > > > > debugging this? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > > > ------------------------------------------------------------------------------ > > > > Come build with us! The BlackBerry(R) Developer Conference > > > > in SF, CA > > > > is the only developer event you need to attend this year. > > > > Jumpstart your > > > > developing skills, take BlackBerry mobile applications to > > > > market and stay > > > > ahead of the curve. Join us from November 9 - 12, 2009. > > > > Register now! > > > > http://p.sf.net/sfu/devconference > > > > -----Inline Attachment Follows----- > > > > > > > > _______________________________________________ > > > > bluesmoke-devel mailing list > > > > bluesmoke-devel@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > > > > > > > > ------------------------------------------------------------------------------ > > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > > is the only developer event you need to attend this year. Jumpstart your > > > developing skills, take BlackBerry mobile applications to market and stay > > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > > http://p.sf.net/sfu/devconference > > > _______________________________________________ > > > bluesmoke-devel mailing list > > > bluesmoke-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > bluesmoke-devel mailing list > > bluesmoke-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > > > Cheers, > Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Module loads but has error. 2009-10-21 15:26 ` Keith Mannthey @ 2009-10-21 20:03 ` Mauro Carvalho Chehab 2009-10-21 20:58 ` Colbert, Rusty 0 siblings, 1 reply; 14+ messages in thread From: Mauro Carvalho Chehab @ 2009-10-21 20:03 UTC (permalink / raw) To: Keith Mannthey; +Cc: Doug Thompson, bluesmoke ML Em Wed, 21 Oct 2009 08:26:10 -0700 Keith Mannthey <kmannth@us.ibm.com> escreveu: > On Wed, 2009-10-21 at 14:13 +0000, Colbert, Rusty wrote: > > It was a linux-next tree and is identified as 2.6.32-rc4, and edac is: > > EDAC MC: Ver: 2.1.0 Oct 16 2009 > > There are 2 sockets in the system. > > I don't see those addresses in the output of lspci. It is looking glum, if my BIOS is hiding buses. However, once I verify that that is the case, I'll contact someone on the ROM team to check on that. > > You might ask someone on your ROM team. Yes. A worthy trial would be to use lastbus=255 pci parameter during the boot. > > If I look at another board with Nehalem, not running my kernel, should I see those buses? (does not show up on a DL380 G6 running SLES11 default kernel either) > > No. There is something weird going on with the Xeons. For some reason > vendors are not listing the cpu pci busses in ACPI, when the kernel > boots it will not know about the devices. The i7core driver created a > hook to directly probe these device at module load time. > > Without loading the module you won't see the devices in lspci or any > other place. After you load or attempt to load you should see the device > if they are really there at 0xff and below. It should also be added that, with some other memory controller drivers, it was noticed that some BIOS have the bad habit of protecting the memory registers via SMI. While we haven't observed this behavior yet with Nehalem, I don't doubt it will happen with certain devices. Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Module loads but has error. 2009-10-21 20:03 ` Mauro Carvalho Chehab @ 2009-10-21 20:58 ` Colbert, Rusty 2009-10-21 23:03 ` Mauro Carvalho Chehab 0 siblings, 1 reply; 14+ messages in thread From: Colbert, Rusty @ 2009-10-21 20:58 UTC (permalink / raw) To: Mauro Carvalho Chehab, Keith Mannthey; +Cc: Doug Thompson, bluesmoke ML Outstanding! That shows the buses, though they are at 3e and 3f. I now have Myriagon_Memory_Tester:~ # find /sys/devices/system/edac/ -type d /sys/devices/system/edac/ /sys/devices/system/edac/mc /sys/devices/system/edac/mc/mc193 /sys/devices/system/edac/mc/mc193/inject_addrmatch /sys/devices/system/edac/mc/mc193/csrow0 /sys/devices/system/edac/mc/mc0 /sys/devices/system/edac/mc/mc0/inject_addrmatch /sys/devices/system/edac/mc/mc0/csrow0 /sys/devices/system/edac/pci /sys/devices/system/edac/pci/pci0 /sys/devices/system/edac/pci/pci1 And 3e:00.0 0600: 8086:2c40 (rev 04) 3e:00.1 0600: 8086:2c01 (rev 04) 3e:02.0 0600: 8086:2c10 (rev 04) 3e:02.1 0600: 8086:2c11 (rev 04) 3e:02.4 0600: 8086:2c14 (rev 04) 3e:02.5 0600: 8086:2c15 (rev 04) 3e:03.0 0600: 8086:2c18 (rev 04) 3e:03.1 0600: 8086:2c19 (rev 04) 3e:03.2 0600: 8086:2c1a (rev 04) 3e:03.4 0600: 8086:2c1c (rev 04) 3e:04.0 0600: 8086:2c20 (rev 04) 3e:04.1 0600: 8086:2c21 (rev 04) 3e:04.2 0600: 8086:2c22 (rev 04) 3e:04.3 0600: 8086:2c23 (rev 04) 3e:05.0 0600: 8086:2c28 (rev 04) 3e:05.1 0600: 8086:2c29 (rev 04) 3e:05.2 0600: 8086:2c2a (rev 04) 3e:05.3 0600: 8086:2c2b (rev 04) 3e:06.0 0600: 8086:2c30 (rev 04) 3e:06.1 0600: 8086:2c31 (rev 04) 3e:06.2 0600: 8086:2c32 (rev 04) 3e:06.3 0600: 8086:2c33 (rev 04) 3f:00.0 0600: 8086:2c40 (rev 04) 3f:00.1 0600: 8086:2c01 (rev 04) 3f:02.0 0600: 8086:2c10 (rev 04) 3f:02.1 0600: 8086:2c11 (rev 04) 3f:02.4 0600: 8086:2c14 (rev 04) 3f:02.5 0600: 8086:2c15 (rev 04) 3f:03.0 0600: 8086:2c18 (rev 04) 3f:03.1 0600: 8086:2c19 (rev 04) 3f:03.2 0600: 8086:2c1a (rev 04) 3f:03.4 0600: 8086:2c1c (rev 04) 3f:04.0 0600: 8086:2c20 (rev 04) 3f:04.1 0600: 8086:2c21 (rev 04) 3f:04.2 0600: 8086:2c22 (rev 04) 3f:04.3 0600: 8086:2c23 (rev 04) 3f:05.0 0600: 8086:2c28 (rev 04) 3f:05.1 0600: 8086:2c29 (rev 04) 3f:05.2 0600: 8086:2c2a (rev 04) 3f:05.3 0600: 8086:2c2b (rev 04) 3f:06.0 0600: 8086:2c30 (rev 04) 3f:06.1 0600: 8086:2c31 (rev 04) 3f:06.2 0600: 8086:2c32 (rev 04) 3f:06.3 0600: 8086:2c33 (rev 04) -----Original Message----- From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org] Sent: Wednesday, October 21, 2009 3:04 PM To: Keith Mannthey Cc: Colbert, Rusty; Doug Thompson; bluesmoke ML Subject: Re: Module loads but has error. Em Wed, 21 Oct 2009 08:26:10 -0700 Keith Mannthey <kmannth@us.ibm.com> escreveu: > On Wed, 2009-10-21 at 14:13 +0000, Colbert, Rusty wrote: > > It was a linux-next tree and is identified as 2.6.32-rc4, and edac is: > > EDAC MC: Ver: 2.1.0 Oct 16 2009 > > There are 2 sockets in the system. > > I don't see those addresses in the output of lspci. It is looking glum, if my BIOS is hiding buses. However, once I verify that that is the case, I'll contact someone on the ROM team to check on that. > > You might ask someone on your ROM team. Yes. A worthy trial would be to use lastbus=255 pci parameter during the boot. > > If I look at another board with Nehalem, not running my kernel, should I see those buses? (does not show up on a DL380 G6 running SLES11 default kernel either) > > No. There is something weird going on with the Xeons. For some reason > vendors are not listing the cpu pci busses in ACPI, when the kernel > boots it will not know about the devices. The i7core driver created a > hook to directly probe these device at module load time. > > Without loading the module you won't see the devices in lspci or any > other place. After you load or attempt to load you should see the device > if they are really there at 0xff and below. It should also be added that, with some other memory controller drivers, it was noticed that some BIOS have the bad habit of protecting the memory registers via SMI. While we haven't observed this behavior yet with Nehalem, I don't doubt it will happen with certain devices. Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Module loads but has error. 2009-10-21 20:58 ` Colbert, Rusty @ 2009-10-21 23:03 ` Mauro Carvalho Chehab 2009-10-22 15:04 ` Colbert, Rusty 0 siblings, 1 reply; 14+ messages in thread From: Mauro Carvalho Chehab @ 2009-10-21 23:03 UTC (permalink / raw) To: Colbert, Rusty; +Cc: Doug Thompson, bluesmoke ML Em Wed, 21 Oct 2009 20:58:40 +0000 "Colbert, Rusty" <rusty.colbert@hp.com> escreveu: > Outstanding! > That shows the buses, though they are at 3e and 3f. That's weird! They weren't supposed to be at 3e and 3f. The driver will wrongly associate the memory controller numbers in this case. > I now have > Myriagon_Memory_Tester:~ # find /sys/devices/system/edac/ -type d > /sys/devices/system/edac/ > /sys/devices/system/edac/mc > /sys/devices/system/edac/mc/mc193 > /sys/devices/system/edac/mc/mc193/inject_addrmatch > /sys/devices/system/edac/mc/mc193/csrow0 Yes, here it is: it is calling mc1 as 193, since the driver is doing 0xff-0x3f to compute the number of the processor socket... I don't think this would have any real impact, but for sure it should be fixed. The basic question is: why on your machines it is using a different bus address. Could you please email the output of cat /proc/cpuinfo? I'll also see if I can find a machine similar to yours on Red Hat labs for doing some tests on it. > /sys/devices/system/edac/mc/mc0 > /sys/devices/system/edac/mc/mc0/inject_addrmatch > /sys/devices/system/edac/mc/mc0/csrow0 > /sys/devices/system/edac/pci > /sys/devices/system/edac/pci/pci0 > /sys/devices/system/edac/pci/pci1 > > > And > 3e:00.0 0600: 8086:2c40 (rev 04) > 3e:00.1 0600: 8086:2c01 (rev 04) > 3e:02.0 0600: 8086:2c10 (rev 04) > 3e:02.1 0600: 8086:2c11 (rev 04) > 3e:02.4 0600: 8086:2c14 (rev 04) > 3e:02.5 0600: 8086:2c15 (rev 04) > 3e:03.0 0600: 8086:2c18 (rev 04) > 3e:03.1 0600: 8086:2c19 (rev 04) > 3e:03.2 0600: 8086:2c1a (rev 04) > 3e:03.4 0600: 8086:2c1c (rev 04) > 3e:04.0 0600: 8086:2c20 (rev 04) > 3e:04.1 0600: 8086:2c21 (rev 04) > 3e:04.2 0600: 8086:2c22 (rev 04) > 3e:04.3 0600: 8086:2c23 (rev 04) > 3e:05.0 0600: 8086:2c28 (rev 04) > 3e:05.1 0600: 8086:2c29 (rev 04) > 3e:05.2 0600: 8086:2c2a (rev 04) > 3e:05.3 0600: 8086:2c2b (rev 04) > 3e:06.0 0600: 8086:2c30 (rev 04) > 3e:06.1 0600: 8086:2c31 (rev 04) > 3e:06.2 0600: 8086:2c32 (rev 04) > 3e:06.3 0600: 8086:2c33 (rev 04) > 3f:00.0 0600: 8086:2c40 (rev 04) > 3f:00.1 0600: 8086:2c01 (rev 04) > 3f:02.0 0600: 8086:2c10 (rev 04) > 3f:02.1 0600: 8086:2c11 (rev 04) > 3f:02.4 0600: 8086:2c14 (rev 04) > 3f:02.5 0600: 8086:2c15 (rev 04) > 3f:03.0 0600: 8086:2c18 (rev 04) > 3f:03.1 0600: 8086:2c19 (rev 04) > 3f:03.2 0600: 8086:2c1a (rev 04) > 3f:03.4 0600: 8086:2c1c (rev 04) > 3f:04.0 0600: 8086:2c20 (rev 04) > 3f:04.1 0600: 8086:2c21 (rev 04) > 3f:04.2 0600: 8086:2c22 (rev 04) > 3f:04.3 0600: 8086:2c23 (rev 04) > 3f:05.0 0600: 8086:2c28 (rev 04) > 3f:05.1 0600: 8086:2c29 (rev 04) > 3f:05.2 0600: 8086:2c2a (rev 04) > 3f:05.3 0600: 8086:2c2b (rev 04) > 3f:06.0 0600: 8086:2c30 (rev 04) > 3f:06.1 0600: 8086:2c31 (rev 04) > 3f:06.2 0600: 8086:2c32 (rev 04) > 3f:06.3 0600: 8086:2c33 (rev 04) > > > > -----Original Message----- > From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org] > Sent: Wednesday, October 21, 2009 3:04 PM > To: Keith Mannthey > Cc: Colbert, Rusty; Doug Thompson; bluesmoke ML > Subject: Re: Module loads but has error. > > Em Wed, 21 Oct 2009 08:26:10 -0700 > Keith Mannthey <kmannth@us.ibm.com> escreveu: > > > On Wed, 2009-10-21 at 14:13 +0000, Colbert, Rusty wrote: > > > It was a linux-next tree and is identified as 2.6.32-rc4, and edac is: > > > EDAC MC: Ver: 2.1.0 Oct 16 2009 > > > There are 2 sockets in the system. > > > I don't see those addresses in the output of lspci. It is looking glum, if my BIOS is hiding buses. However, once I verify that that is the case, I'll contact someone on the ROM team to check on that. > > > > You might ask someone on your ROM team. > > Yes. A worthy trial would be to use lastbus=255 pci parameter during the boot. > > > > If I look at another board with Nehalem, not running my kernel, should I see those buses? (does not show up on a DL380 G6 running SLES11 default kernel either) > > > > No. There is something weird going on with the Xeons. For some reason > > vendors are not listing the cpu pci busses in ACPI, when the kernel > > boots it will not know about the devices. The i7core driver created a > > hook to directly probe these device at module load time. > > > > Without loading the module you won't see the devices in lspci or any > > other place. After you load or attempt to load you should see the device > > if they are really there at 0xff and below. > > It should also be added that, with some other memory controller drivers, it was > noticed that some BIOS have the bad habit of protecting the memory registers > via SMI. While we haven't observed this behavior yet with Nehalem, I don't > doubt it will happen with certain devices. > > Cheers, > Mauro Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Module loads but has error. 2009-10-21 23:03 ` Mauro Carvalho Chehab @ 2009-10-22 15:04 ` Colbert, Rusty 2009-10-22 20:02 ` Mauro Carvalho Chehab 0 siblings, 1 reply; 14+ messages in thread From: Colbert, Rusty @ 2009-10-22 15:04 UTC (permalink / raw) To: Mauro Carvalho Chehab; +Cc: Doug Thompson, bluesmoke ML Cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 6 model name : Intel(R) Xeon(TM) MV CPU 3.20GHz stepping : 4 cpu MHz : 3200.369 cache size : 2048 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow bogomips : 6400.73 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 6 model name : Intel(R) Xeon(TM) MV CPU 3.20GHz stepping : 4 cpu MHz : 3200.369 cache size : 2048 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow bogomips : 6400.32 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 15 model : 6 model name : Intel(R) Xeon(TM) MV CPU 3.20GHz stepping : 4 cpu MHz : 3200.369 cache size : 2048 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow bogomips : 6400.33 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 15 model : 6 model name : Intel(R) Xeon(TM) MV CPU 3.20GHz stepping : 4 cpu MHz : 3200.369 cache size : 2048 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow bogomips : 6400.30 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: -----Original Message----- From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org] Sent: Wednesday, October 21, 2009 6:04 PM To: Colbert, Rusty Cc: Keith Mannthey; Doug Thompson; bluesmoke ML Subject: Re: Module loads but has error. Em Wed, 21 Oct 2009 20:58:40 +0000 "Colbert, Rusty" <rusty.colbert@hp.com> escreveu: > Outstanding! > That shows the buses, though they are at 3e and 3f. That's weird! They weren't supposed to be at 3e and 3f. The driver will wrongly associate the memory controller numbers in this case. > I now have > Myriagon_Memory_Tester:~ # find /sys/devices/system/edac/ -type d > /sys/devices/system/edac/ > /sys/devices/system/edac/mc > /sys/devices/system/edac/mc/mc193 > /sys/devices/system/edac/mc/mc193/inject_addrmatch > /sys/devices/system/edac/mc/mc193/csrow0 Yes, here it is: it is calling mc1 as 193, since the driver is doing 0xff-0x3f to compute the number of the processor socket... I don't think this would have any real impact, but for sure it should be fixed. The basic question is: why on your machines it is using a different bus address. Could you please email the output of cat /proc/cpuinfo? I'll also see if I can find a machine similar to yours on Red Hat labs for doing some tests on it. > /sys/devices/system/edac/mc/mc0 > /sys/devices/system/edac/mc/mc0/inject_addrmatch > /sys/devices/system/edac/mc/mc0/csrow0 > /sys/devices/system/edac/pci > /sys/devices/system/edac/pci/pci0 > /sys/devices/system/edac/pci/pci1 > > > And > 3e:00.0 0600: 8086:2c40 (rev 04) > 3e:00.1 0600: 8086:2c01 (rev 04) > 3e:02.0 0600: 8086:2c10 (rev 04) > 3e:02.1 0600: 8086:2c11 (rev 04) > 3e:02.4 0600: 8086:2c14 (rev 04) > 3e:02.5 0600: 8086:2c15 (rev 04) > 3e:03.0 0600: 8086:2c18 (rev 04) > 3e:03.1 0600: 8086:2c19 (rev 04) > 3e:03.2 0600: 8086:2c1a (rev 04) > 3e:03.4 0600: 8086:2c1c (rev 04) > 3e:04.0 0600: 8086:2c20 (rev 04) > 3e:04.1 0600: 8086:2c21 (rev 04) > 3e:04.2 0600: 8086:2c22 (rev 04) > 3e:04.3 0600: 8086:2c23 (rev 04) > 3e:05.0 0600: 8086:2c28 (rev 04) > 3e:05.1 0600: 8086:2c29 (rev 04) > 3e:05.2 0600: 8086:2c2a (rev 04) > 3e:05.3 0600: 8086:2c2b (rev 04) > 3e:06.0 0600: 8086:2c30 (rev 04) > 3e:06.1 0600: 8086:2c31 (rev 04) > 3e:06.2 0600: 8086:2c32 (rev 04) > 3e:06.3 0600: 8086:2c33 (rev 04) > 3f:00.0 0600: 8086:2c40 (rev 04) > 3f:00.1 0600: 8086:2c01 (rev 04) > 3f:02.0 0600: 8086:2c10 (rev 04) > 3f:02.1 0600: 8086:2c11 (rev 04) > 3f:02.4 0600: 8086:2c14 (rev 04) > 3f:02.5 0600: 8086:2c15 (rev 04) > 3f:03.0 0600: 8086:2c18 (rev 04) > 3f:03.1 0600: 8086:2c19 (rev 04) > 3f:03.2 0600: 8086:2c1a (rev 04) > 3f:03.4 0600: 8086:2c1c (rev 04) > 3f:04.0 0600: 8086:2c20 (rev 04) > 3f:04.1 0600: 8086:2c21 (rev 04) > 3f:04.2 0600: 8086:2c22 (rev 04) > 3f:04.3 0600: 8086:2c23 (rev 04) > 3f:05.0 0600: 8086:2c28 (rev 04) > 3f:05.1 0600: 8086:2c29 (rev 04) > 3f:05.2 0600: 8086:2c2a (rev 04) > 3f:05.3 0600: 8086:2c2b (rev 04) > 3f:06.0 0600: 8086:2c30 (rev 04) > 3f:06.1 0600: 8086:2c31 (rev 04) > 3f:06.2 0600: 8086:2c32 (rev 04) > 3f:06.3 0600: 8086:2c33 (rev 04) > > > > -----Original Message----- > From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org] > Sent: Wednesday, October 21, 2009 3:04 PM > To: Keith Mannthey > Cc: Colbert, Rusty; Doug Thompson; bluesmoke ML > Subject: Re: Module loads but has error. > > Em Wed, 21 Oct 2009 08:26:10 -0700 > Keith Mannthey <kmannth@us.ibm.com> escreveu: > > > On Wed, 2009-10-21 at 14:13 +0000, Colbert, Rusty wrote: > > > It was a linux-next tree and is identified as 2.6.32-rc4, and edac is: > > > EDAC MC: Ver: 2.1.0 Oct 16 2009 > > > There are 2 sockets in the system. > > > I don't see those addresses in the output of lspci. It is looking glum, if my BIOS is hiding buses. However, once I verify that that is the case, I'll contact someone on the ROM team to check on that. > > > > You might ask someone on your ROM team. > > Yes. A worthy trial would be to use lastbus=255 pci parameter during the boot. > > > > If I look at another board with Nehalem, not running my kernel, should I see those buses? (does not show up on a DL380 G6 running SLES11 default kernel either) > > > > No. There is something weird going on with the Xeons. For some reason > > vendors are not listing the cpu pci busses in ACPI, when the kernel > > boots it will not know about the devices. The i7core driver created a > > hook to directly probe these device at module load time. > > > > Without loading the module you won't see the devices in lspci or any > > other place. After you load or attempt to load you should see the device > > if they are really there at 0xff and below. > > It should also be added that, with some other memory controller drivers, it was > noticed that some BIOS have the bad habit of protecting the memory registers > via SMI. While we haven't observed this behavior yet with Nehalem, I don't > doubt it will happen with certain devices. > > Cheers, > Mauro Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Module loads but has error. 2009-10-22 15:04 ` Colbert, Rusty @ 2009-10-22 20:02 ` Mauro Carvalho Chehab 2009-10-22 20:26 ` Colbert, Rusty 0 siblings, 1 reply; 14+ messages in thread From: Mauro Carvalho Chehab @ 2009-10-22 20:02 UTC (permalink / raw) To: Colbert, Rusty; +Cc: Doug Thompson, bluesmoke ML Em Thu, 22 Oct 2009 15:04:18 +0000 "Colbert, Rusty" <rusty.colbert@hp.com> escreveu: > Cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 15 > model : 6 > model name : Intel(R) Xeon(TM) MV CPU 3.20GHz > stepping : 4 > cpu MHz : 3200.369 > cache size : 2048 KB > physical id : 0 > siblings : 4 > core id : 0 > cpu cores : 2 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 6 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow > bogomips : 6400.73 > clflush size : 64 > cache_alignment : 128 > address sizes : 36 bits physical, 48 bits virtual > power management: Ok, this is where the things diverge. This is the cpu model on my test machine: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 1596.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5336.25 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: So, basically, your CPU model is 6, while mine is 26. According with: http://www.intel.com/support/processors/xeon5k/sb/cs-022297.htm The MV processor is a Xeon 5063, being part of Xeon 5000 series. The Intel datasheets for this series doesn't mention a memory controller on it. It was covered only by this spec update: http://www.intel.com/Assets/en_US/PDF/specupdate/313065.pdf AFAIK, the Xeon 5000 series were not meant to have a memory controller inside, but I suspect that this MV chip has the same memory controller as a Xeon 35xx. We need to double check this with Intel, to be sure that it is safe to enable EDAC on those machines. Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Module loads but has error. 2009-10-22 20:02 ` Mauro Carvalho Chehab @ 2009-10-22 20:26 ` Colbert, Rusty 0 siblings, 0 replies; 14+ messages in thread From: Colbert, Rusty @ 2009-10-22 20:26 UTC (permalink / raw) To: Mauro Carvalho Chehab; +Cc: Doug Thompson, bluesmoke ML Ooops. Too many balls in the air, dropped this one. I must have ran in the wrong putty window. Sorry about that. Here is the correct one: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.70 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 1 siblings : 8 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 16 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.39 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 0 siblings : 8 core id : 2 cpu cores : 4 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.35 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 1 siblings : 8 core id : 2 cpu cores : 4 apicid : 20 initial apicid : 20 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.38 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 4 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 0 siblings : 8 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.36 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 5 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 1 siblings : 8 core id : 1 cpu cores : 4 apicid : 18 initial apicid : 18 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.38 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 6 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.36 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 1 siblings : 8 core id : 3 cpu cores : 4 apicid : 22 initial apicid : 22 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.40 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 8 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.36 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 9 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 1 siblings : 8 core id : 0 cpu cores : 4 apicid : 17 initial apicid : 17 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.37 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 10 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 0 siblings : 8 core id : 2 cpu cores : 4 apicid : 5 initial apicid : 5 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.36 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 11 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 1 siblings : 8 core id : 2 cpu cores : 4 apicid : 21 initial apicid : 21 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.36 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 12 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 0 siblings : 8 core id : 1 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.35 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 13 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 1 siblings : 8 core id : 1 cpu cores : 4 apicid : 19 initial apicid : 19 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.37 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 14 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.36 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 15 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 2666.853 cache size : 8192 KB physical id : 1 siblings : 8 core id : 3 cpu cores : 4 apicid : 23 initial apicid : 23 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5333.38 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: -----Original Message----- From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org] Sent: Thursday, October 22, 2009 3:03 PM To: Colbert, Rusty Cc: Keith Mannthey; Doug Thompson; bluesmoke ML Subject: Re: Module loads but has error. Em Thu, 22 Oct 2009 15:04:18 +0000 "Colbert, Rusty" <rusty.colbert@hp.com> escreveu: > Cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 15 > model : 6 > model name : Intel(R) Xeon(TM) MV CPU 3.20GHz > stepping : 4 > cpu MHz : 3200.369 > cache size : 2048 KB > physical id : 0 > siblings : 4 > core id : 0 > cpu cores : 2 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 6 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow > bogomips : 6400.73 > clflush size : 64 > cache_alignment : 128 > address sizes : 36 bits physical, 48 bits virtual > power management: Ok, this is where the things diverge. This is the cpu model on my test machine: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5550 @ 2.67GHz stepping : 4 cpu MHz : 1596.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5336.25 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: So, basically, your CPU model is 6, while mine is 26. According with: http://www.intel.com/support/processors/xeon5k/sb/cs-022297.htm The MV processor is a Xeon 5063, being part of Xeon 5000 series. The Intel datasheets for this series doesn't mention a memory controller on it. It was covered only by this spec update: http://www.intel.com/Assets/en_US/PDF/specupdate/313065.pdf AFAIK, the Xeon 5000 series were not meant to have a memory controller inside, but I suspect that this MV chip has the same memory controller as a Xeon 35xx. We need to double check this with Intel, to be sure that it is safe to enable EDAC on those machines. Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Module loads but has error. 2009-10-20 22:47 ` Mauro Carvalho Chehab 2009-10-21 14:13 ` Colbert, Rusty @ 2009-10-21 17:55 ` Colbert, Rusty 2009-10-21 20:15 ` Mauro Carvalho Chehab 1 sibling, 1 reply; 14+ messages in thread From: Colbert, Rusty @ 2009-10-21 17:55 UTC (permalink / raw) To: Mauro Carvalho Chehab; +Cc: Doug Thompson, bluesmoke ML [-- Attachment #1.1: Type: text/plain, Size: 34618 bytes --] I checked my tree against a fresh linux-next download and found no differences in the edac dir. However, my DEBUG output has a different line number for i7core_init. I cannot find your updated i7core_edac.c. EDAC DEBUG: in /usr/src/linux-2.6.34-edac-memtest/drivers/edac/edac_mc_sysfs.c, line at 1028: edac_sysfs_setup_mc_kset() EDAC DEBUG: in /usr/src/linux-2.6.34-edac-memtest/drivers/edac/edac_mc_sysfs.c, line at 1045: edac_sysfs_setup_mc_kset() Registered '.../edac/mc' kobject EDAC DEBUG: in /usr/src/linux-2.6.34-edac-memtest/drivers/edac/i7core_edac.c, line at 1947: MC: /usr/src/linux-2.6.34-edac-memtest/drivers/edac/i7core_edac.c: i7core_init() EDAC i7core: Device not found: dev 03.0 PCI ID 8086:2c18 -----Original Message----- From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org] Sent: Tuesday, October 20, 2009 5:48 PM To: Colbert, Rusty Cc: Keith Mannthey; Doug Thompson; bluesmoke ML Subject: Re: Module loads but has error. Hi Rusty, Em Tue, 20 Oct 2009 14:18:20 -0700 Keith Mannthey <kmannth@us.ibm.com> escreveu: > On Tue, 2009-10-20 at 14:05 -0700, Doug Thompson wrote: > > Copying Mauro on this one as he has the lead on it. He is currently in Japan for a few days for the kernel summit > > > > doug t > > > > --- On Tue, 10/20/09, Colbert, Rusty <rusty.colbert@hp.com> wrote: > > > > > From: Colbert, Rusty <rusty.colbert@hp.com> > > > Subject: Module loads but has error. > > > To: "bluesmoke ML" <bluesmoke-devel@lists.sourceforge.net> > > > Date: Tuesday, October 20, 2009, 11:03 AM > > > > > > EDAC > > > i7core: Device not > > > found: dev 03.0 PCI ID 8086:2c18 > > Rusty, > Are you using the current i7core git tree? What version of the kernel > are you using? > > How many sockets do you have in your system? > > Are there any other edac printk statements? Could you enable > EDAC_DEBUG and see if you get any more output? > > After you try and load the driver what does lspci show? Probably it didn't recognize the PCI buses 0xff and 0xfe. Be sure to be using the linux-next branch from my -git tree (or from the official linux-next tree), since it has all needed patches and fixes needed for PCI device for it to work. One of the tests machine is a Xeon 5550 (motherboard uses a Supermicro model X8DTN with Intel(R) Xeon(R) CPU X5550 @ 2.67GHz CPUs - not sure whose manufactured it, since I'm using it remotely), so I'm pretty sure that it works on such CPU's. Those are the expected results: # dmesg|grep -i edac [ 23.866982] EDAC MC: Ver: 2.1.0 Oct 19 2009 [ 23.867007] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867030] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867054] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867077] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867097] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867117] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867137] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867157] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867178] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867199] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867219] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867239] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867258] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867277] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867295] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867315] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867334] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867353] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867372] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867391] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867409] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867428] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867447] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867466] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867502] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867532] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867562] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867593] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867625] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867702] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867734] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867765] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867797] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867837] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867871] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867904] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867937] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.867970] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868006] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868040] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868079] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868116] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868151] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868186] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868225] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868264] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 537: edac_pci_dev_parity_clear() [ 23.868422] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 1028: edac_sysfs_setup_mc_kset() [ 23.868553] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 1045: edac_sysfs_setup_mc_kset() Registered '.../edac/mc' kobject [ 23.917015] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 2030: MC: drivers/edac/i7core_edac.c: i7core_init() [ 23.952493] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.0 PCI ID 8086:2c18 [ 23.952585] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.0 PCI ID 8086:2c18 [ 23.952723] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.1 PCI ID 8086:2c19 [ 23.952778] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.1 PCI ID 8086:2c19 [ 23.952898] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.2 PCI ID 8086:2c1a [ 23.952964] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.2 PCI ID 8086:2c1a [ 23.953159] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:03.4 PCI ID 8086:2c1c [ 23.953224] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:03.4 PCI ID 8086:2c1c [ 23.953357] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.0 PCI ID 8086:2c20 [ 23.953407] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.0 PCI ID 8086:2c20 [ 23.953546] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.1 PCI ID 8086:2c21 [ 23.953621] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.1 PCI ID 8086:2c21 [ 23.953750] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.2 PCI ID 8086:2c22 [ 23.953796] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.2 PCI ID 8086:2c22 [ 23.953950] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:04.3 PCI ID 8086:2c23 [ 23.954006] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:04.3 PCI ID 8086:2c23 [ 23.954152] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.0 PCI ID 8086:2c28 [ 23.954195] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.0 PCI ID 8086:2c28 [ 23.954285] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.1 PCI ID 8086:2c29 [ 23.954330] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.1 PCI ID 8086:2c29 [ 23.954471] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.2 PCI ID 8086:2c2a [ 23.954539] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.2 PCI ID 8086:2c2a [ 23.954690] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:05.3 PCI ID 8086:2c2b [ 23.954748] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:05.3 PCI ID 8086:2c2b [ 23.954888] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.0 PCI ID 8086:2c30 [ 23.954947] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.0 PCI ID 8086:2c30 [ 23.955098] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.1 PCI ID 8086:2c31 [ 23.955153] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.1 PCI ID 8086:2c31 [ 23.955259] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.2 PCI ID 8086:2c32 [ 23.955315] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.2 PCI ID 8086:2c32 [ 23.955435] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:06.3 PCI ID 8086:2c33 [ 23.955488] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:06.3 PCI ID 8086:2c33 [ 23.955715] i7core_edac: detected a Nehalem Memory Controller [ 23.955724] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 0 dev ff:00.0 PCI ID 8086:2c41 [ 23.955874] i7core_edac: detected a Nehalem Memory Controller [ 23.955886] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1342: Detected socket 1 dev fe:00.0 PCI ID 8086:2c41 [ 23.956042] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 513: Number of active channels on socket 0: 2 [ 23.956077] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 670: edac_mc_register_sysfs_main_kobj() [ 23.956397] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 706: edac_mc_register_sysfs_main_kobj() Registered '.../edac/mc0' kobject [ 23.956409] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1821: MC: drivers/edac/i7core_edac.c: i7core_register_mci(): mci = ffff8801398e8000 [ 23.956435] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.0, dev = ffff88013e1cf000, socket 0 [ 23.956444] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.1, dev = ffff88013e1cf800, socket 0 [ 23.956452] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.2, dev = ffff88013e1cb000, socket 0 [ 23.956462] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.4, dev = ffff88013e1c8800, socket 0 [ 23.956483] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.0, dev = ffff88013c7df000, socket 0 [ 23.956490] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.1, dev = ffff88013c7df800, socket 0 [ 23.956499] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.2, dev = ffff88013c7de000, socket 0 [ 23.956508] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.3, dev = ffff88013c7de800, socket 0 [ 23.956515] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.0, dev = ffff88013c7dd000, socket 0 [ 23.956523] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.1, dev = ffff88013c7dd800, socket 0 [ 23.956529] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.2, dev = ffff88013a2d8000, socket 0 [ 23.956534] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.3, dev = ffff88013a2d8800, socket 0 [ 23.956541] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.0, dev = ffff88013a2d9000, socket 0 [ 23.956549] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.1, dev = ffff88013a2d9800, socket 0 [ 23.956555] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.2, dev = ffff88013a2da000, socket 0 [ 23.956561] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.3, dev = ffff88013a2da800, socket 0 [ 23.956566] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 0.0, dev = ffff88013e1c8000, socket 0 [ 23.956578] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 541: QPI 0 control=0x00000602 status=0x00000019 dod=0x00000090 map=0x00024489 [ 23.956583] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 545: ECC enabled with x8 SDCC [ 23.956590] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 564: DOD Max limits: DIMMS: 1, 1-ranked, 8-banked x4000 x 0x400 [ 23.956596] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 573: Channel 0 is not active [ 23.956614] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch1 phy rd1, wr1 (0x063ffc31): 2 ranks, RDIMMs [ 23.956620] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.956641] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [1] DIVBY3 REMOVED OFFSET [ 23.956646] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956651] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956657] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956661] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956665] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956673] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956680] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956685] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956695] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch2 phy rd3, wr3 (0x063ffc31): 2 ranks, RDIMMs [ 23.956705] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.956733] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [2] DIVBY3 REMOVED OFFSET [ 23.956740] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956748] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956754] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956760] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956767] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956774] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956780] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956785] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.956793] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 473: edac_mc_add_mc() [ 23.956827] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 911: edac_create_sysfs_mci_device() idx=0 [ 23.956880] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.956885] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_section [ 23.956918] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_type [ 23.956953] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_eccmask [ 23.956993] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 818: edac_create_mci_instance_attributes() grp inject_addrmatch, mci ffff8801398e8000 [ 23.957074] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.957082] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file channel [ 23.957106] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file dimm [ 23.957132] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file rank [ 23.957159] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file bank [ 23.957183] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file page [ 23.957212] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file col [ 23.957246] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_enable [ 23.957878] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 296: edac_mc_workq_setup() [ 23.957892] EDAC MC0: Giving out device to 'i7core_edac.c' 'i7 core #0': DEV 0000:ff:03.0 [ 23.957899] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 49: edac_pci_alloc_ctl_info() [ 23.957920] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 346: edac_pci_add_device() [ 23.957946] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 126: add_edac_pci_to_global_list() [ 23.957953] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 101: find_edac_pci_by_dev() [ 23.957961] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 444: edac_pci_create_sysfs() idx=0 [ 23.957966] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 347: edac_pci_main_kobj_setup() [ 23.958246] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 394: Registered '.../edac/pci' kobject [ 23.958254] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 163: edac_pci_create_instance_kobj() [ 23.958436] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 186: edac_pci_create_instance_kobj() Register instance 'pci0' kobject [ 23.958468] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 274: edac_pci_workq_setup() [ 23.958474] EDAC PCI0: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:ff:03.0' (POLLED) [ 23.958511] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 513: Number of active channels on socket 1: 2 [ 23.958526] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 670: edac_mc_register_sysfs_main_kobj() [ 23.962494] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 706: edac_mc_register_sysfs_main_kobj() Registered '.../edac/mc1' kobject [ 23.962503] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1821: MC: drivers/edac/i7core_edac.c: i7core_register_mci(): mci = ffff8801398ea000 [ 23.962533] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.0, dev = ffff88013a2de000, socket 1 [ 23.962539] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.1, dev = ffff88013a2de800, socket 1 [ 23.962545] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.2, dev = ffff88013a2df000, socket 1 [ 23.962549] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 3.4, dev = ffff88013a2df800, socket 1 [ 23.962554] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.0, dev = ffff88013a2f0000, socket 1 [ 23.962561] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.1, dev = ffff88013a2f0800, socket 1 [ 23.962571] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.2, dev = ffff88013a2f1000, socket 1 [ 23.962582] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 4.3, dev = ffff88013a2f1800, socket 1 [ 23.962595] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.0, dev = ffff88013a2f2000, socket 1 [ 23.962609] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.1, dev = ffff88013a2f2800, socket 1 [ 23.962622] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.2, dev = ffff88013a2f3000, socket 1 [ 23.962630] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 5.3, dev = ffff88013a2f3800, socket 1 [ 23.962645] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.0, dev = ffff88013cfc2800, socket 1 [ 23.962653] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.1, dev = ffff88013cfc3000, socket 1 [ 23.962662] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.2, dev = ffff88013cfc1800, socket 1 [ 23.962674] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 6.3, dev = ffff88013cfc4800, socket 1 [ 23.962682] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 1403: Associated fn 0.0, dev = ffff88013a2db000, socket 1 [ 23.962712] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 541: QPI 1 control=0x00000602 status=0x00000019 dod=0x00000090 map=0x00024489 [ 23.962724] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 545: ECC enabled with x8 SDCC [ 23.962737] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 564: DOD Max limits: DIMMS: 1, 1-ranked, 8-banked x4000 x 0x400 [ 23.962745] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 573: Channel 0 is not active [ 23.962766] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch1 phy rd1, wr1 (0x063ffc31): 2 ranks, RDIMMs [ 23.962779] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.962810] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [1] DIVBY3 REMOVED OFFSET [ 23.962822] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962830] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962836] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962845] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962853] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962860] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962869] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962876] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962894] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 617: Ch2 phy rd3, wr3 (0x063ffc31): 2 ranks, RDIMMs [ 23.962903] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 640: dimm 0 1024 Mb offset: 0, bank: 8, rank: 1, row: 0x4000, col: 0x400 [ 23.962943] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 692: [2] DIVBY3 REMOVED OFFSET [ 23.962954] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962966] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962978] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962987] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.962995] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963005] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963012] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963021] EDAC DEBUG: in drivers/edac/i7core_edac.c, line at 697: 0x0 0x0 0x0 [ 23.963033] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 473: edac_mc_add_mc() [ 23.963044] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 911: edac_create_sysfs_mci_device() idx=1 [ 23.963093] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.963105] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_section [ 23.963134] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_type [ 23.963161] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_eccmask [ 23.963202] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 818: edac_create_mci_instance_attributes() grp inject_addrmatch, mci ffff8801398ea000 [ 23.963278] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 802: edac_create_mci_instance_attributes() [ 23.963287] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file channel [ 23.963669] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file dimm [ 23.963713] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file rank [ 23.963749] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file bank [ 23.963786] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file page [ 23.963838] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file col [ 23.963878] EDAC DEBUG: in drivers/edac/edac_mc_sysfs.c, line at 835: edac_create_mci_instance_attributes() file inject_enable [ 23.964601] EDAC DEBUG: in drivers/edac/edac_mc.c, line at 296: edac_mc_workq_setup() [ 23.964613] EDAC MC1: Giving out device to 'i7core_edac.c' 'i7 core #1': DEV 0000:fe:03.0 [ 23.964624] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 49: edac_pci_alloc_ctl_info() [ 23.964644] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 346: edac_pci_add_device() [ 23.964655] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 126: add_edac_pci_to_global_list() [ 23.964663] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 101: find_edac_pci_by_dev() [ 23.964671] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 444: edac_pci_create_sysfs() idx=1 [ 23.964678] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 347: edac_pci_main_kobj_setup() [ 23.964689] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 163: edac_pci_create_instance_kobj() [ 23.964918] EDAC DEBUG: in drivers/edac/edac_pci_sysfs.c, line at 186: edac_pci_create_instance_kobj() Register instance 'pci1' kobject [ 23.964971] EDAC DEBUG: in drivers/edac/edac_pci.c, line at 274: edac_pci_workq_setup() [ 23.964978] EDAC PCI1: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:fe:03.0' (POLLED) [ 23.964985] EDAC i7core: Driver loaded. Also, you should be able to see the PCI buses ff and fe: # lspci -n|grep ^f fe:00.0 0600: 8086:2c40 (rev 04) fe:00.1 0600: 8086:2c01 (rev 04) fe:02.0 0600: 8086:2c10 (rev 04) fe:02.1 0600: 8086:2c11 (rev 04) fe:02.4 0600: 8086:2c14 (rev 04) fe:02.5 0600: 8086:2c15 (rev 04) fe:03.0 0600: 8086:2c18 (rev 04) fe:03.1 0600: 8086:2c19 (rev 04) fe:03.2 0600: 8086:2c1a (rev 04) fe:03.4 0600: 8086:2c1c (rev 04) fe:04.0 0600: 8086:2c20 (rev 04) fe:04.1 0600: 8086:2c21 (rev 04) fe:04.2 0600: 8086:2c22 (rev 04) fe:04.3 0600: 8086:2c23 (rev 04) fe:05.0 0600: 8086:2c28 (rev 04) fe:05.1 0600: 8086:2c29 (rev 04) fe:05.2 0600: 8086:2c2a (rev 04) fe:05.3 0600: 8086:2c2b (rev 04) fe:06.0 0600: 8086:2c30 (rev 04) fe:06.1 0600: 8086:2c31 (rev 04) fe:06.2 0600: 8086:2c32 (rev 04) fe:06.3 0600: 8086:2c33 (rev 04) ff:00.0 0600: 8086:2c40 (rev 04) ff:00.1 0600: 8086:2c01 (rev 04) ff:02.0 0600: 8086:2c10 (rev 04) ff:02.1 0600: 8086:2c11 (rev 04) ff:02.4 0600: 8086:2c14 (rev 04) ff:02.5 0600: 8086:2c15 (rev 04) ff:03.0 0600: 8086:2c18 (rev 04) ff:03.1 0600: 8086:2c19 (rev 04) ff:03.2 0600: 8086:2c1a (rev 04) ff:03.4 0600: 8086:2c1c (rev 04) ff:04.0 0600: 8086:2c20 (rev 04) ff:04.1 0600: 8086:2c21 (rev 04) ff:04.2 0600: 8086:2c22 (rev 04) ff:04.3 0600: 8086:2c23 (rev 04) ff:05.0 0600: 8086:2c28 (rev 04) ff:05.1 0600: 8086:2c29 (rev 04) ff:05.2 0600: 8086:2c2a (rev 04) ff:05.3 0600: 8086:2c2b (rev 04) ff:06.0 0600: 8086:2c30 (rev 04) ff:06.1 0600: 8086:2c31 (rev 04) ff:06.2 0600: 8086:2c32 (rev 04) ff:06.3 0600: 8086:2c33 (rev 04) If you are not noticing the PCI devices starting with fe: and ff: and are using my latest tree, then it is likely that your motherboard BIOS is doing something weird to hide the Nehalem non-core PCI buses. > > Thanks, > Keith Mannthey > LTC Real-Time > > > > > > > > > > This would seem to be the > > > PCI_DEVICE_ID_INTEL_I7_MCR > > > > > > > > > > > > The modules are loaded, but I think this > > > error may have caused them to > > > be ineffective. There are no files under > > > /sys/devices/system/edac/mc as in > > > older edac enabled kernels. > > > > > > > > > > > > I have access to multiple platforms and > > > can acquire DIMMs with ECC > > > errors, but I don't see the point in installing them if > > > the driver is not > > > installing properly. > > > > > > > > > > > > I am currently running on an HP ProLiant DL360. It > > > has > > > Intel Xeon CPUs X5550. > > > > > > Any pointers on how I should approach > > > debugging this? > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > ------------------------------------------------------------------------------ > > > Come build with us! The BlackBerry(R) Developer Conference > > > in SF, CA > > > is the only developer event you need to attend this year. > > > Jumpstart your > > > developing skills, take BlackBerry mobile applications to > > > market and stay > > > ahead of the curve. Join us from November 9 - 12, 2009. > > > Register now! > > > http://p.sf.net/sfu/devconference > > > -----Inline Attachment Follows----- > > > > > > _______________________________________________ > > > bluesmoke-devel mailing list > > > bluesmoke-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > bluesmoke-devel mailing list > > bluesmoke-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > bluesmoke-devel mailing list > bluesmoke-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel Cheers, Mauro [-- Attachment #1.2: Type: text/html, Size: 87735 bytes --] [-- Attachment #2: Type: text/plain, Size: 399 bytes --] ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference [-- Attachment #3: Type: text/plain, Size: 176 bytes --] _______________________________________________ bluesmoke-devel mailing list bluesmoke-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Module loads but has error. 2009-10-21 17:55 ` Colbert, Rusty @ 2009-10-21 20:15 ` Mauro Carvalho Chehab 0 siblings, 0 replies; 14+ messages in thread From: Mauro Carvalho Chehab @ 2009-10-21 20:15 UTC (permalink / raw) To: Colbert, Rusty; +Cc: Doug Thompson, bluesmoke ML Em Wed, 21 Oct 2009 17:55:51 +0000 "Colbert, Rusty" <rusty.colbert@hp.com> escreveu: > I checked my tree against a fresh linux-next download and found no differences in the edac dir. However, my DEBUG output has a different line number for i7core_init. I cannot find your updated i7core_edac.c. > > > > EDAC DEBUG: in /usr/src/linux-2.6.34-edac-memtest/drivers/edac/edac_mc_sysfs.c, line at 1028: edac_sysfs_setup_mc_kset() > > EDAC DEBUG: in /usr/src/linux-2.6.34-edac-memtest/drivers/edac/edac_mc_sysfs.c, line at 1045: edac_sysfs_setup_mc_kset() Registered '.../edac/mc' kobject > > EDAC DEBUG: in /usr/src/linux-2.6.34-edac-memtest/drivers/edac/i7core_edac.c, line at 1947: MC: /usr/src/linux-2.6.34-edac-memtest/drivers/edac/i7core_edac.c: i7core_init() > EDAC i7core: Device not found: dev 03.0 PCI ID 8086:2c18 > The version I've ran the tests is a version where there were some new patches applied there, that are under tests. As none of the patches touch the PCI ID detection, this shouldn't cause any differences for you. Cheers, Mauro ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2009-10-22 20:26 UTC | newest] Thread overview: 14+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-10-20 17:03 Module loads but has error Colbert, Rusty 2009-10-20 21:05 ` Doug Thompson 2009-10-20 21:18 ` Keith Mannthey 2009-10-20 22:47 ` Mauro Carvalho Chehab 2009-10-21 14:13 ` Colbert, Rusty 2009-10-21 15:26 ` Keith Mannthey 2009-10-21 20:03 ` Mauro Carvalho Chehab 2009-10-21 20:58 ` Colbert, Rusty 2009-10-21 23:03 ` Mauro Carvalho Chehab 2009-10-22 15:04 ` Colbert, Rusty 2009-10-22 20:02 ` Mauro Carvalho Chehab 2009-10-22 20:26 ` Colbert, Rusty 2009-10-21 17:55 ` Colbert, Rusty 2009-10-21 20:15 ` Mauro Carvalho Chehab
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox