-
-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Softlock CPU Stuck Renders My Device Unresponsive #7183
Comments
Please enable persistent system logs to check where those soft locks start: dietpi-software uninstall 103
mkdir /var/log/journal
reboot When it happens again, browse the logs from previous boot session: journalctl |
Sure, @MichaIng. Here is the log https://paste.debian.net/hidden/262b91b4/ Also included a slightly different picture in case that helps. |
@louisefindlay23 Or did the stall happen right at the time when you started that Docker container with |
@MichaIng, sure. I tried journalctl and also journalctl --list-boots but it only shows one entry even after the issue occurs again, there's no amount of detail for some strange reason. I even tried setting storage to persistent. The error doesn't occur immediately after the docker start command but some time after they start but never the same amount of the time. Sometimes it's an hour or two or sometimes several days. |
Turns out it was user error. I didn't realise I needed to use sudo. 🤦♀️ Hopefully this should help, @MichaIng |
Creating a bug report/issue
Required Information
9.6.1
echo $G_DISTRO_NAME $G_RASPBIAN
didn't output anythingLinux RegencyServer 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux
x86_64 BIOS CSM - Ryzen 7 1700 - NVIDIA RTX 3050
Additional Information (if applicable)
d6e9ed8b-db51-415f-a36b-954c614173e4
Steps to reproduce
Expected behaviour
Actual behaviour
The text was updated successfully, but these errors were encountered: