Am 10.06.23 um 14:58 schrieb Carl Hartung via openSUSE Users:
On Sat, 10 Jun 2023 13:52:11 +0200 Daniel Bauer wrote:
Hi,
I just bought a new intel-I7-mini pc (brand of a Spanish shop pccomoponentes, which doesn't exist in internet, so I don't know about the psysical details).
I installed OpenSuse 15.5 which went flawless, but later, during the first update, it suddenly shut down and rebooted.
This repeated several times, but the sudden shutdown/reboot occurs after different times in different situations. Because my first thought was that it's a memory problem I booted with memtest86 and let it run for approx. 5 hours (1 full pass plus some more) with no error reported.
In one occasion while running OS I got the following system messages:
8< - - - - - - snipped for brevity - - - - - - >8
My questions: - Can anyone decrypt those mce messages? - Is is clear that it is a hardware error or could it be a software thing?
Thanks for your hints!
Daniel
Hi Daniel,
This /could/ be a hardware problem /or/ a kernel bug, but it's a new 'mini' so you'd likely need some surgeon's tools and a steady hand to effect any repairs deeper than removing and replacing things at the board / device level -- if even that is possible. I think a more efficient test would involve exchanging the suspected 'defective' new unit with the seller so you can try to reproduce the problem with the replacement. I'm basing this approach on the following:
Machine check not valid Corrected error CPUID Vendor Intel Family 6 Model 142 Step 12 SOCKET 0 APIC 0 microcode ec Hardware event. This is not a software error. CPU 1 BANK 3 Processor context corrupt MCA: Internal Timer error
In the 'old days' with larger components, swapping out the CPU and memory, etc, would be easy. But this unit is new and under warranty (I presume) and swapping out components is likely more difficult, and, I suspect "Processor context corrupt" and "Internal Timer error" complaints are likely hardware.
regards,
Carl
Thank you Carl, yes, it's new and there is warranty. I'll try to send it back Monday. I just liked to have some feedback (like yours) so I can stand hard and say: it IS the hardware! You know: all so-called customer services always say: oh, when there is not Windows then it is the operating system, not the hardware... I personally think the beeps at switching on already show that there is a hardware problem, because to my knowledge in the moment that those beeps occur the computer doesn't know what system it will find later... But I might be wrong, that's why I am asking here :-) have a nice weekend! -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com