What does this mean? kernel: MCA: Bank 4, Status 0x940c4001fe080813 kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 kernel: MCA: CPU 0 COR BUSLG Source RD Memory kernel: MCA: Address 0x7ff6b0 FreeBSD 7.3-STABLE #1: Sun Aug 22 23:16:43 -- Dan Langille - http://langille.org/
On 23/08/2010, at 10:48, Dan Langille wrote:> What does this mean? > > kernel: MCA: Bank 4, Status 0x940c4001fe080813 > kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 > kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 > kernel: MCA: CPU 0 COR BUSLG Source RD Memory > kernel: MCA: Address 0x7ff6b0 > > FreeBSD 7.3-STABLE #1: Sun Aug 22 23:16:43It's generated by machine check support, see.. /usr/src/sys/i386/i386/mca.c /usr/src/sys/amd64/amd64/mca.c Some info here.. http://en.wikipedia.org/wiki/Machine_check_architecture No man page for it though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
On 8/22/2010 9:18 PM, Dan Langille wrote:> What does this mean? > > kernel: MCA: Bank 4, Status 0x940c4001fe080813 > kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 > kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 > kernel: MCA: CPU 0 COR BUSLG Source RD Memory > kernel: MCA: Address 0x7ff6b0 > > FreeBSD 7.3-STABLE #1: Sun Aug 22 23:16:43And another one: kernel: MCA: Bank 4, Status 0x9459c0014a080813 kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 kernel: MCA: CPU 0 COR BUSLG Source RD Memory kernel: MCA: Address 0x7ff670 -- Dan Langille - http://langille.org/
on 23/08/2010 05:05 Dan Langille said the following:> On 8/22/2010 9:18 PM, Dan Langille wrote: >> What does this mean? >> >> kernel: MCA: Bank 4, Status 0x940c4001fe080813 >> kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 >> kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 >> kernel: MCA: CPU 0 COR BUSLG Source RD Memory >> kernel: MCA: Address 0x7ff6b0 >> >> FreeBSD 7.3-STABLE #1: Sun Aug 22 23:16:43 > > And another one: > > kernel: MCA: Bank 4, Status 0x9459c0014a080813 > kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 > kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 > kernel: MCA: CPU 0 COR BUSLG Source RD Memory > kernel: MCA: Address 0x7ff670I believe that you get correctable RAM ECC errors, but not entirely sure. There is mcelog utility that decodes such messages into human-friendly descriptions. The utility is available on Linux-based systems. John Baldwin has a port of it to FreeBSD, but it seems to be WIP and is private so far. Wait and watch John posting decoded text in this thread :-) -- Andriy Gapon
On 8/22/2010 10:05 PM, Dan Langille wrote:> On 8/22/2010 9:18 PM, Dan Langille wrote: >> What does this mean? >> >> kernel: MCA: Bank 4, Status 0x940c4001fe080813 >> kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 >> kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 >> kernel: MCA: CPU 0 COR BUSLG Source RD Memory >> kernel: MCA: Address 0x7ff6b0 >> >> FreeBSD 7.3-STABLE #1: Sun Aug 22 23:16:43 > > And another one: > > kernel: MCA: Bank 4, Status 0x9459c0014a080813 > kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 > kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 > kernel: MCA: CPU 0 COR BUSLG Source RD Memory > kernel: MCA: Address 0x7ff670kernel: MCA: Bank 4, Status 0x947ec000d8080a13 kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 kernel: MCA: CPU 0 COR BUSLG Responder RD Memory kernel: MCA: Address 0xbfa9930 Another one. These errors started appearing after upgrading to 8.1-STABLE from 7.2.. something. I suspect the functionality was added about then -- Dan Langille - http://langille.org/
on 24/08/2010 02:43 Dan Langille said the following:> On 8/22/2010 10:05 PM, Dan Langille wrote: >> On 8/22/2010 9:18 PM, Dan Langille wrote: >>> What does this mean? >>> >>> kernel: MCA: Bank 4, Status 0x940c4001fe080813 >>> kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 >>> kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 >>> kernel: MCA: CPU 0 COR BUSLG Source RD Memory >>> kernel: MCA: Address 0x7ff6b0 >>> >>> FreeBSD 7.3-STABLE #1: Sun Aug 22 23:16:43 >> >> And another one: >> >> kernel: MCA: Bank 4, Status 0x9459c0014a080813 >> kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 >> kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 >> kernel: MCA: CPU 0 COR BUSLG Source RD Memory >> kernel: MCA: Address 0x7ff670 > > kernel: MCA: Bank 4, Status 0x947ec000d8080a13 > kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 > kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 > kernel: MCA: CPU 0 COR BUSLG Responder RD Memory > kernel: MCA: Address 0xbfa9930 > > Another one. > > These errors started appearing after upgrading to 8.1-STABLE from 7.2.. > something. I suspect the functionality was added about thenPlease strop the flood :-) Depending on hardware there could be hundreds of such errors per day. Either replace memory modules or learn to live with these messages. -- Andriy Gapon
On Monday, August 23, 2010 5:35:40 pm Matthew D. Fuller wrote:> On Mon, Aug 23, 2010 at 08:20:35AM -0400 I heard the voice of > John Baldwin, and lo! it spake thus: > > > > It is not private, it is in //depot/projects/mcelog/... in p4. > > Which may as well be Siberia for us lowly non-developers. Any chance > you could stick a tarball or a patch against upstream mcelog > somewhere?It is actually public at perforce.freebsd.org. :) However, it is tedious to download the files. It really should be a port perhaps, though Someone (tm) should try to get the patches integrated upstream. You can find a patch at www.freebsd.org/~jhb/mcelog/. You will also need to download the memstream.c file from there as well and put that in the extracted mcelog tarball. -- John Baldwin
On 8/22/2010 9:18 PM, Dan Langille wrote:> What does this mean? > > kernel: MCA: Bank 4, Status 0x940c4001fe080813 > kernel: MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 > kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 > kernel: MCA: CPU 0 COR BUSLG Source RD Memory > kernel: MCA: Address 0x7ff6b0 > > FreeBSD 7.3-STABLE #1: Sun Aug 22 23:16:43FYI, these are occurring every hour, almost to the second. e.g. xx:56:yy, where yy is 09, 10, or 11. Checking logs, I don't see anything that correlates with this point in the hour (i.e 56 minutes past) that doesn't also occur at other times. It seems very odd to occur so regularly. -- Dan Langille - http://langille.org/
On Tue, Aug 24, 2010 at 4:06 PM, John Baldwin <jhb@freebsd.org> wrote:> On Monday, August 23, 2010 5:35:40 pm Matthew D. Fuller wrote: >> On Mon, Aug 23, 2010 at 08:20:35AM -0400 I heard the voice of >> John Baldwin, and lo! it spake thus: >> > >> > It is not private, it is in //depot/projects/mcelog/... in p4. >> >> Which may as well be Siberia for us lowly non-developers. ?Any chance >> you could stick a tarball or a patch against upstream mcelog >> somewhere? > > It is actually public at perforce.freebsd.org. :) ?However, it is tedious to > download the files. ?It really should be a port perhaps, though Someone (tm) > should try to get the patches integrated upstream. > > You can find a patch at www.freebsd.org/~jhb/mcelog/. ?You will also need to > download the memstream.c file from there as well and put that in the extracted > mcelog tarball. >I wrote a small script a while back to extract a tree from perforce using the web interface, might be handy: http://www.clearchain.com/~benjsc/downloads/FreeBSD/P4fetch.rb Cheers Tom