Github messages for voidlinux
 help / color / mirror / Atom feed
From: CaioFrancisco <CaioFrancisco@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: amdgpu system freeze
Date: Thu, 02 Jan 2025 02:16:59 +0100	[thread overview]
Message-ID: <20250102011659.3F0FE2CC71@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: 1371 bytes --]

New comment by CaioFrancisco on void-packages repository

https://github.com/void-linux/void-packages/issues/53787#issuecomment-2567210373

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 ryzen 5 2400g 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.

  parent reply	other threads:[~2025-01-02  1:16 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 [this message]
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
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=20250102011659.3F0FE2CC71@inbox.vuxu.org \
    --to=caiofrancisco@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).