This is a fresh installation (brought to me by a flaky PDU that caused the upgrade from 12.1 to 12.2 to become useless).
The boot up freezes fairly reliably right after the CPU microcode upgrade (see messages listing below). The listing is from a successful boot; the success seems to be when there is a break in the stream of microcode updates. If the logging shows all updates contiguously, the “Microcode Update Driver” line is the last one output before the system freezes.
Any suggestions about what to prevent the freezing?
Oct 28 19:47:08 linux kernel: 4.342778] device fsid 0617578a-edca-4e3b-9100-729ae05c9057 devid 1 transid 57 /dev/sdc7
Oct 28 19:47:08 linux kernel: 4.343493] btrfs: disk space caching is enabled
Oct 28 19:47:08 linux kernel: 7.348880] microcode: CPU0: patch_level=0x00000000
Oct 28 19:47:08 linux kernel: 8.280828] btrfs: disk space caching is enabled
Oct 28 19:47:08 linux kernel: 8.330539] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 28 19:47:08 linux kernel: 8.330541] EDD information not available.
Oct 28 19:47:08 linux kernel: 8.959184] microcode: CPU0: new patch_level=0x010000c8
Oct 28 19:47:08 linux kernel: 8.959198] microcode: CPU1: patch_level=0x00000000
Oct 28 19:47:08 linux kernel: 8.959764] microcode: CPU1: new patch_level=0x010000c8
Oct 28 19:47:08 linux kernel: 8.959776] microcode: CPU2: patch_level=0x00000000
Oct 28 19:47:08 linux kernel: 8.960090] microcode: CPU2: new patch_level=0x010000c8
Oct 28 19:47:08 linux kernel: 8.960098] microcode: CPU3: patch_level=0x00000000
Oct 28 19:47:08 linux kernel: 8.960341] microcode: CPU3: new patch_level=0x010000c8
Oct 28 19:47:08 linux kernel: 8.960380] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
====<the freeze occurs here, when it does >====
Oct 28 19:47:08 linux kernel: 9.076327] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
Oct 28 19:47:08 linux kernel: 9.076384] ACPI: Power Button [PWRB]
Updating CPU microcode: That seems a bold move. Is there a way to prevent it? To test if indeed that is the issue?
But, what ever bugs may exist in your CPU would be left uncorrected on each reboot. The article above even talks about updating the microcode yourself. Here is the location for SAKC:
Consider that before you turn off a feature, you could just try a newer kernel. Kernel 3.6.4 is now the main stable release which you can use SAKC to compile. Once you make a change, your active kernel config would always include this change meaning you would on purpose go in and change your original change back to the way it was.
The actual problem had nothing to do with updating the microcode: It was a defective memory board. The memory was intermittently having a stuck something and it occurred about the time and memory location that the microcode was being changed.
After replacing the memory, the system boots just fine and has shown none of its previous instability (it would spontaneously reboot 1 - 2 times per week).
Well it is good to know you found the issue. Hardware can always get you when you least expect it. I do wonder if having the number 666 in your name might have anything to do with it?
I do wonder if having the number 666 in your name might have anything to do with it?
That was from creating my account. I had created an account previously but the forum manager would not acknowledge the old account except to say that it existed. It would not send any password changes or anything else, only that I could not use the old username; sort of a zombie account.
Being quite miffed by the whole “Yes, you exist. No, you don’t” bit, I created anew account with a username that represented my state of mind at the time.
So, I am a moderator and have some extra abilities now, so if you need help, just let me know. I might say that at first, I was here maybe five years ago and could not remember what name I even used and just decided to start over a couple of years ago and so its no big thing to do that. Having a 666 is kind of funny really, but if you don’t like it, you could request it be deleted and just start over before you spend much time with it. Then again, while I would not want the name dirt, it does not really matter all that much. Either you try to help others and you are polite when you ask for help, or you are not and your name does not really matter all that much. I might also add that we really want to help our users and I am sorry if you had a bad experience before. We are just volunteers here and have the same daily problems as everyone else. I can even admit to having too much to drink before where I can assure you drinking and Moderation does not always mix. So, what does this really mean? We are all here “hopefully” to help each other and to get better at using openSUSE. If I can provide assistance to you in any way, you only need to ask.
Let me say that without a doubt, the online name of please_try_again fits your online persona to a T. And while you appear to be just a common human with a strange online name, you might actually by a super smart alien octopus of some sort. I base this assumption on the fact that you often show flashes of brilliance and the fact that must have more than two hands to produce the alien like programming code that you write. Even as it works perfectly, it seems some how unearthly to me. But hey, no one has accused me of being a good judge of character before.
