View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001317 | channel: elrepo/el8 | kmod-wireguard | public | 2023-01-17 13:42 | 2023-01-22 09:36 |
| Reporter | brianjmurrell | Assigned To | pperry | ||
| Priority | high | Severity | crash | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Summary | 0001317: kmod-wireguard causing CPU soft lockups | ||||
| Description | kmod-wireguard-1.0.20220627-4.el8_7.elrepo.x86_64 is causing CPU soft lockups: [ 860.647931] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kworker/1:7:1861] [ 860.655188] Modules linked in: wireguard(E) ip6_udp_tunnel udp_tunnel nft_counter xt_conntrack ipt_REJECT xt_comment xt_owner nft_compat nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nf_log_syslog nft_log nft_ct nf_tables_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink vfat fat intel_rapl_msr intel_rapl_common pcspkr joydev i2c_piix4 xfs libcrc32c nvme_tcp(X) nvme_fabrics nvme nvme_core sd_mod t10_pi sg ata_generic crct10dif_pclmul crc32_pclmul crc32c_intel bochs drm_vram_helper drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm_ttm_helper ttm drm ghash_clmulni_intel ata_piix virtio_net libata serio_raw net_failover virtio_scsi failover dm_multipath sunrpc dm_mirror dm_region_hash dm_log dm_mod be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi [ 860.759982] CPU: 1 PID: 1861 Comm: kworker/1:7 Kdump: loaded Tainted: G EL X --------- - - 4.18.0-425.3.1.el8.x86_64 #1 [ 860.768386] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.4.1 12/03/2020 [ 860.773787] Workqueue: events_power_efficient wg_ratelimiter_gc_entries [wireguard] [ 860.779919] RIP: 0010:native_safe_halt+0xe/0x20 [ 860.783261] Code: 00 f0 80 48 02 20 48 8b 00 a8 08 75 c0 e9 79 ff ff ff 90 90 90 90 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d e6 96 41 00 fb f4 <e9> fd 09 21 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 e9 07 00 00 [ 860.794692] RSP: 0018:ffffbf7a0104fe18 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 [ 860.849038] RAX: 0000000000000003 RBX: ffffffffc0847fb8 RCX: 0000000000000008 [ 860.854777] RDX: 0000000000000000 RSI: 0000000000000003 RDI: ffffffffc0847fb8 [ 860.860764] RBP: ffff9e647d32bcc0 R08: 0000000000000008 R09: 000000000000005c [ 860.866738] R10: 8080808080808080 R11: 0000000000000018 R12: 0000000000000000 [ 860.872370] R13: 0000000000000001 R14: 0000000000000100 R15: 0000000000080000 [ 860.878090] FS: 0000000000000000(0000) GS:ffff9e647d300000(0000) knlGS:0000000000000000 [ 860.883782] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 860.888057] CR2: 00007f06ca0090cc CR3: 000000000a2d2000 CR4: 00000000003506e0 [ 860.893017] Call Trace: [ 860.894755] kvm_wait+0x58/0x60 [ 860.896824] __pv_queued_spin_lock_slowpath+0x268/0x2a0 [ 860.948570] wg_ratelimiter_gc_entries+0x10c/0x170 [wireguard] [ 860.953186] process_one_work+0x1a7/0x360 [ 860.956359] ? create_worker+0x1a0/0x1a0 [ 860.959026] worker_thread+0x30/0x390 [ 860.962277] ? create_worker+0x1a0/0x1a0 [ 860.965024] kthread+0x10b/0x130 [ 860.967300] ? set_kthread_struct+0x50/0x50 [ 860.970265] ret_from_fork+0x35/0x40 | ||||
| Steps To Reproduce | Simply create a connection: [Interface] PrivateKey = [redacted] Address = 10.14.0.5/24 [Peer] PublicKey = [redacted] Endpoint = vpn.example.com:1234 AllowedIPs = 10.14.0.1/32, 10.75.22.0/24 and start it up. | ||||
| Tags | No tags attached. | ||||
|
|
Please update your system to kernel-4.18.0-425.10.1.el8_7 as there is a Red Hat recognized bug with kernel-4.18.0-425.3.1.el8.x86_64 For reference please see: (1) https://access.redhat.com/solutions/6985596 (2) https://elrepo.org/bugs/view.php?id=1316 |
|
|
I started with 4.18.0-425.10.1.el8_7 and only went back to 4.18.0-425.3.1.el8.x86_64 to eliminate any suspicion of kABI breakage with the 4.18.0-425.3.1.el8.x86_64 wireguard kmod. |
|
|
Hrm. I just tried 4.18.0-425.10.1.el8_7 again and it does seem to be working now. Strange. |
|
|
There was indeed an issue with the kmod-wireguard package and the latest RHEL kernel, but that was fixed in the latest wireguard release: kmod-wireguard-1.0.20220627-4.el8_7.elrepo.x86_64.rpm which you seem to have installed. I suspect when you first noticed the issue, you were maybe still on the old wiregaurd package and it subsequently got updated? Anyway, I'll assume it's fixed. Please do let us know if otherwise. |
|
|
Marking as fixed as this was fixed in the latest kmod-wireguard release. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-17 13:42 | brianjmurrell | New Issue | |
| 2023-01-17 13:42 | brianjmurrell | Status | new => assigned |
| 2023-01-17 13:42 | brianjmurrell | Assigned To | => pperry |
| 2023-01-17 14:46 | burakkucat | Relationship added | related to 0001316 |
| 2023-01-17 14:53 | burakkucat | Note Added: 0008927 | |
| 2023-01-17 15:02 | brianjmurrell | Note Added: 0008928 | |
| 2023-01-17 15:33 | brianjmurrell | Note Added: 0008929 | |
| 2023-01-17 18:05 | pperry | Note Added: 0008930 | |
| 2023-01-22 09:36 | pperry | Status | assigned => resolved |
| 2023-01-22 09:36 | pperry | Resolution | open => fixed |
| 2023-01-22 09:36 | pperry | Note Added: 0008937 |
