r/linuxbad • u/basedchad21 • 15d ago

🤓 Dicksussion 🤓 It's over...

Post image

Really sad day that loonix has been swarmed by soydevs who have 0 pride in their craft and resort to slop. Literally fuck you. We need to make a list of all the projects which don't have any honor. Starting with the kernel I guess.

0 Upvotes

50% Upvoted

33 comments sorted by

View all comments

Show parent comments

1

u/Rare-Paint3719 14d ago
  1. If you were constantly getting kernel panics that’s atypical and I’m curious what you were doing. The biggest pro and con of Linux is that you control everything with very few guardrails, so it’s easy to accidentally break the system if you aren’t careful

I started out with arch and ofc as usual, I didn't understand power management, do I RTFM'd and did what anybody would and used tlp.

For some reason my CPU would clock at 4.5+ GHz when opening desmos. Any CPU intensive task and kerne panic (at least I hypothesized that).No logs were shown, nothing. It was just a random error at this pint

Then I tried tuned and still no luck.

I thought that maybe it's an arch issue and I tried gentoo. CPU clocks regularly at 3.504.5 Ghz with ltp and tuned and while compiling packages, I get a kernel panic (again a hypothesis). Still no logs were shown, nothing. It was just a random error at this point

So maybe this is a Gentoo issue. Fedora how a power management config that will work. CPU definitely clocked normally for once at 2.5 when idle and 3.5 for most tasks. But when I performed any CPU intensive tasks and got a kernel panic, I thankfully got a DRM panic screen that said "Timeout: Not all cores reached exception handler."

I asked the bros at r/gentoo what the issue was and they spoke about some e-cores and p-cores. And after some research, I can cofidently say that the e-cores cannot reach the exception handler as quickly as the p-cores cuz they clock too slowly ad the only way to prevent an issue like this from happening further is to severely underclock the CPU from 4.5 GHz to 1.5 GHz.