Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I had this problem with a 1st-gen Ryzen system where the CPU would lock up when it was idle. It turned out to be a bug in the handling of P-states (CPU power states) and the solution was to disable a certain P-state in the BIOS (I forget which).
Later on there was a BIOS update for the motherboard which added a separate option that fixed this issue without having to disable the low power P-states.
These kind of issues can be a real pain to diagnose and your best bet is to search for other people who have had the same problem with the same hardware. There is no way I would have figured out the cause on my own without finding posts elsewhere on the internet about the same issue. Installing any available BIOS updates may be the answer if it's a known hardware issue.
Yes I think its power related due to the loose and/or possibly damaged USB c ports which are part of the motherboard of course... No cheap fix there. This laptop has been on a slow decline. If I just reinstalled Debian or any other distro, would it fix the issue or is it more likely a system issue that will follow me regardless?
Exactly the reason I think my next laptop is going to be one where repairability is a primary feature.
Right in the middle of a freeze right now, but the cursor still moves and the sound went muted. I'm pretty sure I saw errors before regarding pipe wire, pulseaudio, and I think another related program
Try booting from the live iso with a USB drive
And then what?
See if you can replicate the problem. You're trying to see if it's specific to your OS install, or if it's something more ingrained.
Ahh I gotcha. Its most likely caused by me, NGL. I've been trying to experiment and explore a bit with computing and networking and the likes, so I probably have something conflicting or broken. I mean I've seen plenty of errors using journalctl right after a hard reset so that I could go backward from there, but none of it makes sense. Do you know anything about log analyzers? But then again analyzers can overcomplicate things too ala netdata lol I set that up and holy god I didn't know what I was looking at lol I also have suspicion that mullvad might be playing a role in this. But again its difficult for me to put pieces together with limited knowledge about logs
So you can't switch to TTY with ctrl + alt + f1 (or f2, f3, f4) ?
You could try booting from live usb and check previous dmesg logs (/var/log/dmesg.0 or something, I think)
You could try to narrow the issue by trying to plug in other keyboard or mouse and check if that works.
If not, then probably not a touchpad/keyboard driver issue.
Are the crashes random? Could it be the system crashes when it's going to sleep/wake up after the system is idle?
I'll try to think something else when my hangover passes... :D
Uhmm for the most part its random. It was much less frequent the other day but not it's happening more and more. And yup, tried all the CTL alt f1-all of them lol like I'm aware logs will probably give the best insight but I don't know much about which log and what it all means plus they're long as fuck. Maybe I should look into log analyzers?
The dmesg logs show boot logs also from previous boots. It has timestamps. After a system freeze, try to reboot and issue sudo dmesg -T and look for the timestamp near the time of crash, is there anything suspicious?
Just throwing another suggestion to look for, maybe check your RAM usage? When I was first trying Linux i was using a persistent live iso, and it would randomly lock up like you describe. Just about the only functionality I had was to REISUB lol. It turned out my OOM services weren't closing programs until it was too late ... or maybe it was trying to put memory into swap space that didn't exist. Who knows. Try opening firefox a bunch of times and maybe see what happens
This type of thing shouldn't happen with a normal setup though.
I hope you can figure it out :)
Thanks a lot. I have a few assumptions just based off what little I could interpret from the logs.... When I check htop for CPU and ram usage, nothing really stands out as abnormal. Of course whichever browser I'm using is always the most ram hungry program. Now if I just did a reinstall of Debian 12, should that hypothetically fix the issue if it is an OS problem (which I believe it may be)?