Arch Linux

jonwilts

Member

Registered: 2024-04-16

Posts: 2

Kernel warning ("Unpatched return thunk in use") in 6.9.3 & 6.9.4-zen

Hi. I noticed the following warning in journalctl a couple of days ago (Kernel 6.9.3-zen1-1-zen). I updated this morning to 6.9.4-zen1-1-zen and the problem is still present. Googling it, I found a few other reports, e.g. https://discuss.cachyos.org/t/unpatched … t-logs/392

Jun 12 09:29:13 air kernel: ------------[ cut here ]------------
Jun 12 09:29:13 air kernel: Unpatched return thunk in use. This should not happen!
Jun 12 09:29:13 air kernel: WARNING: CPU: 1 PID: 356 at arch/x86/kernel/cpu/bugs.c:3023 __warn_thunk+0x2a/0x40
Jun 12 09:29:13 air kernel: Modules linked in: snd_hda_intel(+) wl(POE+) polyval_generic snd_intel_dspcfg spi_nor snd_intel_sdw_acpi gf128mul mtd ext4 ghash_>
Jun 12 09:29:13 air kernel:  spi_pxa2xx_platform video wmi dw_dmac
Jun 12 09:29:13 air kernel: CPU: 1 PID: 356 Comm: (udev-worker) Tainted: P     U     OE      6.9.3-zen1-1-zen #1 5638aa0ef9e579cd2ce899fcf8faea316c5c4dc5
Jun 12 09:29:13 air kernel: Hardware name: Apple Inc. MacBookAir7,2/Mac-937CB26E2E02BB01, BIOS 476.0.0.0.0 09/06/2022
Jun 12 09:29:13 air kernel: RIP: 0010:__warn_thunk+0x2a/0x40
Jun 12 09:29:13 air kernel: Code: 66 0f 1f 00 0f 1f 44 00 00 80 3d d0 4d 37 02 00 74 05 c3 cc cc cc cc 48 c7 c7 c0 bf e3 90 c6 05 bb 4d 37 02 01 e8 06 95 06 >
Jun 12 09:29:13 air kernel: RSP: 0018:ffffb05f40c17938 EFLAGS: 00010286
Jun 12 09:29:13 air kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027
Jun 12 09:29:13 air kernel: RDX: ffff9fa926ca19c8 RSI: 0000000000000001 RDI: ffff9fa926ca19c0
Jun 12 09:29:13 air kernel: RBP: ffffb05f40c17988 R08: ffffffff916b2648 R09: 00000000ffffefff
Jun 12 09:29:13 air kernel: R10: 0000000000000003 R11: 0000000000000002 R12: ffffffffc1c6fac1
Jun 12 09:29:13 air kernel: R13: ffffb05f40c179d0 R14: ffff9fa7d2d57b00 R15: ffff9fa7c8a3e438
Jun 12 09:29:13 air kernel: FS:  00007dd2d3b89680(0000) GS:ffff9fa926c80000(0000) knlGS:0000000000000000
Jun 12 09:29:13 air kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 12 09:29:13 air kernel: CR2: 000077bc78dff000 CR3: 00000001084f2004 CR4: 00000000003706f0
Jun 12 09:29:13 air kernel: Call Trace:
Jun 12 09:29:13 air kernel:  <TASK>
Jun 12 09:29:13 air kernel:  ? __warn_thunk+0x2a/0x40
Jun 12 09:29:13 air kernel:  ? __warn.cold+0x8e/0xf3
Jun 12 09:29:13 air kernel:  ? __warn_thunk+0x2a/0x40
Jun 12 09:29:13 air kernel:  ? report_bug+0xe7/0x200
Jun 12 09:29:13 air kernel:  ? handle_bug+0x3c/0x80
Jun 12 09:29:13 air kernel:  ? exc_invalid_op+0x19/0xc0
Jun 12 09:29:13 air kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jun 12 09:29:13 air kernel:  ? __warn_thunk+0x2a/0x40
Jun 12 09:29:13 air kernel:  ? __warn_thunk+0x2a/0x40
Jun 12 09:29:13 air kernel:  warn_thunk_thunk+0x1a/0x30
Jun 12 09:29:13 air kernel:  getvar+0x20/0x70 [wl 0f036265dc5db6036406fdba8b694eb3f0584079]
Jun 12 09:29:13 air kernel:  ? __UNIQUE_ID_vermagic434+0x4fa07e3430b3/0x4fa07e3430b3 [wl 0f036265dc5db6036406fdba8b694eb3f0584079]
Jun 12 09:29:13 air kernel:  wl_module_init+0x17/0xa0 [wl 0f036265dc5db6036406fdba8b694eb3f0584079]
Jun 12 09:29:13 air kernel:  ? do_one_initcall+0x5b/0x310
Jun 12 09:29:13 air kernel:  ? do_init_module+0x60/0x220
Jun 12 09:29:13 air kernel:  ? idempotent_init_module+0x182/0x340
Jun 12 09:29:13 air kernel:  ? __x64_sys_finit_module+0x5e/0xb0
Jun 12 09:29:13 air kernel:  ? do_syscall_64+0x83/0x190
Jun 12 09:29:13 air kernel:  ? filemap_get_pages+0xa1/0x8d0
Jun 12 09:29:13 air kernel:  ? touch_atime+0x8a/0x320
Jun 12 09:29:13 air kernel:  ? copy_page_to_iter+0x8b/0x140
Jun 12 09:29:13 air kernel:  ? syscall_exit_to_user_mode+0x75/0x1f0
Jun 12 09:29:13 air kernel:  ? do_syscall_64+0x8f/0x190
Jun 12 09:29:13 air kernel:  ? vfs_read+0x33f/0x460
Jun 12 09:29:13 air kernel:  ? __rseq_handle_notify_resume+0x23f/0x4e0
Jun 12 09:29:13 air kernel:  ? switch_fpu_return+0x4e/0xd0
Jun 12 09:29:13 air kernel:  ? syscall_exit_to_user_mode+0x75/0x1f0
Jun 12 09:29:13 air kernel:  ? do_syscall_64+0x8f/0x190
Jun 12 09:29:13 air kernel:  ? do_syscall_64+0x8f/0x190
Jun 12 09:29:13 air kernel:  ? do_syscall_64+0x8f/0x190
Jun 12 09:29:13 air kernel:  ? exc_page_fault+0x81/0x190
Jun 12 09:29:13 air kernel:  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jun 12 09:29:13 air kernel:  </TASK>
Jun 12 09:29:13 air kernel: ---[ end trace 0000000000000000 ]---

Last edited by jonwilts (2024-06-15 18:35:15)

seth

Member

Registered: 2012-09-03

Posts: 58,145

Re: Kernel warning ("Unpatched return thunk in use") in 6.9.3 & 6.9.4-zen

Please use [code][/code] tags. Edit your post in this regard.

This is from the OOT broadcom-wl driver.
Do you also get this w/ the non-zen kernel using the non-dkms module?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

loqs

Member

Registered: 2014-03-06

Posts: 17,986

Re: Kernel warning ("Unpatched return thunk in use") in 6.9.3 & 6.9.4-zen

Related upstream commit https://github.com/torvalds/linux/commi … 3d07eed381

gromit

Package Maintainer (PM)

From: Germany

Registered: 2024-02-10

Posts: 632

Website

Re: Kernel warning ("Unpatched return thunk in use") in 6.9.3 & 6.9.4-zen

Is this only an issue with the zen kernel or also with the linux package?

Celsiuss

Member

Registered: 2020-11-05

Posts: 16

Re: Kernel warning ("Unpatched return thunk in use") in 6.9.3 & 6.9.4-zen

Hi, I am having the same logs appear on boot, using the broadcom-wl-dkms 6.30.223.271 and linux-zen 6.11.3.
In a addition to OPs error, I have also gotten this one:

kernel: memcpy: detected field-spanning write (size 182) of single field "dst" at /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c:3072 (size 0)
kernel: WARNING: CPU: 1 PID: 666 at /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c:3072 wl_inform_single_bss+0x392/0x4f0 [wl]
kernel: Modules linked in: vfat fat mt76x2u(+) mt76x2_common mt76x02_usb amd_atl intel_rapl_msr mt76_usb intel_rapl_common mt76x02_lib snd_hda_codec_realtek mt76 snd_hda_codec_generic snd_hda_codec_ca0132 snd_hda_scodec_component snd_>
kernel:  ttm drm_exec gpu_sched drm_suballoc_helper drm_buddy drm_display_helper nvme cec crc32c_intel nvme_core crc16 xhci_pci xhci_pci_renesas nvme_auth wmi
kernel: CPU: 1 UID: 0 PID: 666 Comm: wl_event_handle Tainted: P        W  OE      6.11.3-zen1-1-zen #1 1400000003000000474e5500d4154c511b9cdca1
kernel: Tainted: [P]=PROPRIETARY_MODULE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B450-F GAMING, BIOS 5404 03/18/2024
kernel: RIP: 0010:wl_inform_single_bss+0x392/0x4f0 [wl]
kernel: Code: 0f 85 dd fd ff ff 31 c9 4c 89 e6 48 c7 c2 c0 50 5b c2 48 c7 c7 28 51 5b c2 48 89 44 24 10 c6 05 54 de 15 00 01 e8 ce 04 dd c1 <0f> 0b 48 8b 44 24 10 e9 ad fd ff ff 8b 0e 41 89 8f 1a 04 00 00 42
kernel: RSP: 0018:ffffbdb981a53dc0 EFLAGS: 00010286
kernel: RAX: 0000000000000000 RBX: ffff9a4ac69f400c RCX: 0000000000000027
kernel: RDX: ffff9a51de6a1a48 RSI: 0000000000000001 RDI: ffff9a51de6a1a40
kernel: RBP: ffff9a4ac0e64000 R08: ffff9a51de5fffa8 R09: 00000000ffffdfff
kernel: R10: 0000000000000003 R11: 0000000000000002 R12: 00000000000000b6
kernel: R13: ffff9a4ac69f4014 R14: 0000000000000050 R15: ffff9a4aee0c4900
kernel: FS:  0000000000000000(0000) GS:ffff9a51de680000(0000) knlGS:0000000000000000
kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 000077ee97c26010 CR3: 00000006c8222000 CR4: 0000000000350ef0
kernel: Call Trace:
kernel:  <TASK>
kernel:  ? wl_inform_single_bss+0x392/0x4f0 [wl 1400000003000000474e5500e1dce64cfcb35906]
kernel:  ? __warn.cold+0x8e/0xf5
kernel:  ? wl_inform_single_bss+0x392/0x4f0 [wl 1400000003000000474e5500e1dce64cfcb35906]
kernel:  ? report_bug+0xe7/0x210
kernel:  ? console_unlock+0x84/0x130
kernel:  ? handle_bug+0x3c/0x80
kernel:  ? exc_invalid_op+0x19/0xc0
kernel:  ? asm_exc_invalid_op+0x1a/0x20
kernel:  ? wl_inform_single_bss+0x392/0x4f0 [wl 1400000003000000474e5500e1dce64cfcb35906]
kernel:  ? srso_return_thunk+0x5/0x5f
kernel:  ? warn_thunk_thunk+0x1a/0x30
kernel:  ? wl_notify_scan_status+0x134/0x260 [wl 1400000003000000474e5500e1dce64cfcb35906]
kernel:  ? wl_event_handler+0x7a/0x180 [wl 1400000003000000474e5500e1dce64cfcb35906]
kernel:  ? wl_cfg80211_set_tx_power+0x180/0x180 [wl 1400000003000000474e5500e1dce64cfcb35906]
kernel:  ? kthread+0xd2/0x100
kernel:  ? __pfx_kthread+0x10/0x10
kernel:  ? ret_from_fork+0x34/0x50
kernel:  ? __pfx_kthread+0x10/0x10
kernel:  ? ret_from_fork_asm+0x1a/0x30
kernel:  </TASK>

Despite the presence of these messages, the driver and wifi device seem to operate normally.

EDIT:
Using linux 6.11.4 and broadcom-wl 6.30.223.271 I get the exact same two kernel warnings.

Last edited by Celsiuss (2024-10-21 20:34:15)