From: narodnik <narodnik@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] amdgpu system freeze
Date: Wed, 01 Jan 2025 15:42:08 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53787@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2162 bytes --]
New issue by narodnik on void-packages repository
https://github.com/void-linux/void-packages/issues/53787
Description:
### Is this a new report?
Yes
### System Info
Void 6.9.12_1 x86_64 AuthenticAMD notuptodate rDDF
### Package(s) Affected
linux-firmware-amd-20241210_1.x86_64
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://gitlab.freedesktop.org/drm/amd/-/issues/3863
See also: https://github.com/void-linux/void-packages/issues/53434#issuecomment-2564815160
### Expected behaviour
I'm using Wayland with a minimalistic window manager (DWL). After 30 mins usage, I get a full system freeze.
### Actual behaviour
The system fully freezes. I can still hear music playing, and I can reset using REISUB. But there is no response to input from the WM itself.
I've managed to fix it by doing these steps:
1. `xdowngrade mesa-24.2.3_2.x86_64.xbps libglapi-24.2.3_2.x86_64.xbps libOSMesa-24.2.3_2.x86_64.xbps mesa-libgallium-24.2.3_2.x86_64.xbps libgbm-24.2.3_2.x86_64.xbps libgbm-devel-24.2.3_2.x86_64.xbps MesaLib-devel-24.2.3_2.x86_64.xbps`
2. `xdowngrade linux-firmware-amd-20241110_1.x86_64.xbps`
3. Using Linux 6.9
4. Making a completely new user.
The last step is very unusual and makes me think it's due to a stale mesa cache somewhere. I tried clearing out my normal user's home directory, and logging on as that user. But I still get the crash.
However with a completely new user, the system is completely stable. This is the configuration I've been using so far. When installing linux6.9, I got these messages:
```
File descriptor 21 (/home/myuser/.cache/mesa_shader_cache_db/part0/mesa_cache.db) leaked on lvs invocation. Parent PID 76833: /bin/sh
```
Which made me think it's that cache. So I removed `~/.cache/` completely but it didn't fix the issue. Only a completely new user does!
Please advise me the steps to triage this bug and help get it fixed. I have no idea if it's an issue with Linux, amdgpu or mesa.
### Steps to reproduce
Just use my computer. Strangely if I only use foot terminal, and play no videos or use the browser then it's fine.
next reply other threads:[~2025-01-01 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 14:42 narodnik [this message]
2025-01-01 22:03 ` TeusLollo
2025-01-01 22:04 ` TeusLollo
2025-01-01 22:13 ` TeusLollo
2025-01-02 1:16 ` CaioFrancisco
2025-01-02 7:47 ` narodnik
2025-01-02 16:31 ` TeusLollo
2025-01-02 16:32 ` TeusLollo
2025-01-08 18:40 ` narodnik
2025-01-08 18:40 ` [ISSUE] [CLOSED] " narodnik
2025-01-13 17:46 ` CaioFrancisco
2025-01-20 18:23 [ISSUE] " CaioFrancisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53787@inbox.vuxu.org \
--to=narodnik@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).