Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #233260
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Hardware failure?: Now what? |
| Date | 2021-03-20 22:00 +0100 |
| Message-ID | <BUQRr-4yf-1@gated-at.bofh.it> (permalink) |
| Organization | occasionally |
My syslog is reporting things like: Mar 20 13:58:29 hawk rasdaemon[892]: Calling ras_mc_event_opendb() Mar 20 13:58:29 hawk rasdaemon[892]: cpu 03:rasdaemon: mce_record store: 0x55c124c9b148 Mar 20 13:58:29 hawk kernel: [ 300.407406] mce: [Hardware Error]: Machine check events logged Mar 20 13:58:29 hawk kernel: [ 300.407410] mce: [Hardware Error]: CPU 3: Machine Check: 0 Bank 0: 90000040000f0005 Mar 20 13:58:29 hawk kernel: [ 300.407411] mce: [Hardware Error]: TSC f442c87fda Mar 20 13:58:29 hawk kernel: [ 300.407413] mce: [Hardware Error]: PROCESSOR 0:306c3 TIME 1616270309 SOCKET 0 APIC 6 microcode 19 Mar 20 13:58:29 hawk rasdaemon[892]: rasdaemon: register inserted at db root@hawk:/crc/back# ras-mc-ctl --errors No Memory errors. No PCIe AER errors. No Extlog errors. MCE events: 1 2021-03-20 13:58:30 -0600 error: Internal parity error, mcg mcgstatus=0, mci Corrected_error Error_enabled, mcgcap=0x00000c09, status=0x90000040000f0005, tsc=0xf442c87fda, walltime=0x605653e5, cpu=0x00000003, cpuid=0x000306c3, apicid=0x00000006 2 2021-03-20 14:07:07 -0600 error: Internal parity error, mcg mcgstatus=0, mci Corrected_error Error_enabled, mcgcap=0x00000c09, status=0x90000040000f0005, tsc=0x274d9e61020, walltime=0x605655ea, cpu=0x00000003, cpuid=0x000306c3, apicid=0x00000006 3 2021-03-20 14:07:07 -0600 error: Internal parity error, mcg mcgstatus=0, mci Corrected_error Error_enabled, mcgcap=0x00000c09, status=0x90000040000f0005, tsc=0x27517a5dacb, walltime=0x605655eb, cpu=0x00000003, cpuid=0x000306c3, apicid=0x00000006 4 2021-03-20 14:10:34 -0600 error: Internal parity error, mcg mcgstatus=0, mci Corrected_error Error_enabled, mcgcap=0x00000c09, status=0x90000040000f0005, tsc=0x30ea8517bee, walltime=0x605656b9, cpuid=0x000306c3 root@hawk:/crc/back# If I read that correctly, CPU 3 is seeing and correcting internal parity errors. The board is an ASUS H97M-E, bios date 05/15/2015. Processor is Intel(R) Core(TM) i7-4790S CPU @ 3.20GHz, with eight processors. Now what? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread
Hardware failure?: Now what? Charles Curley <charlescurley@charlescurley.com> - 2021-03-20 22:00 +0100
Re: Hardware failure?: Now what? Sven Hartge <sven@svenhartge.de> - 2021-03-20 22:20 +0100
Re: Hardware failure?: Now what? Andy Smith <andy@strugglers.net> - 2021-03-20 23:20 +0100
Re: Hardware failure?: Now what? Charles Curley <charlescurley@charlescurley.com> - 2021-03-21 03:40 +0100
Re: Hardware failure?: Now what? Charles Curley <charlescurley@charlescurley.com> - 2021-03-22 21:00 +0100
Re: Hardware failure?: Now what? Is this worth pursuing? Charles Curley <charlescurley@charlescurley.com> - 2021-03-23 21:40 +0100
Re: Hardware failure?: Now what? Is this worth pursuing? Sven Hartge <sven@svenhartge.de> - 2021-03-23 22:10 +0100
Re: Hardware failure?: Now what? Is this worth pursuing? Charles Curley <charlescurley@charlescurley.com> - 2021-03-23 22:30 +0100
Re: Hardware failure?: Now what? Dan Ritter <dsr@randomstring.org> - 2021-03-21 00:00 +0100
csiph-web