OS slowed to a crawl

Ask Fedora
, , , ,
1

Just had something really weird happen - after opening a Facebook URI in firefox-135.0.1-1.fc41.x86_64, my whole OS slowed to ≈ 3 frames per 15s:

It was to the extent that I couldn’t even invoke my terminal to shutdown the system (and the embedded one in the instance of Dolphin I already had running didn’t want to execute anything). I have an example of one of the two errors that appeared whenever I attempted to below:

image
image1920×1440 253 KB

However, both are depicted in the video too.

I see the undermentioned in journalctl:

  1. #!/usr/bin/env pwsh
journalctl -b -1 <# 263543c2429e45b3aaee5d959264b46b #> -p 1

  2. Feb 26 21:49:55 SNRW3Q kernel: BUG: Bad page state in process fuse mainloop  pfn:45770b
Feb 26 22:56:18 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [kcompactd0:96]
Feb 26 22:56:46 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 52s! [kcompactd0:96]
Feb 26 22:57:38 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 101s! [kcompactd0:96]
Feb 26 22:58:06 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 127s! [kcompactd0:96]
Feb 26 22:58:34 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 153s! [kcompactd0:96]
Feb 26 22:59:02 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 179s! [kcompactd0:96]
Feb 26 22:59:30 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 205s! [kcompactd0:96]
Feb 26 23:00:42 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 272s! [kcompactd0:96]
Feb 26 23:01:10 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 298s! [kcompactd0:96]
Feb 26 23:01:38 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 324s! [kcompactd0:96]
Feb 26 23:02:06 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 350s! [kcompactd0:96]
Feb 26 23:02:34 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 376s! [kcompactd0:96]
Feb 26 23:03:42 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 440s! [kcompactd0:96]
Feb 26 23:04:10 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 466s! [kcompactd0:96]
Feb 26 23:04:38 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 492s! [kcompactd0:96]
Feb 26 23:05:06 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 518s! [kcompactd0:96]
Feb 26 23:05:34 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 544s! [kcompactd0:96]
Feb 26 23:06:42 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 607s! [kcompactd0:96]
Feb 26 23:07:10 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 633s! [kcompactd0:96]
Feb 26 23:07:38 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 659s! [kcompactd0:96]
Feb 26 23:08:06 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 686s! [kcompactd0:96]
Feb 26 23:08:34 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 712s! [kcompactd0:96]
Feb 26 23:09:42 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 775s! [kcompactd0:96]
Feb 26 23:10:10 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 801s! [kcompactd0:96]
Feb 26 23:10:38 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 827s! [kcompactd0:96]
Feb 26 23:11:06 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 853s! [kcompactd0:96]
Feb 26 23:11:34 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 879s! [kcompactd0:96]
Feb 26 23:12:42 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 943s! [kcompactd0:96]
Feb 26 23:13:10 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 969s! [kcompactd0:96]
Feb 26 23:13:38 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 995s! [kcompactd0:96]
Feb 26 23:14:06 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 1021s! [kcompactd0:96]
Feb 26 23:14:34 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 1047s! [kcompactd0:96]
Feb 26 23:15:42 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 1110s! [kcompactd0:96]
Feb 26 23:16:10 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 1136s! [kcompactd0:96]
Feb 26 23:16:38 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 1162s! [kcompactd0:96]
Feb 26 23:17:06 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 1188s! [kcompactd0:96]

Has anyone else experienced this…? I ask because bugzilla.opensuse.org/show_bug.cgi?id=1193303#c0 appears to vaguely corroborate this, but it’s not very verbose about what the reporter experienced. Additionally, I’m using firefox-135.0.1-1.fc41.x86_64.rpm, so not a flatpak package. I didn’t even have any open at the time.

2

Kernel 6.13 by accident?

My system is constantly crashing, while 6.12 just works

1 Like
3

I had a similar issue in the past when a failing wifi adapter began losing connections intermittently.

In my case it seemed that connections where the browser was waiting for a response caused a lockup when the link was dropped. The new connection did not restore the link to the remote sight and the cpu was stuck waiting for an answer.

Check what your internet connection may be doing. If you see something in the journalctl logs that show repeated loss of connection and then it being restored your issue may be similar.

There may be something in the logs immediately before the segment you posted that would give more information. Yes, I see the info shown but it is not enough to identify anything.

EDIT
Do you by chance have an nvidia GPU?
It seems that those who updated early to the 6.13 kernel may not have gotten the needed upgrade to the nvidia 570 driver at the same time. A later upgrade would also upgrade the nvidia driver and avoid issues in that respect.

1 Like
4

@boredsquirrel, is it slowly hanging like my video depicts, too? Anyway, newly 6.13:

  1. #!/usr/bin/env sh
rpm -qa kernel

  2. kernel-6.12.13-200.fc41.x86_64
kernel-6.12.15-200.fc41.x86_64
kernel-6.13.4-200.fc41.x86_64

@computersavvy, apologies for being lazy. I did it from --pager-end, [1] this time, down to -p 7. There’s definitely some repetition, and of a stack trace:

Feb 26 23:17:06 SNRW3Q kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 1188s! [kcompactd0:96]
Feb 26 23:17:06 SNRW3Q kernel: CPU#5 Utilization every 4s during lockup:
Feb 26 23:17:06 SNRW3Q kernel:         #1: 100% system,          0% softirq,          0% hardirq,          0% idle
Feb 26 23:17:06 SNRW3Q kernel:         #2: 100% system,          0% softirq,          1% hardirq,          0% idle
Feb 26 23:17:06 SNRW3Q kernel:         #3: 100% system,          0% softirq,          0% hardirq,          0% idle
Feb 26 23:17:06 SNRW3Q kernel:         #4: 100% system,          0% softirq,          0% hardirq,          0% idle
Feb 26 23:17:06 SNRW3Q kernel:         #5: 100% system,          0% softirq,          1% hardirq,          0% idle
Feb 26 23:17:06 SNRW3Q kernel: Modules linked in: ib_core uinput rfcomm snd_seq_dummy snd_hrtimer nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag>
Feb 26 23:17:06 SNRW3Q kernel:  amdxcp i2c_algo_bit drm_ttm_helper hid_logitech_hidpp ttm crct10dif_pclmul drm_exec crc32_pclmul crc32c_intel polyval_clmulni polyval_generic gpu_sched ghash_clmulni_intel sha512_ssse3 sha256_ssse3 drm_suballoc_helper sha1_ssse3 drm_panel_backlight_quirks nvme drm_buddy sp5100_tco >
Feb 26 23:17:06 SNRW3Q kernel: CPU: 5 UID: 0 PID: 96 Comm: kcompactd0 Tainted: G    B D      L     6.13.4-200.fc41.x86_64 #1
Feb 26 23:17:06 SNRW3Q kernel: Tainted: [B]=BAD_PAGE, [D]=DIE, [L]=SOFTLOCKUP
Feb 26 23:17:06 SNRW3Q kernel: Hardware name: ASRock X670E Taichi/X670E Taichi, BIOS 3.08 09/19/2024
Feb 26 23:17:06 SNRW3Q kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x77/0x2d0
Feb 26 23:17:06 SNRW3Q kernel: Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 55 85 c0 74 10 0f b6 03 84 c0 74 09 f3 90 0f b6 03 <84> c0 75 f7 b8 01 00 00 00 66 89 03 5b 5d 41 5c 41 5d 41 5e e9 ab
Feb 26 23:17:06 SNRW3Q kernel: RSP: 0018:ffff99a7004efc18 EFLAGS: 00000202
Feb 26 23:17:06 SNRW3Q kernel: RAX: 0000000000000001 RBX: ffff8a219e4bee40 RCX: 0000000000000001
Feb 26 23:17:06 SNRW3Q kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8a219e4bee40
Feb 26 23:17:06 SNRW3Q kernel: RBP: 0000000000000005 R08: ffffef2f134c5908 R09: 0000000000000005
Feb 26 23:17:06 SNRW3Q kernel: R10: 0000000000000002 R11: 00000000000108ef R12: 0000000000000000
Feb 26 23:17:06 SNRW3Q kernel: R13: ffff8a21bded6040 R14: ffffef2f059d8000 R15: 0000000000167800
Feb 26 23:17:06 SNRW3Q kernel: FS:  0000000000000000(0000) GS:ffff8a219e480000(0000) knlGS:0000000000000000
Feb 26 23:17:06 SNRW3Q kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 26 23:17:06 SNRW3Q kernel: CR2: 00007f512147aa48 CR3: 00000002c682c000 CR4: 0000000000f50ef0
Feb 26 23:17:06 SNRW3Q kernel: PKRU: 55555554
Feb 26 23:17:06 SNRW3Q kernel: Call Trace:
Feb 26 23:17:06 SNRW3Q kernel:  <IRQ>
Feb 26 23:17:06 SNRW3Q kernel:  ? watchdog_timer_fn.cold+0x314/0x319
Feb 26 23:17:06 SNRW3Q kernel:  ? sched_clock_cpu+0xf/0x1f0
Feb 26 23:17:06 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 26 23:17:06 SNRW3Q kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
Feb 26 23:17:06 SNRW3Q kernel:  ? __hrtimer_run_queues+0x113/0x280
Feb 26 23:17:06 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 26 23:17:06 SNRW3Q kernel:  ? hrtimer_interrupt+0xff/0x230
Feb 26 23:17:06 SNRW3Q kernel:  ? __sysvec_apic_timer_interrupt+0x52/0x100
Feb 26 23:17:06 SNRW3Q kernel:  ? sysvec_apic_timer_interrupt+0x6c/0x90
Feb 26 23:17:06 SNRW3Q kernel:  </IRQ>
Feb 26 23:17:06 SNRW3Q kernel:  <TASK>
Feb 26 23:17:06 SNRW3Q kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Feb 26 23:17:06 SNRW3Q kernel:  ? native_queued_spin_lock_slowpath+0x77/0x2d0
Feb 26 23:17:06 SNRW3Q kernel:  _raw_spin_lock+0x29/0x30
Feb 26 23:17:06 SNRW3Q kernel:  drain_pages_zone+0x2c/0x90
Feb 26 23:17:06 SNRW3Q kernel:  lru_add_drain_cpu_zone+0x28/0x50
Feb 26 23:17:06 SNRW3Q kernel:  compact_zone+0x448/0x1120
Feb 26 23:17:06 SNRW3Q kernel:  kcompactd_do_work+0x121/0x270
Feb 26 23:17:06 SNRW3Q kernel:  kcompactd+0x40b/0x4b0
Feb 26 23:17:06 SNRW3Q kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Feb 26 23:17:06 SNRW3Q kernel:  ? __pfx_kcompactd+0x10/0x10
Feb 26 23:17:06 SNRW3Q kernel:  kthread+0xcf/0x100
Feb 26 23:17:06 SNRW3Q kernel:  ? __pfx_kthread+0x10/0x10
Feb 26 23:17:06 SNRW3Q kernel:  ret_from_fork+0x31/0x50
Feb 26 23:17:06 SNRW3Q kernel:  ? __pfx_kthread+0x10/0x10
Feb 26 23:17:06 SNRW3Q kernel:  ret_from_fork_asm+0x1a/0x30
Feb 26 23:17:06 SNRW3Q kernel:  </TASK>
Feb 26 23:17:07 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 26 23:17:07 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes
Feb 26 23:17:10 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 26 23:17:10 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes
Feb 26 23:17:13 SNRW3Q kwin_wayland[1855]: kwin_core: Failed to open /dev/dri/card0 device (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Feb 26 23:17:13 SNRW3Q kwin_wayland[1855]: kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
Feb 26 23:17:13 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 26 23:17:14 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes
Feb 26 23:17:14 SNRW3Q abrt-server[69013]: Can't find a meaningful backtrace for hashing in '.'
Feb 26 23:17:14 SNRW3Q abrt-server[69013]: Deleting non-reportable oops '.' because DropNotReportableOopses is set to 'yes'
Feb 26 23:17:14 SNRW3Q abrt-server[69013]: 'post-create' on '/var/spool/abrt/oops-2025-02-26-23:13:12-1343-0' exited with 1
Feb 26 23:17:14 SNRW3Q abrt-server[69013]: Deleting problem directory '/var/spool/abrt/oops-2025-02-26-23:13:12-1343-0'
Feb 26 23:17:14 SNRW3Q abrt-server[69013]: Lock file '.lock' was locked by process 69119, but it crashed?
Feb 26 23:17:15 SNRW3Q abrt-dump-journal-oops[1343]: Reported 1 kernel oopses to Abrt
Feb 26 23:17:17 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 26 23:17:17 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes
Feb 26 23:17:20 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 26 23:17:20 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes
Feb 26 23:17:24 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 26 23:17:24 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes
Feb 26 23:17:27 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 26 23:17:27 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes

I did once have a problematic PCIe NIC connected, but I removed it after reporting the fault to the manufacturer and distributor. I also had a problem with my MB’s in-built one, but a firmware update remediated that:

Interestingly, my internet connection has become very slow all of a sudden.

No, thank gosh. That’s one less significant headache.

  1. unix.stackexchange.com/revisions/654562/2 ↩︎

5

FWIW, it looks like that error has been reported upstream recently:

https://lore.kernel.org/linux-mm/CAJnrk1ZFfb7p01nkN=+tTJFt925PEAQyB=zRcsUM7Ue+TV2pZA@mail.gmail.com/T/

2 Likes
6

@glb, yeah. I saw that. Very weird that they reported the bug via e-mail, despite hosting a perfectly functional Bugzilla instance. Makes it difficult to track whether it’s been remediated without actively following a 100-person e-mail thread. For that same reason, I’ve been unable to correlate that message to this specific symptom.

7

Well, the reported symptoms (system crash) are similar:

On Thu, 6 Feb 2025 at 11:54, Christian Heusel christian@heusel.eu wrote:

Hello everyone,

we have recently received [a report][0] on the Arch Linux Gitlab about
multiple users having system crashes when using Flatpak programs and
related FUSE errors in their dmesg logs.

And further down is a report of the same error message from your original post:

Feb 06 11:07:34 frost kernel: BUG: Bad page state in process fuse mainloop pfn:2da0d5
Feb 06 11:07:34 frost kernel: page: refcount:-1 mapcount:0 mapping:0000000000000000 index:0xf pfn:0x2da0d5
Feb 06 11:07:34 frost kernel: flags: 0x17ffffd0000020(lru|node=0|zone=2|lastcpupid=0x1fffff)
Feb 06 11:07:34 frost kernel: raw: 0017ffffd0000020 dead000000000100 dead000000000122 0000000000000000
Feb 06 11:07:34 frost kernel: raw: 000000000000000f 0000000000000000 ffffffffffffffff 0000000000000000
Feb 06 11:07:34 frost kernel: page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag(s) set
Feb 06 11:07:34 frost kernel: Modules linked in: cts …

There is zero chance that a bug that has been reported only two weeks ago on kernel.org will have a remedy that is available to end users in the stable repos of downstream distros. I’d use an older kernel and keep an eye on that thread. There should eventually be a patch submitted to GitLab and then it will be tagged with the kernel releases to which it has been applied.

1 Like
9

I made a wiki post for workarounds

2 Likes
10

Whilst using kernel-6.13.4-200.fc41.x86_64, I attempted to invoke access a file: path via the FreeDesktop Documents Portal integration in app/com.github.Murmele.Gittyup/x86_64/stable --commit=adfe463ee26a63bdaaa0af13f71e26bf9a925d37f43b4527c7b14625ab5a08a7. Confirmation immediately hung the OS, with journalctl -b -1 reporting the undermentioned:

Feb 27 14:39:30 SNRW3Q xdg-document-portal[1893]: fuse: writing device: Invalid argument
Feb 27 14:39:30 SNRW3Q xdg-desktop-portal-kde[2163]: QWindow::fromWinId(): platform plugin does not support foreign windows.
Feb 27 14:39:33 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 27 14:39:33 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes
Feb 27 14:39:36 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
Feb 27 14:39:36 SNRW3Q kernel: amdgpu 0000:59:00.0: [drm] Cannot find any crtc or sizes
Feb 27 14:39:37 SNRW3Q kernel: list_add corruption. next->prev should be prev (ffff94351e6bee70), but was ffff942e00a3aa18. (next=fffff9155c0e8d48).
Feb 27 14:39:37 SNRW3Q kernel: ------------[ cut here ]------------
Feb 27 14:39:37 SNRW3Q kernel: kernel BUG at lib/list_debug.c:29!
Feb 27 14:39:37 SNRW3Q kernel: Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
Feb 27 14:39:37 SNRW3Q kernel: CPU: 9 UID: 1000 PID: 1914 Comm: fuse mainloop Not tainted 6.13.4-200.fc41.x86_64 #1
Feb 27 14:39:37 SNRW3Q kernel: Hardware name: ASRock X670E Taichi/X670E Taichi, BIOS 3.08 09/19/2024
Feb 27 14:39:37 SNRW3Q kernel: RIP: 0010:__list_add_valid_or_report.cold+0x4b/0x5b
Feb 27 14:39:37 SNRW3Q kernel: Code: fb ff 0f 0b 48 89 d1 48 89 c6 4c 89 c2 48 c7 c7 a8 c6 e3 bb e8 b3 8a fb ff 0f 0b 48 89 c1 48 c7 c7 50 c6 e3 bb e8 a2 8a fb ff <0f> 0b 48 c7 c7 28 c6 e3 bb e8 94 8a fb ff 0f 0b 48 89 fe 48 c7 c7
Feb 27 14:39:37 SNRW3Q kernel: RSP: 0018:ffffa03e45847a50 EFLAGS: 00010246
Feb 27 14:39:37 SNRW3Q kernel: RAX: 0000000000000075 RBX: ffff94351e6bee40 RCX: 0000000000000000
Feb 27 14:39:37 SNRW3Q kernel: RDX: 0000000000000000 RSI: ffff94351e6a1900 RDI: ffff94351e6a1900
Feb 27 14:39:37 SNRW3Q kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Feb 27 14:39:37 SNRW3Q kernel: R10: 74707572726f6320 R11: 6464615f7473696c R12: ffff94351e6bee70
Feb 27 14:39:37 SNRW3Q kernel: R13: 0000000000000001 R14: ffff94353ded6040 R15: 0000000000000001
Feb 27 14:39:37 SNRW3Q kernel: FS:  00007fafad6f76c0(0000) GS:ffff94351e680000(0000) knlGS:0000000000000000
Feb 27 14:39:37 SNRW3Q kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 27 14:39:37 SNRW3Q kernel: CR2: 00007faf94004e78 CR3: 00000001a584c000 CR4: 0000000000f50ef0
Feb 27 14:39:37 SNRW3Q kernel: PKRU: 55555554
Feb 27 14:39:37 SNRW3Q kernel: Call Trace:
Feb 27 14:39:37 SNRW3Q kernel:  <TASK>
Feb 27 14:39:37 SNRW3Q kernel:  ? __die_body.cold+0x19/0x27
Feb 27 14:39:37 SNRW3Q kernel:  ? die+0x2e/0x50
Feb 27 14:39:37 SNRW3Q kernel:  ? do_trap+0xca/0x110
Feb 27 14:39:37 SNRW3Q kernel:  ? do_error_trap+0x6a/0x90
Feb 27 14:39:37 SNRW3Q kernel:  ? __list_add_valid_or_report.cold+0x4b/0x5b
Feb 27 14:39:37 SNRW3Q kernel:  ? exc_invalid_op+0x50/0x70
Feb 27 14:39:37 SNRW3Q kernel:  ? __list_add_valid_or_report.cold+0x4b/0x5b
Feb 27 14:39:37 SNRW3Q kernel:  ? asm_exc_invalid_op+0x1a/0x20
Feb 27 14:39:37 SNRW3Q kernel:  ? __list_add_valid_or_report.cold+0x4b/0x5b
Feb 27 14:39:37 SNRW3Q kernel:  free_unref_page_commit+0x94/0x370
Feb 27 14:39:37 SNRW3Q kernel:  free_unref_page+0x46a/0x600
Feb 27 14:39:37 SNRW3Q kernel:  fuse_copy_page+0x37e/0x6c0 [fuse]
Feb 27 14:39:37 SNRW3Q kernel:  ? do_splice+0x427/0x890
Feb 27 14:39:37 SNRW3Q kernel:  fuse_copy_args+0x186/0x210 [fuse]
Feb 27 14:39:37 SNRW3Q kernel:  fuse_dev_do_write+0x7f5/0x1420 [fuse]
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? syscall_exit_to_user_mode+0x10/0x210
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? do_syscall_64+0x8e/0x160
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  fuse_dev_splice_write+0x28d/0x370 [fuse]
Feb 27 14:39:37 SNRW3Q kernel:  do_splice+0x308/0x890
Feb 27 14:39:37 SNRW3Q kernel:  __do_splice+0x204/0x220
Feb 27 14:39:37 SNRW3Q kernel:  __x64_sys_splice+0x84/0xf0
Feb 27 14:39:37 SNRW3Q kernel:  do_syscall_64+0x82/0x160
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? syscall_exit_to_user_mode+0x1d5/0x210
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? do_syscall_64+0x8e/0x160
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? do_syscall_64+0x8e/0x160
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? do_syscall_64+0x8e/0x160
Feb 27 14:39:37 SNRW3Q kernel:  ? exc_page_fault+0x7e/0x180
Feb 27 14:39:37 SNRW3Q kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 27 14:39:37 SNRW3Q kernel: RIP: 0033:0x7fafbe83ed73
Feb 27 14:39:37 SNRW3Q kernel: Code: 7d e8 48 89 4d d0 e8 4c 73 f7 ff 44 8b 4d d8 4c 8b 45 c8 89 c3 4c 8b 55 d0 8b 55 dc b8 13 01 00 00 48 8b 75 e0 8b 7d e8 0f 05 <48> 3d 00 f0 ff ff 77 2d 89 df 48 89 45 e8 e8 9a 73 f7 ff 48 8b 45
Feb 27 14:39:37 SNRW3Q kernel: RSP: 002b:00007fafad6f68e0 EFLAGS: 00000297 ORIG_RAX: 0000000000000113
Feb 27 14:39:37 SNRW3Q kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fafbe83ed73
Feb 27 14:39:37 SNRW3Q kernel: RDX: 0000000000000007 RSI: 0000000000000000 RDI: 000000000000000c
Feb 27 14:39:37 SNRW3Q kernel: RBP: 00007fafad6f6920 R08: 0000000000008010 R09: 0000000000000001
Feb 27 14:39:37 SNRW3Q kernel: R10: 0000000000000000 R11: 0000000000000297 R12: 00007fafad6f6a60
Feb 27 14:39:37 SNRW3Q kernel: R13: 0000000000000001 R14: 0000000000000008 R15: 00007fafad6f6ab0
Feb 27 14:39:37 SNRW3Q kernel:  </TASK>
Feb 27 14:39:37 SNRW3Q kernel: Modules linked in: uinput snd_seq_dummy rfcomm snd_hrtimer nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables uhid qrtr bnep sunrpc binfmt_misc vfat fat squashfs iwlmvm intel_rapl_msr amd_atl spd5118 snd_hda_codec_hdmi intel_rapl_common mac80211 edac_mce_amd uvcvideo snd_hda_intel snd_intel_dspcfg uvc libarc4 videobuf2_vmalloc kvm_amd snd_intel_sdw_acpi snd_usb_audio snd_hda_codec videobuf2_memops snd_hda_core videobuf2_v4l2 btusb kvm snd_usbmidi_lib snd_ump btrtl btintel snd_rawmidi snd_hwdep iwlwifi videobuf2_common btbcm snd_seq btmtk i2c_piix4 rapl wmi_bmof intel_wmi_thunderbolt pcspkr snd_seq_device i2c_smbus videodev k10temp snd_pcm bluetooth mc snd_timer cfg80211 corsair_psu snd thunderbolt soundcore r8169 realtek rfkill joydev gpio_amdpt gpio_generic loop nfnetlink zram lz4hc_compress lz4_compress amdgpu
Feb 27 14:39:37 SNRW3Q kernel:  hid_logitech_hidpp amdxcp i2c_algo_bit drm_ttm_helper crct10dif_pclmul ttm crc32_pclmul drm_exec crc32c_intel gpu_sched polyval_clmulni polyval_generic drm_suballoc_helper ghash_clmulni_intel sha512_ssse3 nvme sha256_ssse3 drm_panel_backlight_quirks sha1_ssse3 drm_buddy sp5100_tco drm_display_helper uas cec nvme_core usb_storage nvme_auth video wmi hid_logitech_dj fuse i2c_dev
Feb 27 14:39:37 SNRW3Q kernel: ---[ end trace 0000000000000000 ]---
Feb 27 14:39:37 SNRW3Q kernel: RIP: 0010:__list_add_valid_or_report.cold+0x4b/0x5b
Feb 27 14:39:37 SNRW3Q kernel: Code: fb ff 0f 0b 48 89 d1 48 89 c6 4c 89 c2 48 c7 c7 a8 c6 e3 bb e8 b3 8a fb ff 0f 0b 48 89 c1 48 c7 c7 50 c6 e3 bb e8 a2 8a fb ff <0f> 0b 48 c7 c7 28 c6 e3 bb e8 94 8a fb ff 0f 0b 48 89 fe 48 c7 c7
Feb 27 14:39:37 SNRW3Q kernel: RSP: 0018:ffffa03e45847a50 EFLAGS: 00010246
Feb 27 14:39:37 SNRW3Q kernel: RAX: 0000000000000075 RBX: ffff94351e6bee40 RCX: 0000000000000000
Feb 27 14:39:37 SNRW3Q kernel: RDX: 0000000000000000 RSI: ffff94351e6a1900 RDI: ffff94351e6a1900
Feb 27 14:39:37 SNRW3Q kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Feb 27 14:39:37 SNRW3Q kernel: R10: 74707572726f6320 R11: 6464615f7473696c R12: ffff94351e6bee70
Feb 27 14:39:37 SNRW3Q kernel: R13: 0000000000000001 R14: ffff94353ded6040 R15: 0000000000000001
Feb 27 14:39:37 SNRW3Q kernel: FS:  00007fafad6f76c0(0000) GS:ffff94351e680000(0000) knlGS:0000000000000000
Feb 27 14:39:37 SNRW3Q kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 27 14:39:37 SNRW3Q kernel: CR2: 00007faf94004e78 CR3: 00000001a584c000 CR4: 0000000000f50ef0
Feb 27 14:39:37 SNRW3Q kernel: PKRU: 55555554
Feb 27 14:39:37 SNRW3Q kernel: note: fuse mainloop[1914] exited with preempt_count 2
Feb 27 14:39:37 SNRW3Q kernel: BUG: Bad page state in process Isolated Web Co  pfn:3218f8
Feb 27 14:39:37 SNRW3Q kernel: page: refcount:-1 mapcount:0 mapping:0000000000000000 index:0x29 pfn:0x3218f8
Feb 27 14:39:37 SNRW3Q kernel: flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff)
Feb 27 14:39:37 SNRW3Q kernel: raw: 0017ffffc0000000 dead000000000100 dead000000000122 0000000000000000
Feb 27 14:39:37 SNRW3Q kernel: raw: 0000000000000029 0000000000000000 ffffffffffffffff 0000000000000000
Feb 27 14:39:37 SNRW3Q kernel: page dumped because: nonzero _refcount
Feb 27 14:39:37 SNRW3Q kernel: Modules linked in: uinput snd_seq_dummy rfcomm snd_hrtimer nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables uhid qrtr bnep sunrpc binfmt_misc vfat fat squashfs iwlmvm intel_rapl_msr amd_atl spd5118 snd_hda_codec_hdmi intel_rapl_common mac80211 edac_mce_amd uvcvideo snd_hda_intel snd_intel_dspcfg uvc libarc4 videobuf2_vmalloc kvm_amd snd_intel_sdw_acpi snd_usb_audio snd_hda_codec videobuf2_memops snd_hda_core videobuf2_v4l2 btusb kvm snd_usbmidi_lib snd_ump btrtl btintel snd_rawmidi snd_hwdep iwlwifi videobuf2_common btbcm snd_seq btmtk i2c_piix4 rapl wmi_bmof intel_wmi_thunderbolt pcspkr snd_seq_device i2c_smbus videodev k10temp snd_pcm bluetooth mc snd_timer cfg80211 corsair_psu snd thunderbolt soundcore r8169 realtek rfkill joydev gpio_amdpt gpio_generic loop nfnetlink zram lz4hc_compress lz4_compress amdgpu
Feb 27 14:39:37 SNRW3Q kernel:  hid_logitech_hidpp amdxcp i2c_algo_bit drm_ttm_helper crct10dif_pclmul ttm crc32_pclmul drm_exec crc32c_intel gpu_sched polyval_clmulni polyval_generic drm_suballoc_helper ghash_clmulni_intel sha512_ssse3 nvme sha256_ssse3 drm_panel_backlight_quirks sha1_ssse3 drm_buddy sp5100_tco drm_display_helper uas cec nvme_core usb_storage nvme_auth video wmi hid_logitech_dj fuse i2c_dev
Feb 27 14:39:37 SNRW3Q kernel: CPU: 7 UID: 1000 PID: 22224 Comm: Isolated Web Co Tainted: G      D            6.13.4-200.fc41.x86_64 #1
Feb 27 14:39:37 SNRW3Q kernel: Tainted: [D]=DIE
Feb 27 14:39:37 SNRW3Q kernel: Hardware name: ASRock X670E Taichi/X670E Taichi, BIOS 3.08 09/19/2024
Feb 27 14:39:37 SNRW3Q kernel: Call Trace:
Feb 27 14:39:37 SNRW3Q kernel:  <TASK>
Feb 27 14:39:37 SNRW3Q kernel:  dump_stack_lvl+0x5d/0x80
Feb 27 14:39:37 SNRW3Q kernel:  bad_page.cold+0x7a/0x91
Feb 27 14:39:37 SNRW3Q kernel:  __rmqueue_pcplist+0x209/0xeb0
Feb 27 14:39:37 SNRW3Q kernel:  ? current_time+0x40/0x120
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  get_page_from_freelist+0x2d3/0x1be0
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? pipe_write+0x415/0x690
Feb 27 14:39:37 SNRW3Q kernel:  __alloc_pages_noprof+0x184/0x330
Feb 27 14:39:37 SNRW3Q kernel:  alloc_pages_mpol_noprof+0x8d/0x200
Feb 27 14:39:37 SNRW3Q kernel:  folio_alloc_mpol_noprof+0x14/0x30
Feb 27 14:39:37 SNRW3Q kernel:  vma_alloc_folio_noprof+0x69/0xb0
Feb 27 14:39:37 SNRW3Q kernel:  do_anonymous_page+0x33c/0x920
Feb 27 14:39:37 SNRW3Q kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Feb 27 14:39:37 SNRW3Q kernel:  ? ___pte_offset_map+0x1b/0x180
Feb 27 14:39:37 SNRW3Q kernel:  __handle_mm_fault+0xb34/0xf90
Feb 27 14:39:37 SNRW3Q kernel:  handle_mm_fault+0x107/0x330
Feb 27 14:39:37 SNRW3Q kernel:  do_user_addr_fault+0x2ca/0x7b0
Feb 27 14:39:37 SNRW3Q kernel:  exc_page_fault+0x7e/0x180
Feb 27 14:39:37 SNRW3Q kernel:  asm_exc_page_fault+0x26/0x30
Feb 27 14:39:37 SNRW3Q kernel: RIP: 0033:0x7f7cfaddc370
Feb 27 14:39:37 SNRW3Q kernel: Code: 0f 7e 00 80 79 10 00 4c 8b 60 08 66 0f 6c c2 75 64 8b 41 14 3d 54 05 00 00 74 5a 8d 70 01 48 8d 04 40 48 8d 44 c1 18 89 71 14 <4c> 89 60 10 0f 11 00 83 83 d0 00 00 00 01 85 d2 74 30 8d 42 ff 48
Feb 27 14:39:37 SNRW3Q kernel: RSP: 002b:00007ffd03eea770 EFLAGS: 00010287
Feb 27 14:39:37 SNRW3Q kernel: RAX: 00007f7cca163ff0 RBX: 00007f7d03a9c300 RCX: 00007f7cca15d000
Feb 27 14:39:37 SNRW3Q kernel: RDX: 00000000000002d8 RSI: 00000000000004aa RDI: 00007f7d03a9c300
Feb 27 14:39:37 SNRW3Q kernel: RBP: 00007f7d00960c40 R08: 0000000000210101 R09: 0000000000000100
Feb 27 14:39:37 SNRW3Q kernel: R10: 0000000000000000 R11: 00007f7d04288000 R12: 00007f7d008a3bf0
Feb 27 14:39:37 SNRW3Q kernel: R13: 0000000000000001 R14: 00000d7598b8ae05 R15: 00007ffd03eea8c0
Feb 27 14:39:37 SNRW3Q kernel:  </TASK>
Feb 27 14:39:37 SNRW3Q kernel: BUG: Bad page state in process Isolated Web Co  pfn:5c8948

Consequently, you were all correct that this was probably a symptom of the referenced BR, since although my initial experience with it was different to yours, it now reproduces identically.

Though, it’s rather strange that despite sudo sysctl kernel.panic returning kernel.panic = 0, the OS doesn’t automatically reboot. At least I’m not the sole person with this problem, per askubuntu.com/q/222835. I’m estimating that it’s a kernel panic, since SysRq doesn’t work.

1 Like
11

Nice you managed to get logs!

Do you want to make a howto or something? Maybe fix the flatpak docs?

I was not able to get logs, I didnt know you could use xdg-desktop-portal from the terminal.

Tried to debug Okular with gdb as I thought it was an issue with that app

1 Like
12

@boredsquirrel, I didn’t need to, actually. I just:

  1. Booted into kernel-6.13.4 (via GRUB2), invoked Gittyup (with flatpak run);
  2. Dutifully sacrificed that boot to the kernel gods by invoking, selecting, and confirming a directory in the KDE File Picker;
  3. Hit the motherboard’s RESET_SW (⏻⃣) when it inevitably hung; then:
  4. Captured the logs from journalctl on the next boot (in kernel-6.12.15).

Luckily, unlike running a flatpak app through GDB (which is a nightmare), kernel bugs go straight to SystemD’s journal.

Though, you can - I think the portal can be invoked from DBus. If of interest, the undermentioned appears to contain some information about that:

Would be nice to have a minimal reproducible sample, but I bet the kernel devs don’t need it, since they’ve stated that a git blame has demonstrated the origin of the problem.

1 Like
13

Aaah okay so it might just be that I have disabled some of these kernel debugging features. They generally expose a lot of system details, I thought I made a complete switch, but maybe there is stuff missing

1 Like
14

wait, so… is this still unresolved?
I was just looking to reinstall Silverblue, but I wasn’t sure if ALL of the issues with 6.13 were resolved (I wanted to wait out the bugs before writing an iso). The flatpak issue is resolved in .5, but I was wondering if there’s anything else I should wait out, or.

15

@blind-confused, my response that you’ve responded to merely elaborates about the original post’s problem. The symptom that my response describes has been resolved in kernel-6.13.5-200.fc41.x86_64, and I’ve had no reproduction of the (very unique) symptom demonstrated in the original post since, regardless.

Although this is caused by how the kernel interacts with FUSE filsystems, I am not using an immutable distribution, so I can’t guarantee it’s been resolved for them.

1 Like
16
2 Likes