This post is to show how to "fix" almost the problem of startups with errors Arch Linux. Something like the following image:
As can be seen, we see that this is one of the many "combinations" of errors that appear randomly when starting an operating system with this problem. As it says in that error, it indicates that there may be a problem in the "Hardware", however, as we all know in this operating system, even the bad tricks of what does not belong to the OS can be solved.
So, I am going to describe my experience of this problem. From what I was able to experience, the problem was only with Arch Linux or another distro that I tested externally, since with any ubuntu that I had installed or tested, it started without problems. But if he tried to rip the Arch Linux installed on the hard drive, I had a problem that I had to reboot about 50 times in order for the OS to boot normally and use it.
This already had something wrong with me because I could only use the ubuntu that I had installed to test it and I could not do even half of the things I could do with Arch Linux. So I decided to solve this problem and began to investigate, looking for forum threads that had the same problem, they also mentioned that it was a hardware error and that it was precisely the CPU, so it began to worry me, so I got to open the PC and verify what was happening, however, it did not help.
But something that showed me, that I should not give up was that if Ubuntu I could because Arch Linux no (perhaps Ubuntu is better than Arch…?). So I started writing boot parameters to the kernel of Arch Linux, things like: lapic, nomce, intel_idle.max_cstate = 0, disable_cpu_apic, acpi_skip_timer_override, acpi = stric, clk, apm, noapic, acpi = oldboot, acpi-cpufreq, intel_pstate = disable, i8042.noacpi = 1, apm = copyds, acdtpi = 0, apm = copyds, acdtpi = XNUMX, apm = copyds pci = nocrs, rhgb, acpi = force, pnpacpi = XNUMXff and others more ... All this was recommended in the forums that I read.
Until I had to enter the documentation of the kernel parameters, which I recommend by the way: https://www.kernel.org/doc/Documentation/kernel-parameters.txt
And I found a quite interesting parameter that for the moment I managed to boot Arch Linux No problem:
linux /boot/vmlinuz-linux root=UUID=fbefe36c-1712-4f3b-b3e3-3eac759d71c9 notsc nomce maxcpus = 0
As indicated there, what this parameter does is limit the use to a cpu without activating the symmetric mode of processing. At first it worked quite well until when I used the command pacman-Syyu; threw me a core dumped o segmentation fault.
So I automatically noticed that something strange was happening, so I started running other processes until suddenly the system completely froze and didn't work anymore, until I rebooted it. So I did the same operation, but this time I managed to execute htop and it showed me the following:
As expected, it only showed one CPU, since the other had disabled it, however, it seemed very strange to me why the programs threw segfault, and couldn't even start the graphical environment; so it was something that at least gave me more hope that if I set the kernel parameters one way it would boot my Arch Linux as usual.
So I kept trying the other parameters that I wrote in the list until I came across this one, which is the best solution at the moment:
linux /boot/vmlinuz-linux root=UUID=fbefe36c-1712-4f3b-b3e3-3eac759d71c9 notsc nomce isolcpus = 1
This parameter does something as simple as isolating (not deactivating) the second core from the CPU in symmetric processing, that is, the processing load is given to a single core while the other is only complementary. This, although it seems contradictory, does not affect performance so much, since this great OS was able to run applications in this way:
So with this, the only problem that I observed that occurs at boot time, is one or two kernel panics or oops; but compared to the 50 times I had to reboot previously, I can consider it a "workaround". For the rest, so far it has allowed me to use the OS and write this post that you are reading right now :-).
I hope they help you, and do not get out of GNU / Linux, which is the best operating system they have ever invented. I say it for sure.