Linux 6.7+ warning: "Interrupt for port 107, but apparently not enabled"

How to file a helpful issue

Qubes OS release

R4.2

Brief summary

With Linux 6.7.x kernel prints a warning like the one below.

This was not the case on Linux 6.6

Steps to reproduce

Update to Linux 6.7, watch logs

Expected behavior

No warnings

Actual behavior

[  136.336762] ------------[ cut here ]------------
[  136.336808] Interrupt for port 107, but apparently not enabled; per-user 00000000eccfe518
[  136.336927] WARNING: CPU: 3 PID: 4873 at drivers/xen/evtchn.c:167 evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[  136.336952] Modules linked in: vfat fat snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_ctl_led snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus snd_pcm_dmaengine ledtrig_audio snd_hda_codec_hdmi snd_pci_ps snd_hda_intel snd_intel_dspcfg snd_rpl_pci_acp6x snd_intel_sdw_acpi snd_acp_pci snd_hda_codec snd_acp_legacy_common snd_hda_core intel_rapl_msr snd_pci_acp6x snd_hwdep snd_seq intel_rapl_common iwlwifi snd_seq_device hp_wmi sparse_keymap snd_pcm platform_profile snd_pci_acp5x cfg80211 pcspkr snd_rn_pci_acp3x snd_timer wmi_bmof snd_acp_config snd joydev r8169 rfkill snd_soc_acpi k10temp hp_accel soundcore snd_pci_acp3x wireless_hotkey realtek lis3lv02d i2c_piix4 fuse loop xenfs dm_thin_pool dm_persistent_data dm_bio_prison dm_crypt amdgpu crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec gpu_sched
[  136.337059]  drm_suballoc_helper ghash_clmulni_intel rtsx_pci_sdmmc sha512_ssse3 drm_buddy mmc_core xhci_pci drm_display_helper ucsi_acpi video sha256_ssse3 xhci_pci_renesas hid_multitouch sha1_ssse3 serio_raw typec_ucsi sp5100_tco xhci_hcd ccp cec wmi rtsx_pci i2c_hid_acpi typec i2c_hid xen_acpi_processor xen_privcmd xen_pciback xen_blkback xen_gntalloc xen_gntdev xen_evtchn scsi_dh_rdac scsi_dh_emc scsi_dh_alua uinput dm_multipath
[  136.337195] CPU: 3 PID: 4873 Comm: qrexec-client Not tainted 6.7.3-1.qubes.1.fc37.x86_64 #1
[  136.337206] Hardware name: HP HP ProBook 445 G7/8730, BIOS S79 Ver. 01.10.00 07/20/2022
[  136.337215] RIP: e030:evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[  136.337229] Code: ba 01 00 00 00 be 1d 00 00 00 48 8d bb 88 00 00 00 e8 0e 41 44 c0 eb b4 8b 76 20 48 89 da 48 c7 c7 70 d2 24 c0 e8 1a df 0c c0 <0f> 0b e9 61 ff ff ff 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90
[  136.337245] RSP: e02b:ffffc90048133db0 EFLAGS: 00010086
[  136.337261] RAX: 0000000000000000 RBX: ffff8881098a59c0 RCX: 0000000000000027
[  136.337269] RDX: ffff8881354e15c8 RSI: 0000000000000001 RDI: ffff8881354e15c0
[  136.337276] RBP: ffff88810cd0c740 R08: 0000000000000000 R09: ffffc90048133c48
[  136.337283] R10: 0000000000000003 R11: ffffffff82146528 R12: ffff8881067f16a4
[  136.337290] R13: ffff8881067f1760 R14: ffff88810cd0c740 R15: ffff8881067f1600
[  136.337338] FS:  00007835b8b7dd40(0000) GS:ffff8881354c0000(0000) knlGS:0000000000000000
[  136.337348] CS:  10000e030 DS: 0000 ES: 0000 CR0: 0000000080050033
[  136.337355] CR2: 00007e5ef50f8a80 CR3: 0000000105c20000 CR4: 0000000000050660
[  136.337365] Call Trace:
[  136.337373]  <TASK>
[  136.337378]  ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[  136.337391]  ? __warn+0x81/0x130
[  136.337408]  ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[  136.337423]  ? report_bug+0x171/0x1a0
[  136.337434]  ? prb_read_valid+0x1b/0x30
[  136.337446]  ? handle_bug+0x41/0x70
[  136.337456]  ? exc_invalid_op+0x17/0x70
[  136.337464]  ? asm_exc_invalid_op+0x1a/0x20
[  136.337478]  ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
[  136.337494]  __free_irq+0x114/0x2b0
[  136.337508]  free_irq+0x32/0x70
[  136.337515]  unbind_from_irqhandler+0x31/0xb0
[  136.337527]  evtchn_release+0x2b/0xa0 [xen_evtchn]
[  136.337541]  __fput+0x9a/0x2c0
[  136.337553]  __x64_sys_close+0x3d/0x80
[  136.337561]  do_syscall_64+0x63/0xe0
[  136.337571]  ? irqtime_account_irq+0x40/0xc0
[  136.337592]  ? __do_softirq+0x17a/0x2c8
[  136.337607]  ? __irq_exit_rcu+0x4b/0xc0
[  136.337618]  ? xen_pv_evtchn_do_upcall+0x54/0xb0
[  136.337626]  entry_SYSCALL_64_after_hwframe+0x6e/0x76
[  136.337637] RIP: 0033:0x7835b8d04a0a
[  136.337648] Code: 00 00 0f 05 48 3d 00 f0 ff ff 77 44 c3 0f 1f 00 48 83 ec 18 89 7c 24 0c e8 33 bc f8 ff 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 93 bc f8 ff 8b 44 24
[  136.337664] RSP: 002b:00007ffd29a76e80 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
[  136.337674] RAX: ffffffffffffffda RBX: 00005c8920e588f0 RCX: 00007835b8d04a0a
[  136.337681] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000000f
[  136.337688] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
[  136.337695] R10: 00007835b8c20468 R11: 0000000000000293 R12: 0000000000000000
[  136.337702] R13: 0000000000000000 R14: 00007ffd29a77eb4 R15: 00005c8920e572a0
[  136.337760]  </TASK>
[  136.337770] ---[ end trace 0000000000000000 ]---

Additional context

This started happening with 6.7-rc1 already, reported upstream here: https://lore.kernel.org/xen-devel/ZWf0sWey05VnpH7X@mail-itl/ Besides polluting the logs there seems to be no other negative effects.

QubesOS / qubes-issues