Messages in this thread | | | Date | Thu, 1 Jul 2010 08:26:05 +0200 | From | Borislav Petkov <> | Subject | Re: 2.6.34 Northbridge Chipset Errors on HP Proliant 4 x Opteron in x86_64 mode |
| |
From: Jeffrey Merkey <jeffmerkey@gmail.com> Date: Wed, Jun 30, 2010 at 01:21:04PM -0600
> > > > It looks like you don't have extended PCI config space accesses enabled > > on that machine. Can you send me the whole dmesg? > > > > Here is the complete dmesg log of the Northbridge chip error messages. > The drives report IO problems before the chip error message happens.
Jun 29 02:02:08 cloudstream kernel: Northbridge Error, node 0, core: 0 Jun 29 02:02:08 cloudstream kernel: ECC/ChipKill ECC error. Jun 29 02:02:08 cloudstream kernel: EDAC amd64 MC0: CE ERROR_ADDRESS= 0xc7358280 Jun 29 02:02:08 cloudstream kernel: EDAC amd64: get_channel_from_ecc_syndrome: error reading F3x180. Jun 29 02:02:08 cloudstream kernel: EDAC MC0: CE page 0xc7358, offset 0x280, grain 0, syndrome 0xa4c1, row 3, channel 0, label "": amd64_edac Jun 29 02:03:21 cloudstream kernel: Northbridge Error, node 0 Jun 29 02:03:21 cloudstream kernel: ECC/ChipKill ECC error. Jun 29 02:03:21 cloudstream kernel: EDAC amd64 MC0: CE ERROR_ADDRESS= 0xc7358280 Jun 29 02:03:21 cloudstream kernel: EDAC amd64: get_channel_from_ecc_syndrome: error reading F3x180. Jun 29 02:03:21 cloudstream kernel: EDAC MC0: CE page 0xc7358, offset 0x280, grain 0, syndrome 0xa4c1, row 3, channel 0, label "": amd64_edac
Right, this is the ECC happening. I asked about the dmesg because of the "error reading F3x180" but you have a K8 machine so no extended PCI config space there. And the error message is wrong there, I will move that F3x180 read behind a family check since it makes no sense to access that on K8.
Thanks.
-- Regards/Gruss, Boris.
| |