Re: Hardware failure?: Now what? Is this worth pursuing?

2021-03-23 Thread Charles Curley
On Tue, 23 Mar 2021 22:03:08 +0100 Sven Hartge wrote: > Other than that: Intel has acknowledged the defect as an official > erro^Werratum and documented it. So "case closed" in that regard. Agreed. Thanks. -- Does anybody read signatures any more? https://charlescurley.com

Re: Hardware failure?: Now what? Is this worth pursuing?

2021-03-23 Thread Sven Hartge
Charles Curley wrote: > On Mon, 22 Mar 2021 13:52:27 -0600 Charles Curley > wrote: >> I ran an amd64 VM for 24 hours, and no errors. I just fired up a 486 >> VM, and no errors. I will let that run 24 hours and see what that >> does. >> >> The i386 VM is "qemu32". I see a kvm32 in my list of

Re: Hardware failure?: Now what? Is this worth pursuing?

2021-03-23 Thread Charles Curley
On Mon, 22 Mar 2021 13:52:27 -0600 Charles Curley wrote: > I ran an amd64 VM for 24 hours, and no errors. I just fired up a 486 > VM, and no errors. I will let that run 24 hours and see what that > does. > > The i386 VM is "qemu32". I see a kvm32 in my list of options. I may > try that as well.

Re: Hardware failure?: Now what?

2021-03-22 Thread Charles Curley
On Sat, 20 Mar 2021 20:09:24 -0600 Charles Curley wrote: > I have a number of amd64 VMs, and I do not recall seeing this error > before. If I can run those without this error, that will narrow things > down to the i386 VM, and that may be worth a bug report. I ran an amd64 VM for 24 hours, and

Re: Hardware failure?: Now what?

2021-03-20 Thread Dan Ritter
Charles Curley wrote: > > 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? 4 cores, 8 threads. As others are pointing out, this could be thermal. Clean the fan, consider replacing the power

Re: Hardware failure?: Now what?

2021-03-20 Thread Andy Smith
Hi, On Sat, Mar 20, 2021 at 02:29:25PM -0600, Charles Curley wrote: > MCE events: > 1 2021-03-20 13:58:30 -0600 error: Internal parity error, mcg mcgstatus=0, > mci Corrected_error Error_enabled, mcgcap=0x0c09, > status=0x904f0005, tsc=0xf442c87fda, walltime=0x605653e5, >

Re: Hardware failure?: Now what?

2021-03-20 Thread Sven Hartge
Charles Curley wrote: > 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

Hardware failure?: Now what?

2021-03-20 Thread Charles Curley
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