You are not logged in.

#1 2025-10-09 00:31:28

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 130
Website

journalctl flooded with not enoughmemory for command submission

I updated this night so i can install docker because my mirrors were broken and now hyprland just crashes with a grey screen and big cursor & my journal is flooded with

kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for command submission!

, I have the built in gpu in the AMD Ryzen 5800H for my iGPU and the Nvidia Geforce RTX 3050 for my dGPU, 16gb of RAM and also on eco mode in power-profiles-daemon. can anyone figure out what happened and what to do.

Last edited by Omarz2012 (2025-10-09 21:38:11)

Offline

#2 2025-10-09 00:52:59

loqs
Member
Registered: 2014-03-06
Posts: 18,630

Re: journalctl flooded with not enoughmemory for command submission

Please post the full dmesg output from a boot with the issue and also adjust the all caps part of the thread title.

Offline

#3 2025-10-09 00:57:48

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 130
Website

Re: journalctl flooded with not enoughmemory for command submission

loqs wrote:

Please post the full dmesg output from a boot with the issue and also adjust the all caps part of the thread title.

[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for command submission!

also repeated over and over again and can you pleas specify what to change about the all caps part of the title

Offline

#4 2025-10-09 01:00:46

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 130
Website

Re: journalctl flooded with not enoughmemory for command submission

found something intresting: whenever i set the power-profile-daemon to preformance, then back to the setting i want, it stops the error
Edit: now when i set it to balanced, the fix doesn't work anymore

Last edited by Omarz2012 (2025-10-09 01:15:35)

Offline

#5 2025-10-09 01:06:02

loqs
Member
Registered: 2014-03-06
Posts: 18,630

Re: journalctl flooded with not enoughmemory for command submission

https://bbs.archlinux.org/viewtopic.php?id=57855 Can you reproduce the issue if you boot with power-profile-daemon disabled?  Change the all caps to sentence case.

Offline

#6 2025-10-09 21:37:35

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 130
Website

Re: journalctl flooded with not enoughmemory for command submission

loqs wrote:

https://bbs.archlinux.org/viewtopic.php?id=57855 Can you reproduce the issue if you boot with power-profile-daemon disabled?  Change the all caps to sentence case.

After some testing, power-profiles-daemon is correlated to the problem, but too loose to have any meaning. Sometimes when I uninstalled power-profiles-daemon, the error would persist, and sometimes it would disappear. will do more research with kernel versions

Offline

#7 2025-10-09 22:15:25

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 130
Website

Re: journalctl flooded with not enoughmemory for command submission

Update: the problem definitely occured in either 6.17.1 or 6.17, hyprland crashing was due to dynamic-cursor being corrupt.
another update: this only happens on KDE plasma

Last edited by Omarz2012 (2025-10-10 01:48:03)

Offline

#8 2025-10-10 08:00:41

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,138

Re: journalctl flooded with not enoughmemory for command submission

"Uninstalling" foobar-daemon will not stop foobar-daemon before the next reboot.
Is the LTS kernel affected?
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

also

pacman -Qs vulkan

Either you're legitimately flooding the GPU (do you have to run some specific GPU-heavy task to trigger this? Game? The more fringe/uncommon the more likely) or this is a follow-up issue (firmware crash, GPU dropped off the bus/fails to reset/… maybe because of a hybrid setup)

Offline

#9 2025-10-14 00:28:57

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 130
Website

Re: journalctl flooded with not enoughmemory for command submission

seth wrote:

"Uninstalling" foobar-daemon will not stop foobar-daemon before the next reboot.
Is the LTS kernel affected?
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

also

pacman -Qs vulkan

Either you're legitimately flooding the GPU (do you have to run some specific GPU-heavy task to trigger this? Game? The more fringe/uncommon the more likely) or this is a follow-up issue (firmware crash, GPU dropped off the bus/fails to reset/… maybe because of a hybrid setup)

https://0x0.st/KSmO.txt
LTS kernel working a-ok. i made sure to restart after each time i tinkered with power-profiles-daemon's installation
the second command outputed

local/amdvlk 2025.Q2.1-1
    AMD's standalone Vulkan driver
local/lib32-amdvlk 2025.Q2.1-1
    AMD's standalone Vulkan driver
local/lib32-nvidia-utils 580.95.05-1
    NVIDIA drivers utilities (32-bit)
local/lib32-vkd3d 1.17-1
    Direct3D 12 to Vulkan translation library By WineHQ
local/lib32-vulkan-icd-loader 1.4.328.1-1
    Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/nvidia-utils 580.95.05-1
    NVIDIA drivers utilities
local/qt6-shadertools 6.10.0-1 (qt6)
    Provides functionality for the shader pipeline that allows Qt Quick to operate on Vulkan, Metal, and Direct3D, in addition to OpenGL
local/spirv-tools 1:1.4.328.1-1 (vulkan-devel)
    API and commands for processing SPIR-V modules
local/vkd3d 1.17-2
    Direct3D 12 to Vulkan translation library By WineHQ
local/vkd3d-proton-bin 2.14.1-1
    Direct3D 12 to Vulkan translation library (Windows DLL binary files)
local/vulkan-headers 1:1.4.328.1-1 (vulkan-devel)
    Vulkan header files and API registry
local/vulkan-icd-loader 1.4.328.1-1 (vulkan-devel)
    Vulkan Installable Client Driver (ICD) Loader
local/vulkan-tools 1.4.328.1-1 (vulkan-devel)
    Vulkan tools and utilities

also it stopped when vesktop automatically launched with this coming up after it stopped (ran journalctl with -r)

Oct 13 20:24:59 archernitro5 systemd[1256]: app-org.kde.dolphin@6441a6e7da264c83a2d3c99a4ebcda59.service: Consumed 1.206s CPU time, 125.6M memory peak.
Oct 13 20:24:56 archernitro5 wireplumber[1430]: wp-event-dispatcher: <WpAsyncEventHook:0x5617d2063da0> failed: <WpSiStandardLink:0x5617d22cf990> link failed: 1 of 1 PipeWire links failed to activate
Oct 13 20:24:56 archernitro5 iwd[657]: invalid HE capabilities for d6:94:35:af:52:b8
Oct 13 20:24:56 archernitro5 iwd[657]: invalid HE capabilities for da:94:35:7b:16:20
Oct 13 20:24:56 archernitro5 iwd[657]: invalid HE capabilities for c6:94:35:7b:16:20
Oct 13 20:24:51 archernitro5 iwd[657]: event: roam-scan,
Oct 13 20:24:51 archernitro5 iwd[657]: event: roam-scan,
Oct 13 20:23:38 archernitro5 org.gnome.DejaDup[10130]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
Oct 13 20:23:38 archernitro5 /usr/lib/xdg-desktop-portal[1344]: Failed to close session implementation: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path '/org/freedesktop/portal/desktop/session/1_103/gtk5415164>
Oct 13 20:23:38 archernitro5 /usr/lib/xdg-desktop-portal[1344]: A backend call failed: No such method 'CreateMonitor' in interface 'org.freedesktop.impl.portal.Inhibit' at object path '/org/freedesktop/portal/desktop' (signature 'ooss')
Oct 13 20:23:37 archernitro5 systemd[1256]: Started dbus-:1.2-org.gnome.DejaDup@0.service.
Oct 13 20:23:37 archernitro5 systemd[1256]: Created slice Slice /app/dbus-:1.2-org.gnome.DejaDup.
Oct 13 20:23:21 archernitro5 electron[2550]: [2550:1013/202321.187953:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
Oct 13 20:23:21 archernitro5 electron[2550]: [2550:1013/202321.118356:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
Oct 13 20:23:21 archernitro5 electron[2550]: [2550:1013/202321.118073:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
Oct 13 20:23:11 archernitro5 electron[2550]: [2550:1013/202311.381731:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
Oct 13 20:23:10 archernitro5 electron[2488]: [2488:1013/202310.265252:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
Oct 13 20:23:10 archernitro5 electron[1922]: [1922:1013/202310.040689:ERROR:gpu_process_host.cc(981)] GPU process exited unexpectedly: exit_code=512
Oct 13 20:23:10 archernitro5 electron[2488]: [2488:1013/202310.032082:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
Oct 13 20:23:10 archernitro5 electron[2550]: [2550:1013/202310.032073:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

Offline

#10 2025-10-14 03:17:53

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 130
Website

Re: journalctl flooded with not enoughmemory for command submission

for the meanwhile. disabling vesktop autostartup fixes the problem although i will keep this open till the vencord team is able to fix this memory leak i think?

Offline

#11 2025-10-14 03:24:35

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 130
Website

Re: journalctl flooded with not enoughmemory for command submission

is there a way to make kde plasma use the dgpu like hyprland?

Offline

#12 2025-10-14 07:07:31

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,138

Offline

Board footer

Powered by FluxBB