On 1.05.26 07:51, Salvatore Bonaccorso wrote: Hello Salvatore, > I'm sorry to hear about this regression caused with the lastest urgent > security update for the kernel. Would you be able to bisect the > changes between 6.12.74 and 6.12.85 to identify which commit triggers > this specifically?
Bisecting returns this commit: $ git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [715c263119fd1b918a9fcbd8a36ea5b604a46324] iommu/amd: move wait_on_sem() out of spinlock $ git bisect log git bisect start # status: waiting for both good and bad commits # good: [444b39ef6108313e8452010b22aaba588e8fb92b] Linux 6.12.74 git bisect good 444b39ef6108313e8452010b22aaba588e8fb92b # status: waiting for bad commit, 1 good commit known # bad: [18cd79ce247a35c2938698145d1834a09b5f7777] Linux 6.12.85 git bisect bad 18cd79ce247a35c2938698145d1834a09b5f7777 # bad: [aa9ebc084505fb26dd90f4d7a249045aad152043] unshare: fix unshare_fs() handling git bisect bad aa9ebc084505fb26dd90f4d7a249045aad152043 # bad: [26c82ec5add2139e9c043d505bb413d8925426ca] wifi: rtw89: wow: add reason codes for disassociation in WoWLAN mode git bisect bad 26c82ec5add2139e9c043d505bb413d8925426ca # good: [0c74a63b797ca495e8d48645103bc2b1eb634adf] clk: qcom: gcc-x1e80100: Update the SDCC RCGs to use shared_floor_ops git bisect good 0c74a63b797ca495e8d48645103bc2b1eb634adf # good: [5f15fa06dccb6034777aaefd8ccfb2993fb9d9bf] libperf: Don't remove -g when EXTRA_CFLAGS are used git bisect good 5f15fa06dccb6034777aaefd8ccfb2993fb9d9bf # good: [1ba3a56f4854fab439e5bfe694062f9024a324ea] media: chips-media: wave5: Process ready frames when CMD_STOP sent to Encoder git bisect good 1ba3a56f4854fab439e5bfe694062f9024a324ea # good: [0fa0a82274c8471f9168b4ac338580981da86078] HID: multitouch: add eGalaxTouch EXC3188 support git bisect good 0fa0a82274c8471f9168b4ac338580981da86078 # good: [bfefacf1996f00fd2d60d99a89e5a73ae7cc9037] ASoC: fsl: imx-rpmsg: use snd_soc_find_dai_with_mutex() in probe git bisect good bfefacf1996f00fd2d60d99a89e5a73ae7cc9037 # good: [46216a48cd89d5b38fa3c1872ab10a07c369a350] wifi: rtw89: ser: enable error IMR after recovering from L1 git bisect good 46216a48cd89d5b38fa3c1872ab10a07c369a350 # good: [65bc40fea4fd6f5f07db550f4fdf4dee7f42116f] iommu/arm-smmu-v3: Improve CMDQ lock fairness and efficiency git bisect good 65bc40fea4fd6f5f07db550f4fdf4dee7f42116f # good: [b82073564373e68c6ae3a96039fae14cd002a496] wifi: libertas: fix WARNING in usb_tx_block git bisect good b82073564373e68c6ae3a96039fae14cd002a496 # bad: [faac634c2795cb4e2170e329680e7a6f766110ff] wifi: rtw89: mac: correct page number for CSI response git bisect bad faac634c2795cb4e2170e329680e7a6f766110ff I'm not sure if that's relevant: It is an older AMD Zen2 CPU: smpboot: CPU0: AMD Ryzen 5 PRO 4650G with Radeon Graphics (family: 0x17, model: 0x60, stepping: 0x1) It doesn't matter whether iommu.strict is on or off. Regards Friedemann
