From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: amdgpu system freeze
Date: Thu, 02 Jan 2025 17:31:53 +0100 [thread overview]
Message-ID: <20250102163153.1ABA223340@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53787@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2578 bytes --]
New comment by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/issues/53787#issuecomment-2568046151
Comment:
> i too am suffering from this bug. currently running XFCE on X11, i also ran kde plasma X11 some time ago, which also crashed just the same way. weirdly enough, it might just be luck, but kde plasma wayland never crashed on me.
>
> my system specs are and nvidia GTX 1650 GPU, and that the crash can happen randomly. i can sometimes do video intensive tasks for hours without a single hiccup, but sometimes i can crash 10 minutes after booting up while using my browser.
>
> as a last note, the dmesg logs have some errors when the system "freezes" (i can still ssh my way in with my phone). they usually are prety quiet up until something like this happens:
>
> ```
> [ 422.608105] amdgpu 0000:08:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6
> [ 422.876854] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:73:crtc-0] hw_done or flip_done timed out
> [ 433.117233] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:77:crtc-1] hw_done or flip_done timed out
> [ 434.689642] amdgpu 0000:08:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
> [ 454.621453] amdgpu 0000:08:00.0: amdgpu: Dumping IP State
> ```
>
> followed by the watchdog freaking out at the CPU threads getting stuck until i reisub.
Back when these errors started cropping up, it was speculated that some out-of-sync interactions between `AMDGPU`, `amd-firmware`, and the GPU's clock state were resulting in freezes. But you managed to get those with a CPU-integrated GPU, which is interesting to say the least.
In your case, you may just want to disable your CPU-embedded GPU in BIOS/UEFI, and be stuck with then Nvidia discrete adapter, although its support for wayland is not there, basically, and it's driver support is in a state of flux since they're open-sourcing their driver, but support is still early.
@narodnik Try and see also if you can get some `dmesg` logs just like CaioFrancisco did.
Also ensure you have setup a `syslog` config, and see if anything comes up there: https://docs.voidlinux.org/config/services/logging.html?highlight=log#logging (Less likely, but you never know what weird cascade effects may crop up)
I know `dmesg` can be a pain to read into, but something like the log above hints at some driver problem into `AMDGPU`, which really should be brought up to their engineers. It's not the first time something like this comes up.
Both of you may have found some deep-seated bug.
next prev parent reply other threads:[~2025-01-02 16:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 14:42 [ISSUE] " narodnik
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 [this message]
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
2025-01-22 12:22 ` Laitinlok
2025-01-22 16:01 ` CaioFrancisco
2025-01-22 17:15 ` CaioFrancisco
2025-01-22 19:07 ` CaioFrancisco
2025-01-22 23:44 ` ACR-Jeff
2025-01-22 23:51 ` Laitinlok
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=20250102163153.1ABA223340@inbox.vuxu.org \
--to=teuslollo@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).