Date: Wed, 29 Jan 2014 20:06:38 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Tim Daneliuk <tundra@tundraware.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Kernel Geniuses: Need Help With MCA Code Message-ID: <CA%2BtpaK0u%2B6DLKmd-MCdML4HZ5m6a80Ax5Nx=7HRngfhvEOTJEg@mail.gmail.com> In-Reply-To: <52E73717.3000503@tundraware.com> References: <52E73717.3000503@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 27, 2014 at 10:50 PM, Tim Daneliuk <tundra@tundraware.com>wrote:
>
>
> I've swapped CPUs (i5). I've fiddled with an endless supply of
> mobo settings. I've switched power supplies. I've moved mem
> sticks around .... No joy.
>
Looks like the only thing left is rpl to start pulling out dimms.
So, I dug through the sources and found this:
>
>
>
> mca_log(const struct mca_record *rec)
> {
> uint16_t mca_error;
>
> printf("MCA: Bank %d, Status 0x%016llx\n", rec->mr_bank,
> (long long)rec->mr_status);
> printf("MCA: Global Cap 0x%016llx, Status 0x%016llx\n",
> (long long)rec->mr_mcg_cap, (long long)rec->mr_mcg_status);
> printf("MCA: Vendor \"%s\", ID 0x%x, APIC ID %d\n", cpu_vendor,
> rec->mr_cpu_id, rec->mr_apic_id);
> printf("MCA: CPU %d ", rec->mr_cpu);
> if (rec->mr_status & MC_STATUS_UC)
> printf("UNCOR ");
> else {
> printf("COR ");
> if (rec->mr_mcg_cap & MCG_CAP_CMCI_P)
> printf("(%lld) ", ((long long)rec->mr_status &
> MC_STATUS_COR_COUNT) >> 38);
> }
>
>
> It looks like the trailing else clause is kicking out the error but I am
> unclear what the error means, beyond the fact that it appears to be a
> parity
> error somewhere within the CPU's internal memory (cache?). Is this error
> getting corrected? Is this benign, Should I get a different mobo?
>
> Um .... Haaaaalp :)
A pity you didn't follow my earlier suggestion.
--
Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK0u%2B6DLKmd-MCdML4HZ5m6a80Ax5Nx=7HRngfhvEOTJEg>