On 06.06.23 04:36, Bagas Sanjaya wrote:
On Mon, Jun 05, 2023 at 01:24:25PM +0200, Malte Starostik wrote:
Hello,
chiming in here as I'm experiencing what looks like the exact same issue, also on a Lenovo Z13 notebook, also on Arch: Oops during startup in task udev-worker followed by udev-worker blocking all attempts to suspend or cleanly shutdown/reboot the machine - in fact I first noticed because the machine surprised with repeatedly running out of battery after it had supposedly been in standby but couldn't. Only then I noticed the error on boot.
bisect result: 904e28c6de083fa4834cdbd0026470ddc30676fc is the first bad commit commit 904e28c6de083fa4834cdbd0026470ddc30676fc Merge: a738688177dc 2f7f4efb9411 Author: Benjamin Tissoires benjamin.tissoires@redhat.com Date: Wed Feb 22 10:44:31 2023 +0100
Merge branch 'for-6.3/hid-bpf' into for-linusHmm, seems like bad bisect (bisected to HID-BPF which IMO isn't related to amd_sfh). Can you repeat the bisection?
Well, amd_sfh afaics apparently interacts with HID (see trace earlier in the thread), so it's not that far away. But it's a merge commit, which is possible, but doesn't happen every day. So a recheck might really be a good idea.
Anyway, tl;dr:
A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting?
[...]
BTW, I'm not sure if this really is helpful. Teaching this to upcoming kernel developers is definitely worth it, but I wonder if pushing this on all reporters might do more harm than good. I also wonder if asking them a bit more kindly might be wiser (e.g. instead of "Anyway, tl;dr:" something like "BTW, please do not top-post:" or something like that maybe).
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page.