En-Wei Wu, After a lot of trial and error, I was able to build linux-next and disable secure boot so I could run the kernel.
I confirmed my copy of linux-next already included the referenced patch. I am able to now report that it appears to solve the high CPU complaint. While there still are interrupts as Greg is reporting, I am so happy to see the CPU is idle. My solution until today has been to rmmod after boot with a root's crontab: --- $ sudo crontab -l #Ansible: kernel bug @reboot sleep 10 && rmmod ucsi_acpi --- $ grep . -r /sys/firmware/acpi/interrupts/ | awk '$2 > 0' /sys/firmware/acpi/interrupts/sci: 1247 /sys/firmware/acpi/interrupts/gpe_all: 1247 /sys/firmware/acpi/interrupts/gpe17: 1247 EN enabled unmasked $ lsmod|egrep ucsi typec_ucsi 61440 0 typec 114688 1 typec_ucsi $ sudo modprobe -a /lib/modules/6.12.0-rc5-next-20241030-custom/kernel/drivers/usb/typec/ucsi/ucsi_acpi.ko $ lsmod|egrep ucsi ucsi_acpi 12288 0 typec_ucsi 61440 1 ucsi_acpi typec 114688 1 typec_ucsi $ grep . -r /sys/firmware/acpi/interrupts/ | awk '$2 > 0' /sys/firmware/acpi/interrupts/sci: 1319 /sys/firmware/acpi/interrupts/gpe_all: 1319 /sys/firmware/acpi/interrupts/gpe17: 1319 EN enabled unmasked $ uptime 10:01:36 up 8 min, 2 users, load average: 0.08, 0.09, 0.07 $ uname -a Linux victus 6.12.0-rc5-next-20241030-custom #4 SMP PREEMPT_DYNAMIC Fri Nov 1 08:33:33 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux Thank you for your continued efforts, and Greg Kroah-Hartman <gre...@linuxfoundation.org> for the commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073538 Title: kacpi_notify high cpu on interrupt gpe17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
