Dmesg's "delayed_fput hogged CPU" & "Atomic update failure on pipe A"

Hardware Support
1

Greetings!

I've been a Zorin OS user since December 2025 — so far it's been a great experience — a lot to learn and to "get up to speed", but I can finally say I feel comfortable using Linux, and I'm not looking back! Gemini has been very helpful in the learning process and also in diagnosing and fixing most of the issues that surfaced in my particular setup. BTW, I use this laptop mostly for web browsing (Brave & Firefox), studies/office (LibreOffice), FreeTube/YouTube (plays fine up to 1080p60/h264ify), music (Qmmp) and some vintage gaming (OpenTTD, SimCity 4, etc.). These tasks in Zorin OS 18 Core perform extremely well most of the time, so much so that it's not rare to forget I'm actually handling a 16-year-old machine!

Routinely, though, multiple errors appear in the "dmesg -w" report, the most common ones being as follows:

[ 513.031009] workqueue: delayed_fput hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[ 514.022020] workqueue: delayed_fput hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND
[ 515.029025] workqueue: delayed_fput hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND
[ 582.040340] workqueue: delayed_fput hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND
[ 586.028361] workqueue: delayed_fput hogged CPU for >10000us 19 times, consider switching to WQ_UNBOUND
[ 608.032472] workqueue: delayed_fput hogged CPU for >10000us 35 times, consider switching to WQ_UNBOUND
[ 625.059570] workqueue: delayed_fput hogged CPU for >10000us 67 times, consider switching to WQ_UNBOUND
[ 666.051811] workqueue: delayed_fput hogged CPU for >10000us 131 times, consider switching to WQ_UNBOUND
[ 728.036198] workqueue: delayed_fput hogged CPU for >10000us 259 times, consider switching to WQ_UNBOUND
[ 869.047150] workqueue: delayed_fput hogged CPU for >10000us 515 times, consider switching to WQ_UNBOUND
[ 1420.034410] workqueue: delayed_fput hogged CPU for >10000us 1027 times, consider switching to WQ_UNBOUND
[ 2209.035113] workqueue: delayed_fput hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND
[ 3581.071151] workqueue: delayed_fput hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND
[ 6008.799492] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=360923 end=360924) time 2253 us, min 763, max 767, scanline start 694, end 18
[ 6512.110098] workqueue: delayed_fput hogged CPU for >10000us 8195 times, consider switching to WQ_UNBOUND
[ 8437.312319] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=506620 end=506621) time 2255 us, min 763, max 767, scanline start 733, end 57
[12946.215097] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=676893 end=676894) time 2196 us, min 763, max 767, scanline start 672, end 775

--

Meanwhile, the "journalctl -p 3 -xb --no-pager" report shows the following:

journalctl -p 3 -xb --no-pager
abr 07 23:21:02 Vostro-3500 kernel: i2c i2c-0: Failed to register i2c client jc42 at 0x18 (-16)
abr 07 23:21:02 Vostro-3500 kernel: faux_driver dell-pc: platform_profile probe failed
abr 07 23:21:04 Vostro-3500 bluetoothd[743]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
abr 07 23:21:04 Vostro-3500 bluetoothd[743]: sap-server: Operation not permitted (1)
abr 07 23:21:13 Vostro-3500 bluetoothd[743]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
abr 07 23:21:13 Vostro-3500 bluetoothd[743]: sap-server: Operation not permitted (1)
abr 07 23:21:25 Vostro-3500 gdm-password][1759]: gkr-pam: unable to locate daemon control file
abr 07 23:21:26 Vostro-3500 gdm3[1007]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
abr 07 23:21:28 Vostro-3500 systemd[1782]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1965.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 215 and the job result is failed.
abr 07 23:21:28 Vostro-3500 systemd[1782]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1968.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 219 and the job result is failed.
abr 07 23:21:28 Vostro-3500 systemd[1782]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-1971.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 223 and the job result is failed.
abr 07 23:21:33 Vostro-3500 gdm3[1007]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
abr 08 01:01:03 Vostro-3500 kernel: i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=360923 end=360924) time 2253 us, min 763, max 767, scanline start 694, end 18
abr 08 01:41:32 Vostro-3500 kernel: i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=506620 end=506621) time 2255 us, min 763, max 767, scanline start 733, end 57
abr 08 02:56:40 Vostro-3500 kernel: i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=676893 end=676894) time 2196 us, min 763, max 767, scanline start 672, end 775

--

More useful information, as per usually requested:

inxi -Fz
System:
Kernel: 6.17.0-20-generic arch: x86_64 bits: 64
Desktop: GNOME v: 46.0 Distro: Zorin OS 18.1 noble
Machine:
Type: Portable System: Dell product: Vostro 3500 v: A12
serial:
Mobo: Dell model: N/A v: A12 serial: BIOS: Dell
v: A12 date: 04/08/2014
Battery:
ID-1: BAT0 charge: 77.0 Wh (100.3%) condition: 76.8/72.7 Wh (105.6%)
volts: 5.6 min: 11.2
CPU:
Info: dual core model: Intel Core i7 M 640 bits: 64 type: MT MCP cache:
L2: 512 KiB
Speed (MHz): avg: 2225 min/max: 1197/2794 cores: 1: 2540 2: 1459 3: 2448
4: 2454
Graphics:
Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel
Display: wayland server: X.Org v: 23.2.6 with: Xwayland v: 23.2.6
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: crocus gpu: i915 resolution: 1366x768~60Hz
API: EGL v: 1.5 drivers: crocus,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa
v: 25.2.8-0ubuntu0.24.04.1 renderer: Mesa Intel HD Graphics (ILK)
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio
driver: snd_hda_intel
API: ALSA v: k6.17.0-20-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active
Network:
Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k
IF: wlp18s0 state: up mac:
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp19s0 state: down mac:
Bluetooth:
Device-1: Qualcomm Atheros AR3012 Bluetooth 4.0 driver: btusb type: USB
Report: hciconfig ID: hci0 rfk-id: 2 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address:
Drives:
Local Storage: total: 476.94 GiB used: 131.87 GiB (27.7%)
ID-1: /dev/sda model: SSD 512GB size: 476.94 GiB
Partition:
ID-1: / size: 467.89 GiB used: 131.87 GiB (28.2%) fs: ext4 dev: /dev/sda3
ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2
Swap:
ID-1: swap-1 type: file size: 4.01 GiB used: 0 KiB (0.0%) file: /swapfile
ID-2: swap-2 type: zram size: 4.52 GiB used: 67.2 MiB (1.5%)
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 52.0 C mobo: 42.0 C
Fan Speeds (rpm): cpu: 0
Info:
Memory: total: 8 GiB available: 7.54 GiB used: 2.83 GiB (37.5%)
Processes: 256 Uptime: 5h 8m Shell: Bash inxi: 3.3.34

--

echo $XDG_SESSION_TYPE
wayland

Vostro-3500:~$ glxinfo | grep "OpenGL version"
ATTENTION: default value of option vblank_mode overridden by environment.
OpenGL version string: 2.1 Mesa 25.2.8-0ubuntu0.24.04.1

Vostro-3500:~$ inxi -t cm
Processes:
CPU top: 5 of 262
1: cpu: 20.4% command: firefox pid: 147128
2: cpu: 7.9% command: gnome-shell pid: 1985
3: cpu: 3.1% command: firefox-bin pid: 255944
4: cpu: 2.1% command: conky pid: 2700
5: cpu: 2.1% command: firefox-bin pid: 147384
System RAM: total: 8 GiB available: 7.54 GiB used: 3.59 GiB (47.6%)
Memory top: 5 of 262
1: mem: 726.5 MiB (9.4%) command: firefox pid: 147128
2: mem: 338.3 MiB (4.3%) command: gnome-shell pid: 1985
3: mem: 324.2 MiB (4.1%) command: firefox-bin pid: 147384
4: mem: 319.4 MiB (4.1%) command: firefox-bin pid: 259736
5: mem: 292.1 MiB (3.7%) command: firefox-bin pid: 255944

--

Gemini helped me disable the dedicated GeForce 310M once the Nouveau driver was causing instabilities. Hopefully, in the future we may have access to Linux compatible graphical drivers which may better handle legacy hardware.

Many Grub edits were made — ask if they might be helpful, and I'll share them as well.

Any help to diagnose and, especially, fixing these errors is welcomed.

Thanks in advance, best regards!

2

There might be Errors in the Logs but do You have any Issues with Your System?

1 Like
3

Hi! Yes—sometimes recoverable freezes; more rarely, events that require the "REISUB" procedure.

4

Have you tried Zorin on xorg instead of Wayland?

1 Like
5

Hi! Yes, I tried it; however, it was considerably slower compared to Wayland, so I didn't go any further with it.

6

Are these Freezes when You use a specific Program or do they happen ramdomly independent from the used Program?

7

They happen randomly and independent of any specific software.

8

Did you try it with Zorin 17/Zorin 17 Lite or an older kernel, e.g. 6.8 or 5.15? I'm surprised that your 16 years old computer runs better with Wayland than with Xorg.

9

Hi! I went straight to Zorin OS 18 Core since last December — I believe that since then there have been two or three kernel version updates.
Trying Xorg was very disappointing, since pretty much everywhere it's said that it should be optimal for older systems such as this.

10

Just now I was playing JGRPP (OpenTTD), then a screen freeze occurred when I tried to take a screenshot (I've done this before without issues) - it froze for a few seconds, then went back to the login screen as if a "soft reset" had happened.

Relevant dmesg and journalctl messages below (the latter ones may pertain to the aforementioned moment):

[ 4048.974891] i915 0000:00:02.0: [drm] GPU HANG: ecode 5:1:9ffdfeff, in Xwayland [2332]
[ 4048.974901] i915 0000:00:02.0: [drm] GPU error state saved to /sys/class/drm/card1/error
[ 4048.978394] i915 0000:00:02.0: [drm] GT0: Resetting chip for stopped heartbeat on rcs0
[ 4049.079974] i915 0000:00:02.0: [drm] Xwayland[2332] context reset due to GPU hang
[ 4340.067782] workqueue: delayed_fput hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[ 4340.079770] workqueue: delayed_fput hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND
[ 4343.083837] workqueue: delayed_fput hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND
[ 4346.116907] workqueue: delayed_fput hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND
[ 4351.058024] workqueue: delayed_fput hogged CPU for >10000us 19 times, consider switching to WQ_UNBOUND
[ 4358.061172] workqueue: delayed_fput hogged CPU for >10000us 35 times, consider switching to WQ_UNBOUND
[ 4374.064801] workqueue: delayed_fput hogged CPU for >10000us 67 times, consider switching to WQ_UNBOUND
[ 4454.074155] workqueue: delayed_fput hogged CPU for >10000us 131 times, consider switching to WQ_UNBOUND
[ 4513.090281] workqueue: delayed_fput hogged CPU for >10000us 259 times, consider switching to WQ_UNBOUND
[ 4988.095447] workqueue: delayed_fput hogged CPU for >10000us 515 times, consider switching to WQ_UNBOUND
[ 5110.427514] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=307026 end=307027) time 1788 us, min 763, max 767, scanline start 689, end 773
[ 5232.096353] workqueue: delayed_fput hogged CPU for >10000us 1027 times, consider switching to WQ_UNBOUND
[ 9579.032848] i915 0000:00:02.0: [drm] GPU HANG: ecode 5:1:86fefffc, in gnome-shell [1982]
[ 9579.033555] i915 0000:00:02.0: [drm] GT0: Resetting chip for stopped heartbeat on rcs0
[ 9579.137136] i915 0000:00:02.0: [drm] gnome-shell[1982] context reset due to GPU hang
[ 9992.026242] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=401948 end=401949) time 2388 us, min 763, max 767, scanline start 716, end 46
[10285.170222] workqueue: delayed_fput hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND
[11822.149257] workqueue: delayed_fput hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND
[12653.115382] i915 0000:00:02.0: [drm] GPU HANG: ecode 5:1:86fefffc, in gnome-shell [1982]
[12653.117653] i915 0000:00:02.0: [drm] GT0: Resetting chip for stopped heartbeat on rcs0
[12653.219644] i915 0000:00:02.0: [drm] gnome-shell[1982] context reset due to GPU hang
[12659.065743] i915 0000:00:02.0: [drm] GPU HANG: ecode 5:1:86fffffd, in gnome-shell [1982]
[12659.070470] i915 0000:00:02.0: [drm] GT0: Resetting chip for stopped heartbeat on rcs0
[12659.172687] i915 0000:00:02.0: [drm] gnome-shell[1982] context reset due to GPU hang
[12659.460318] rfkill: input handler enabled
[12662.609189] rfkill: input handler disabled
[12671.074273] rfkill: input handler enabled
[12673.338569] rfkill: input handler disabled

--

journalctl -p 3 -xb --no-pager
abr 09 01:56:42 Vostro-3500 kernel: i2c i2c-0: Failed to register i2c client jc42 at 0x18 (-16)
abr 09 01:56:42 Vostro-3500 kernel: faux_driver dell-pc: platform_profile probe failed
abr 09 01:56:45 Vostro-3500 bluetoothd[795]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
abr 09 01:56:45 Vostro-3500 bluetoothd[795]: sap-server: Operation not permitted (1)
abr 09 01:56:50 Vostro-3500 bluetoothd[795]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
abr 09 01:56:50 Vostro-3500 bluetoothd[795]: sap-server: Operation not permitted (1)
abr 09 01:57:04 Vostro-3500 gdm-password][1763]: gkr-pam: unable to locate daemon control file
abr 09 01:57:05 Vostro-3500 gdm3[1023]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
abr 09 01:57:07 Vostro-3500 systemd[1784]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1967.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 215 and the job result is failed.
abr 09 01:57:09 Vostro-3500 systemd[1784]: Failed to start app-gnome-spice\x2dvdagent-2115.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 256 and the job result is failed.
abr 09 01:57:12 Vostro-3500 gdm3[1023]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
abr 09 03:21:45 Vostro-3500 kernel: i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=307026 end=307027) time 1788 us, min 763, max 767, scanline start 689, end 773
abr 09 04:43:06 Vostro-3500 kernel: i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=401948 end=401949) time 2388 us, min 763, max 767, scanline start 716, end 46
abr 09 05:27:34 Vostro-3500 gdm3[1023]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
abr 09 05:27:34 Vostro-3500 gdm3[1023]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
abr 09 05:27:44 Vostro-3500 gdm-password][171300]: gkr-pam: unable to locate daemon control file
abr 09 05:27:45 Vostro-3500 gdm3[1023]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
abr 09 05:27:46 Vostro-3500 systemd[171364]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-171537.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 215 and the job result is failed.
abr 09 05:27:46 Vostro-3500 systemd[171364]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-171539.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 219 and the job result is failed.
abr 09 05:27:49 Vostro-3500 gdm3[1023]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

11

Can You remember when this started? Was it from the Beginning or later?

12

I had sporadic issues since the beginning, most of which were solved with Gemini's help by (for the most part) editing Grub and also disabling the discrete GeForce 310M.

13

Okay, try it with disabled Hardware Acceleration in the Browsers and check if that helps.

14

It has been done already; also, Zorin's/Gnome animations have been disabled.

15

Okay, could You post Your Hardware Specs in Detail please?

16

The "inxi -Fz" command output can be seen in the OP.

17

I am guessing at least one of these grub edits was disabling panel self refresh psr=0
But I notice that you are using Wayland and a kernel i915 error like this is much more likely to occur on Wayland. You are using Xorg by means of XWayland anyway (apparently out of necessity) - so... Have you tried switching to just Xorg (X11) to move away from Wayland causes?

18

Hi! Here is how my system's Grub cmdline line is currently:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d acpi_backlight=native usbcore.autosuspend=-1 i915.enable_psr=0 i915.enable_rc6=0 i915.enable_ips=0 i915.semaphores=1 intel_iommu=igfx_off i915.enable_fbc=0 i915.enable_ppgtt=0 mitigations=off processor.max_cstate=7 transparent_hugepage=never pcie_aspm=force split_lock_detect=off pcie_port_pm=off nouveau.modeset=0 pci=noaer log_buf_len=4M preempt=full workqueue.power_efficient=y"

Possibly Conky and/or other software I use is dependent on XWayland; I'm not sure. As I said previously, I did try Xorg but came out of it disappointed: it's proven to be much slower compared to Wayland and also caused graphical glitches such as horizontal lines and frequent stuttering.

19

oof...
That is a list.

Well:

All of these will reduce performance. ppgtt=0 especially so and is more problematic because it affects GPU memory handling.
You have disabled your CPU security:

This will cause GPU performance issues, too.

Your atomic failure can easily be caused by:

This one disables error reporting, but it does not solve any errors.

This contradicts the power settings applied elsewhere.

I cannot see any possible means of troubleshooting this with that very large pile of Grub Parameters ordering the kernel left, right and sideways.

The best starting point would be to begin with "quiet splash i915.enable_psr=0"

Leave logging enabled, do a full cycle reboot and begin fresh.

2 Likes
20

If you're the adventurous type (your grub file looks like this :wink:) and are interested in getting the Nvidia 340 legacy driver to work on Zorin 18, maybe this PPA is worth a try (because you had no good experience with nouveau):

The driver seems to work e.g. with kernel 6.8 or 6.11. There is also a solution posted for kernel 6.14 from MayorBug.

1 Like