When critical kernel error messages start looping on you in boot sequence
Non system disk 💿 or disk error
If you ever worked on a single tasking operating system in a closed source form you know this error
This is the type of error you get just after the post when the BIOS has been loaded
I got an interesting scare early one morning on one of my older machines, when I got a interesting set of error messages, some even looping ➿
One of those errors was DRM. After that the /dev devices could not all be loaded
Then another was a set of loops by the operating system because it could not continue, when the DRM error occurred.
There were in total 12 different error messages thrown at me after every post regardless of which kernel I grabbed to boot the system from, so something was wacky with my hardware, in these expensive RAM DDR4 DDR5 SSD M.2SSD GPU times!
Staying calm is the best you can do and of course I did that, because I was with Spock Logic, troubleshooting this error sequence
Of course I open the machine up reseated the memory modules, DDR4, reseated the internal m.2SSD to no avail...
It turns out that the kernel was getting confusing error messages from the hardware, thus it was interpreting them based upon its internal error message tables and then threw the messages in a pseudo readable human form to me.
After at one of the startup sequences it was clear,
* DRM error stolen region
* USB blah blah error
Next boot
* DRM error stolen region
* USB blah blah error
At that certain point I yanked out a USB hub on which I have several devices. The machine then finished the startup sequence!
The fix was bloody simple, remove the power supply from the USB hub of course yank out the data cable from the machine and wait for 5 seconds
#Kernel #boot #sequence #error #dev #programming #Linux #POST #USB #power #hardware


🇩🇪


