Hi, On Wed, Jul 08, 2026 at 07:20:09AM +0200, Ponali wrote: > Hi, > > > I have installed 6.12.95-1, and saw the problem still persisting on this > kernel version. > > I bisected the changes between 6.12.90 and 6.12.94 upstream and retrieved > this log: > > > git bisect start > # status: waiting for both good and bad commits > # good: [2538fbeff8a94ee2b54eb09d92209e24a1e650d4] Linux 6.12.90 > git bisect good 2538fbeff8a94ee2b54eb09d92209e24a1e650d4 > # status: waiting for bad commit, 1 good commit known > # bad: [0b8f247169e487eff2d4c2dd531bc43f7efda2cb] Linux 6.12.94 > git bisect bad 0b8f247169e487eff2d4c2dd531bc43f7efda2cb > # bad: [a244395d8c563ed1bb26c3ef708db6aeeaa08084] ixgbevf: fix > use-after-free in VEPA multicast source pruning > git bisect bad a244395d8c563ed1bb26c3ef708db6aeeaa08084 > # good: [07d3611389ba7d78b80ea360a42ce32ab2521fbc] reset: replace boolean > parameters with flags parameter > git bisect good 07d3611389ba7d78b80ea360a42ce32ab2521fbc > # bad: [8f7573f81132380c84261d88324d79dec182935a] netfilter: skip recording > stale or retransmitted INIT > git bisect bad 8f7573f81132380c84261d88324d79dec182935a > # bad: [de42f86e2cf5028a97e74c25869d1a962b13c301] slip: reject VJ receive > packets on instances with no rstate array > git bisect bad de42f86e2cf5028a97e74c25869d1a962b13c301 > # bad: [9640eceaae407dad09e5b745c29a62617626a28c] crypto: sa2ul - Fix AEAD > fallback algorithm names > git bisect bad 9640eceaae407dad09e5b745c29a62617626a28c > # bad: [3493a2305548537a16bf449f97aa279bbe1fca5c] clk: qcom: dispcc-sm4450: > Fix DSI byte clock rate setting > git bisect bad 3493a2305548537a16bf449f97aa279bbe1fca5c > # good: [e2491aa90fd951cd522765303724bbec889c4ccc] nfs/blocklayout: Fix > compilation error (`make W=1`) in bl_write_pagelist() > git bisect good e2491aa90fd951cd522765303724bbec889c4ccc > # bad: [5a04f9a36930792f6d64e28d43609e158d09b665] platform/x86: > dell-wmi-sysman: bound enumeration string aggregation > git bisect bad 5a04f9a36930792f6d64e28d43609e158d09b665 > # bad: [5fa55e5f9d2331c35b28bc47643e24ff623edbe7] tty: serial: ip22zilog: > Fix section mispatch warning > git bisect bad 5fa55e5f9d2331c35b28bc47643e24ff623edbe7 > # bad: [9bd6ec11769bad4e430d0a583bb099c8a4d189e9] platform/x86: asus-wmi: > fix screenpad brightness range > git bisect bad 9bd6ec11769bad4e430d0a583bb099c8a4d189e9 > # good: [1f3f5f945ad1643daeaa3a15585ebd25faec36f4] platform/x86: asus-wmi: > adjust screenpad power/brightness handling > git bisect good 1f3f5f945ad1643daeaa3a15585ebd25faec36f4 > # first bad commit: [9bd6ec11769bad4e430d0a583bb099c8a4d189e9] platform/x86: > asus-wmi: fix screenpad brightness range
Thanks for doing that, so at least the commit is very related to screenpad's. Now the commit was backported to not only 9.12.91 but as well 7.0.10 (from 7.1-rc1). Can you confirm if the issue is as well present with the kernel in testing and/or unstable (aka 7.0.13-1 or 7.1.3-1)? If the issue is present there as well then it's generic regression otherwise something might be missing in the 6.12.y series, in both cases we can report the issue upstream. But clarifying if 7.0.13 and in particular 7.1.3 is affected as well would be very helpful. Can you please test those? Regards, Salvatore
