Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com Control: severity -1 critical
Now that I have your attention, because raising the severity is the only way to get an answer here, let me begin. I noticed that this mess of a kernel reached testing today. As it seems, its original severity status was not enough to prevent this from happening. A kernel that causes hardware failure will soon be in debian's stable release, who would have thought! So, right now I am forced to use an older kernel, thus miss all the security updates from .28 on. And all that because I want my pc to work as it is supposed to work. Because I want to press the power button in the morning and see my pc boot the way it has been booting all those years that it had no issues at all. I would do more testing with liquirix's or xanmod's kernels of the same version in order to prove that your kernel is problematic, but I have ran out of gpus. Thank you for your non existant support. It was also non existant in a another kernel related bug report for 4.19 (bug 919859), which I opened in late 2019. It was closed a few days for lack of activity and it was a monologue with only me reporting stuff and getting no feedback. To be honest, if I knew they would become a monologue, I would not file bug reports but I would open a blog instead. And who knows, maybe someone would share his feedback there. p.s. The only reason I am not in arch today, as I promised last week, is because its installer has some minor issues. In the long term, my decision is to remove debian from any of my machines, including an rpi4 with raspbian.
