ZenStates-Linux
systemd
ZenStates-Linux | systemd | |
---|---|---|
14 | 517 | |
488 | 12,516 | |
- | 1.6% | |
0.0 | 10.0 | |
almost 4 years ago | 1 day ago | |
Python | C | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ZenStates-Linux
-
[HELP] GMK K4 Random Reboot (Ubuntu)
You can also use: https://github.com/r4m0n/ZenStates-Linux/tree/master
-
EPYC 7002 CPUs may hang after 1042 days of uptime
https://github.com/r4m0n/ZenStates-Linux/blob/master/zenstat...
Not sure if this is applicable to EPYC CPUs, probably not. But I would expect that it's possible to disable C6 in some similar way on EPYC CPUs without rebooting the system. (If you are actually at risk of running into this issue, you likely don't want to reboot the system…)
-
Well, it's finally happened to me. Windows update has overwritten my Linux UEFI entry, and now I get to fix it!
I tried everything you've mentioned but finally fixed the issue on my 1300 using python zenstates. I had it run on boot with this systemd service: ``` [Unit] Description=Disable C6 state on ryzen processor to fix idle freezing
-
an AMD Ryzen 5700G system keeps freezing around every other day — disabling 'C-state control' option in BIOS hasn't resolved the issue, 'typical current idle' isn't available
The freezing has only occurred when idle so far: when the monitor returns from sleep, no signal is returned. A related bug report references this Python script several times in the comments, and there's also another for Go. No commits in several years, sudo is obviously required and I don't know if they can be considered as safe.
-
System freezes every other day.
Note: I merely added the systemd script (IIRC by reusing some forum messages while digging my crashes) + the debian packaging. That's not my script :), credit for this script goes to https://github.com/r4m0n/ZenStates-Linux
-
Debian 11 constant freezing after UEFI install
I fixed this by toggling some power management option (can't remember which one, deep in a submenu) in UEFI, then checking with https://github.com/r4m0n/ZenStates-Linux. It must return C6 disabled for package, enabled for cores. Ryzen 5 1600
-
For people running 5900X/5950X on Linux, increase your SOC voltage by 0.05 if your system is crashing
Also try disabling C6 sleep with zenstates
-
AMD CPU undervolt finally possible with this new P State driver ?
You can undervolt by manipulating the VIDs with zenstates https://github.com/r4m0n/ZenStates-Linux
-
not even sure what i did this time(information in comments)
It's the Ryzen bug. You need to disable your C6 cpu state (https://github.com/r4m0n/ZenStates-Linux), disable dram power down enable(bios option) and set Power Supply Idle Control to Typical Current Idle(bios option)
-
AMD Ryzen Sleep, Hibernate and Shutdown Issues
So the other hand is zenstates.py It pokes a register to keep C6 power state from happening. I launch on reboot, and my machine no longer has sleep state problems.
systemd
-
Run0 – systemd based alternative to sudo announced
> 3. even `adduser` will not allow it by default
5. useradd does allow it (as noted in a comment). 6. Local users are not the only source, there things like LDAP and AD.
7. POSIX allows it:
* https://github.com/systemd/systemd/issues/6237#issuecomment-...
-
Systemd Rolling Out "run0" As sudo Alternative
> I for one love to type out 13 extra characters
FWIW, systemd is normally pretty good at providing autocomplete suggestions, so even if you don't want to set up an alias you'll probably just have to type `--b ` to set it.
> I wonder what random ASCII escape sequences we can send.
According to the man page source[0]:
> The color specified should be an ANSI X3.64 SGR background color, i.e. strings such as `40`, `41`, …, `47`, `48;2;…`, `48;5;…`
and a link to the relevant Wikipedia page[1]. Given systemd's generally decent track record wrt defects and security issues, and the simplicity of valid colour values, I expect there's a fairly robust parameter verifier in there.
In fact, given the focus on starting the elevated command in a highly controlled environment, I'd expect the colour codes to be output to the originating terminal, not forwarded to the secure pty. That way, the only thing malformed escapes can affect is your own process, which you already have full control over anyway.
(Happy to be shown if that's a mistaken expectation though.)
[0] https://github.com/systemd/systemd/blob/main/man/run0.xml
[1] https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_G...
- Crash-only software: More than meets the eye
-
Systemd Wants to Expand to Include a Sudo Replacement
bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completio...
-
"Run0" as a Sudo Replacement
the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237
PS: https://pwnies.com/systemd-bugs/
-
Linux fu: getting started with systemd
https://github.com/systemd/systemd/issues/32028#issuecomment...
There are some very compelling arguments made there if you care to read them
-
Ubuntu 24.04 (and Debian) removed libsystemd from SSH server dependencies
Maybe it was because you weren't pointing out anything new?
There was a pull request to stop linking libzma to systemd before the attack even took place
https://github.com/systemd/systemd/pull/31550
This was likely one of many things that pushed the attackers to work faster, and forced them into making mistakes.
-
Systemd minimizing required dependencies for libsystemd
The PR for changing compression libraries to use dlopen() was opened several weeks before the xz-utils backdoor was revealed.
https://github.com/systemd/systemd/pull/31550
- Going in circles without a real-time clock
-
The xz sshd backdoor rabbithole goes quite a bit deeper
I find this the most plausible explanation by far:
* The highly professional outfit simply did not see teknoraver's commit to remove liblzma as standard dependency of systemd build scripts coming.
* The race was on between their compromised code and that commit. They had to win it, with as large a window as possible.
* This caused serious errors.
* The performance regression is __not__ big. It's lucky Andres caught it at all. It's also not necessarily all that simple to remove it. It's not simply a bug in a loop or some such.
* The payload of the 'hack' contains fairly easy ways for the xz hackers to update the payload. They actually used it to remove a real issue where their hackery causes issues with valgrind that might lead to discovering it, and they also used it to release 5.6.1 which rewrites significant chunks; I've as yet not read, nor know of any analysis, as to why they changed so much.
Extra info for those who don't know:
https://github.com/systemd/systemd/commit/3fc72d54132151c131...
That's a commit that changes how liblzma is a dependency of systemd. Not because the author of this commit knew anything was wrong with it. But, pretty much entirely by accident (although removing deps was part of the point of that commit), almost entirely eliminates the value of all those 2 years of hard work.
And that was with the finish line in sight for the xz hackers: On 24 feb 2024, the xz hackers release liblzma 5.6.0 which is the first fully operational compromised version. __12 days later systemd merges a commit that means it won't work__.
So now the race is on. Can they get 5.6.0 integrated into stable releases of major OSes _before_ teknoraver's commit that removes liblzma's status as direct dep of systemd?
I find it plausible that they knew about teknoraver's commit _just before_ Feb 24th 2024 (when liblzma v5.6.0 was released, the first backdoored release), and rushed to release ASAP, before doing the testing you describe. Buoyed by their efforts to add ways to update the payload which they indeed used - March 8th (after teknoraver's commit was accepted) it was used to fix the valgrind issue.
So, no, I don't find this weird, and I don't think the amateurish aspects should be taken as some sort of indication that parts of the outfit were amateuristic. As long as it's plausible that the amateuristic aspects were simply due to time pressure, it sounds like a really bad idea to make assumptions in this regard.
What are some alternatives?
undervolt - Undervolt Intel CPUs under Linux
openrc - The OpenRC init system
picom - A lightweight compositor for X11
tini - A tiny but valid `init` for containers
le9-patch - [PATCH] mm: Protect the working set under memory pressure to prevent thrashing, avoid high latency and prevent livelock in near-OOM conditions
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.
earlyoom - earlyoom - Early OOM Daemon for Linux
s6 - The s6 supervision suite.
radeon-profile - Application to read current clocks of ATi Radeon cards (xf86-video-ati, xf86-video-amdgpu)
snapdrop - A Progressive Web App for local file sharing
supervisor - Supervisor process control system for Unix (supervisord)