Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Video] amdgpu: amdgpu_cs_query_fence_status failed.

New to Debian (Or Linux in general)? Ask your questions here!
Post Reply
Message
Author
bigBuggsTV
Posts: 5
Joined: 2024-04-24 08:37

[Video] amdgpu: amdgpu_cs_query_fence_status failed.

#1 Post by bigBuggsTV »

Hi, I am quite new to Debian.
Lately I have been noticing some freezes with my amd graphics card.
This happens randomly and without any pattern that I figured out so far.

First all screens go blank for a second, then all screens show the same content (even though they are not supposed to) and interaction with any input device is no longer possible.

As far as I have understood from "journalctl" this seems to be a problem with my amd graphics card, but I have no Idea on how to fix this.

Thank you very much for any help or advice.

Here is the output of "journalctl":

Code: Select all

Apr 24 09:21:33 bigBug gnome-keyring-d[1767]: asked to register item /org/freedesktop/secrets/collection/login/17, but it's already registered
Apr 24 10:13:52 bigBug gsd-media-keys[2286]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Apr 24 10:16:16 bigBug gnome-shell[1895]: amdgpu: amdgpu_cs_query_fence_status failed.
Apr 24 10:16:16 bigBug gnome-shell[2886]: amdgpu: The CS has been rejected (-125), but the context isn't robust.
Apr 24 10:16:16 bigBug gnome-shell[2886]: amdgpu: The process will be terminated.
Apr 24 10:16:16 bigBug gnome-shell[1895]: amdgpu: The CS has been rejected (-125), but the context isn't robust.
Apr 24 10:16:16 bigBug gnome-shell[1895]: amdgpu: The process will be terminated.
Apr 24 10:16:16 bigBug firefox-esr.desktop[782463]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[782467]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[673500]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[769855]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[782574]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[774571]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[770510]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[144731]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[103993]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[164433]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[672385]: Exiting due to channel error.
Apr 24 10:16:16 bigBug firefox-esr.desktop[771570]: Exiting due to channel error.
Apr 24 10:16:21 bigBug gnome-calendar[146940]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug gsd-media-keys[2286]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug evolution-alarm[2296]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug xdg-desktop-por[2561]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug xdg-desktop-por[2486]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug gsd-power[2289]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug gsd-color[2276]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug gsd-keyboard[2283]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug gsd-wacom[2315]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug gnome-terminal-[3273]: Error reading events from display: Broken pipe
Apr 24 10:16:21 bigBug systemd[1731]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 10:16:25 bigBug systemd[1731]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 10:16:25 bigBug systemd[1731]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'.
Apr 24 10:16:25 bigBug systemd[1731]: xdg-desktop-portal-gnome.service: Consumed 2.740s CPU time.
Apr 24 10:16:25 bigBug systemd[1731]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 10:16:25 bigBug systemd[1731]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Apr 24 10:16:25 bigBug systemd[1731]: xdg-desktop-portal-gtk.service: Consumed 1.850s CPU time.
Apr 24 10:16:25 bigBug systemd[1731]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 10:16:25 bigBug systemd[1731]: gnome-terminal-server.service: Failed with result 'exit-code'.
Apr 24 10:16:25 bigBug systemd[1731]: gnome-terminal-server.service: Consumed 1min 45.487s CPU time.
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Color.service: Failed with result 'exit-code'.
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Color.service: Consumed 19.319s CPU time.
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'.
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'.
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.MediaKeys.service: Consumed 2.231s CPU time.
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'.
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Power.service: Consumed 1.258s CPU time.
Apr 24 10:16:25 bigBug systemd[1731]: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'exit-code'.
Apr 24 10:16:25 bigBug systemd[1731]: vte-spawn-eee8903f-abbf-4a95-ba97-db25b3444dd1.scope: Consumed 44.725s CPU time.
Apr 24 10:16:25 bigBug systemd[1731]: app-gnome-org.gnome.Evolution\x2dalarm\x2dnotify-2296.scope: Consumed 1.974s CPU time.
Apr 24 10:16:25 bigBug systemd[1731]: app-gnome-org.gnome.Software-2299.scope: Consumed 47.399s CPU time.

mrmazda
Posts: 354
Joined: 2023-06-02 02:22
Has thanked: 11 times
Been thanked: 45 times

Re: [Video] amdgpu: amdgpu_cs_query_fence_status failed.

#2 Post by mrmazda »

Try changing login type. You should have a choice between Wayland and X11 somewhere on your login screen. You may have other choices as well. Others can be added if desired and available freespace on / filesystem exists, such as Cinnamon, KDE/Plasma, Mate &/or XFCE. If you have been using autologin, you'll need to disable it to enable this switching. Can you reproduce with all, or only with whichever you have been using?

bigBuggsTV
Posts: 5
Joined: 2024-04-24 08:37

Re: [Video] amdgpu: amdgpu_cs_query_fence_status failed.

#3 Post by bigBuggsTV »

Hi, I checked and I only have an option for GNOME/GNOME Classic wayland/X11. Currently I am running GNOME on wayland.
The problem occurs so sporadically that its hard to reproduce but often enough that it becomes annoying while working.
I found a maybe related post on arch forums: https://bbs.archlinux.org/viewtopic.php?id=281049

mrmazda
Posts: 354
Joined: 2023-06-02 02:22
Has thanked: 11 times
Been thanked: 45 times

Re: [Video] amdgpu: amdgpu_cs_query_fence_status failed.

#4 Post by mrmazda »

bigBuggsTV wrote: 2024-04-25 09:03I only have an option for GNOME/GNOME Classic wayland/X11.
I don't know how many choices that represents. Since you are using a Wayland selection, try any X11 selection.

bigBuggsTV
Posts: 5
Joined: 2024-04-24 08:37

Re: [Video] amdgpu: amdgpu_cs_query_fence_status failed.

#5 Post by bigBuggsTV »

My bad, that would be 4 selections.
- GNOME (wayland)
- GNOME Classic (wayland)
- GNOME X11
- GNOME Classic X11

Do you reckon that this is an issue with wayland? I would honestly prefer using wayland over X11 if possible.
I thought this might be a driver issue?

mrmazda
Posts: 354
Joined: 2023-06-02 02:22
Has thanked: 11 times
Been thanked: 45 times

Re: [Video] amdgpu: amdgpu_cs_query_fence_status failed.

#6 Post by mrmazda »

bigBuggsTV wrote: 2024-04-25 14:43Do you reckon that this is an issue with wayland?
How would you know if you don't try? Is it just a test, or a fix? Either way, it's not meant as permanent.

bigBuggsTV
Posts: 5
Joined: 2024-04-24 08:37

Re: [Video] amdgpu: amdgpu_cs_query_fence_status failed.

#7 Post by bigBuggsTV »

You are right, Ill try today and let you know

bigBuggsTV
Posts: 5
Joined: 2024-04-24 08:37

Re: [Video] amdgpu: amdgpu_cs_query_fence_status failed.

#8 Post by bigBuggsTV »

Ok, so far no more crashes. Thanks :D

But, I would really like to keep using wayland if possible. So if you have any idea on how to fix this error please let me know.

Post Reply