1. Please describe the problem: Running sadc (via sysstat-collect.service) triggers a GPF in _raw_spin_lock_irqsave. 2. What is the Version-Release number of the kernel: kernel-6.8.10-300.fc40.x86_64 and later. 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Yes. kernel-6.8.10-300.fc40.x86_64. The previous working kernel is kernel-6.8.9-300.fc40.x86_64. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes, every time. 1. Boot into kernel-6.8.10-300.fc40.x86_64 or later. 2. systemctl start sysstat-collect.service. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: It looks like it's fixed in kernel-6.9.3-200.fc40. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Since it's fixed in 6.9.3, I'll post only the trace for reference: Jun 06 20:20:13 kernel: general protection fault, probably for non-canonical address 0x64696c61766e4c20: 0000 [#1] PREEMPT SMP NOPTI Jun 06 20:20:13 kernel: CPU: 0 PID: 1161 Comm: sadc Not tainted 6.8.11-300.fc40.x86_64 #1 Jun 06 20:20:13 kernel: Hardware name: Intel Corporation Milstead Platform/Granite Well, BIOS CDV W Series 05 08/27/2015 Jun 06 20:20:13 kernel: RIP: 0010:_raw_spin_lock_irqsave+0x27/0x50 Jun 06 20:20:13 kernel: Code: 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00 65 ff 05 48 c5 ec 51 31 c0 ba 01 00 00 00 <f0> 0f b1 17 75 09 48 89 d8 5b c3 cc cc cc cc 89 c6 e8 93 08 00 00 Jun 06 20:20:13 kernel: RSP: 0018:ffffb87700ae3a38 EFLAGS: 00010046 Jun 06 20:20:13 kernel: RAX: 0000000000000000 RBX: 0000000000000286 RCX: 0000000000001008 Jun 06 20:20:13 kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: 64696c61766e4c20 Jun 06 20:20:13 kernel: RBP: 64696c61766e4c20 R08: ffffb87700ae3a70 R09: 0000000000000000 Jun 06 20:20:13 kernel: R10: ffffb87700ae3ac8 R11: 0000000000000000 R12: ffffa0bf04f8d780 Jun 06 20:20:13 kernel: R13: 64696c61766e4920 R14: 0000000000000001 R15: 0000000000000001 Jun 06 20:20:13 kernel: FS: 00007fabce9f0740(0000) GS:ffffa0bf1bc00000(0000) knlGS:0000000000000000 Jun 06 20:20:13 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 06 20:20:13 kernel: CR2: 000055f0470b2011 CR3: 00000000d7924000 CR4: 00000000000006f0 Jun 06 20:20:13 kernel: Call Trace: Jun 06 20:20:13 kernel: <TASK> Jun 06 20:20:13 kernel: ? die_addr+0x36/0x90 Jun 06 20:20:13 kernel: ? exc_general_protection+0x17c/0x450 Jun 06 20:20:13 kernel: ? asm_exc_general_protection+0x26/0x30 Jun 06 20:20:13 kernel: ? _raw_spin_lock_irqsave+0x27/0x50 Jun 06 20:20:13 kernel: __percpu_counter_sum+0x18/0xb0 Jun 06 20:20:13 kernel: ? __kmalloc_node+0x455/0x4c0 Jun 06 20:20:13 kernel: nfsd_show+0x53/0x1f0 [nfsd] Jun 06 20:20:13 kernel: seq_read_iter+0x11f/0x480 Jun 06 20:20:13 kernel: seq_read+0x12f/0x170 Jun 06 20:20:13 kernel: proc_reg_read+0x5a/0xa0 Jun 06 20:20:13 kernel: vfs_read+0xac/0x380 Jun 06 20:20:13 kernel: ? path_openat+0x7cf/0x1120 Jun 06 20:20:13 kernel: ksys_read+0x6d/0xf0 Jun 06 20:20:13 kernel: do_syscall_64+0x83/0x170 Jun 06 20:20:13 kernel: ? __pfx_proc_put_link+0x10/0x10 Jun 06 20:20:13 kernel: ? __pfx_kfree_link+0x10/0x10 Jun 06 20:20:13 kernel: ? do_sys_openat2+0x9c/0xe0 Jun 06 20:20:13 kernel: ? syscall_exit_to_user_mode+0x83/0x230 Jun 06 20:20:13 kernel: ? do_syscall_64+0x8f/0x170 Jun 06 20:20:13 kernel: ? __do_sys_newfstat+0x68/0x70 Jun 06 20:20:13 kernel: ? syscall_exit_to_user_mode+0x83/0x230 Jun 06 20:20:13 kernel: ? do_syscall_64+0x8f/0x170 Jun 06 20:20:13 kernel: ? do_syscall_64+0x8f/0x170 Jun 06 20:20:13 kernel: ? do_syscall_64+0x8f/0x170 Jun 06 20:20:13 kernel: ? __irq_exit_rcu+0x4b/0xc0 Jun 06 20:20:13 kernel: entry_SYSCALL_64_after_hwframe+0x78/0x80 Jun 06 20:20:13 kernel: RIP: 0033:0x7fabcebe0cc1 Jun 06 20:20:13 kernel: Code: 00 48 8b 15 59 81 0d 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd e8 b0 aa 01 00 f3 0f 1e fa 80 3d 85 03 0e 00 00 74 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 4f c3 66 0f 1f 44 00 00 55 48 89 e5 48 83 ec Jun 06 20:20:13 kernel: RSP: 002b:00007ffda7ce49a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Jun 06 20:20:13 kernel: RAX: ffffffffffffffda RBX: 000055f04709a2e0 RCX: 00007fabcebe0cc1 Jun 06 20:20:13 kernel: RDX: 0000000000000400 RSI: 000055f047095770 RDI: 0000000000000004 Jun 06 20:20:13 kernel: RBP: 00007ffda7ce49e0 R08: 0000000000000001 R09: 0000000000000000 Jun 06 20:20:13 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007fabcecb8050 Jun 06 20:20:13 kernel: R13: 00007fabcecb7f00 R14: 0000000000000000 R15: 000055f04709a2e0 Jun 06 20:20:13 kernel: </TASK> Jun 06 20:20:13 kernel: Modules linked in: rpcrdma rdma_cm iw_cm ib_cm ib_core rfkill nft_limit xt_time ipt_REJECT nf_reject_ipv4 xt_multiport xt_set nft_chain_nat ip6t_REJECT nf_reject_ipv6 xt_nat xt_LOG nf_nat nf_log_syslog nf_conntrack_pptp xt_limit xt_CT xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables ip_se> Jun 06 20:20:13 kernel: fuse sunrpc nfnetlink zram xfs hid_logitech_hidpp sha512_ssse3 sha256_ssse3 sha1_ssse3 sata_sil24 video wmi hid_logitech_dj serio_raw Jun 06 20:20:13 kernel: ---[ end trace 0000000000000000 ]--- Jun 06 20:20:13 kernel: RIP: 0010:_raw_spin_lock_irqsave+0x27/0x50 Jun 06 20:20:13 kernel: Code: 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00 65 ff 05 48 c5 ec 51 31 c0 ba 01 00 00 00 <f0> 0f b1 17 75 09 48 89 d8 5b c3 cc cc cc cc 89 c6 e8 93 08 00 00 Jun 06 20:20:13 kernel: RSP: 0018:ffffb87700ae3a38 EFLAGS: 00010046 Jun 06 20:20:13 kernel: RAX: 0000000000000000 RBX: 0000000000000286 RCX: 0000000000001008 Jun 06 20:20:13 kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: 64696c61766e4c20 Jun 06 20:20:13 kernel: RBP: 64696c61766e4c20 R08: ffffb87700ae3a70 R09: 0000000000000000 Jun 06 20:20:13 kernel: R10: ffffb87700ae3ac8 R11: 0000000000000000 R12: ffffa0bf04f8d780 Jun 06 20:20:13 kernel: R13: 64696c61766e4920 R14: 0000000000000001 R15: 0000000000000001 Jun 06 20:20:13 kernel: FS: 00007fabce9f0740(0000) GS:ffffa0bf1bc00000(0000) knlGS:0000000000000000 Jun 06 20:20:13 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 06 20:20:13 kernel: CR2: 000055f0470b2011 CR3: 00000000d7924000 CR4: 00000000000006f0 Jun 06 20:20:13 kernel: note: sadc[1161] exited with irqs disabled Jun 06 20:20:13 kernel: note: sadc[1161] exited with preempt_count 1
Small correction: 6.8.12-300.fc40.x86_64 also seems to have this fixed.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.