Public bug reported:
I believe it might have something to do with pidgin notifications
$ lsb_release -rd
Description:Ubuntu 13.10
Release:13.10
$ apt-cache policy unity-services
unity-services:
Installed: 7.1.2+13.10.20131014.1-0ubuntu1
Candidate: 7.1.2+13.10.20131014.1-0ubuntu1
Public bug reported:
Picked up a HP laptop during July sales, and found the CPU soars to 80+ with
kacpi_notify hitting GPE17.
I would like some help finding the cause. Google searches were vague about
masking the interrupt which did NOT help. If we can find what is calling the
interrupts mayb
En-Wei Wu,
Happy to do additional debugging if you could guide me.
I noticed the following in dmesg:
[5.860144] ucsi_acpi USBC000:00: failed to reset PPM!
[5.860150] ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
If I "sudo rmmod ucsi_acpi", the CPU load issue resolves, but
Some additional data I thought might be helpful:
$ sudo su -
# echo l > /proc/sysrq-trigger
---/var/log/syslog---
2024-07-19T12:45:33.815231-04:00 victus kernel: NMI backtrace for cpu 11
2024-07-19T12:45:33.815232-04:00 victus kernel: CPU: 11 PID: 271 Comm:
kworker/11:3 Not tainted 6.8.0-38-gene
perf data file
** Attachment added: "perf data file"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+attachment/5798650/+files/perf.data
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
En-Wei,
First, I dropped to root
$ sudo su -
I was unable to echo to /sys/kernel/debug
# echo 'file ucsi.c +p' > /sys/kernel/debug/dynamic_debug/control
-bash: /sys/kernel/debug/dynamic_debug/control: Operation not permitted
so I tried /proc instead:
# cat /proc/dynamic_debug/control|egrep uc
lshw_json.txt
** Attachment added: "lshw_json.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+attachment/5801947/+files/lshw_json.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
AceLan Kao,
$ sudo fwupdmgr refresh
Metadata is up to date; use --force to refresh again.
$ sudo fwupdmgr get-updates
Devices with no available firmware updates:
• ELAN07FB:00 04F3:321A
• HP Wide Vision HD Camera
• System Firmware
• WD PC SN740 SDDPNQD-512G-2006
Devices with the latest avail
dmidecode.txt
** Attachment added: "dmidecode.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+attachment/5801948/+files/dmidecode.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
AceLan Kao,
First, I added "noble-proposed" to /etc/apt/sources.list.d/ubuntu.sources:
$ sudo sed -i '/^Suites/ s/$/ noble-proposed/'
/etc/apt/sources.list.d/ubuntu.sources
then I ran, apt update:
$ sudo apt update
Then I was able to install the 6.8.0-40 kernel:
$ sudo apt instal
AceLan Kao,
First, I downloaded the image and modules:
$ wget
https://kernel.ubuntu.com/mainline/v6.11-rc1/amd64/linux-image-unsigned-6.11.0-061100rc1-generic_6.11.0-061100rc1.202407281809_amd64.deb
$ wget
https://kernel.ubuntu.com/mainline/v6.11-rc1/amd64/linux-modules-6.11.0-061100rc1-generic
AceLan Kao,
Going the HP support route we all know will be extremely painful, if, I
can convince their support to forward my query along to the right people.
Is there no method to debug or expose the reason for the failed PPM init and/or
what the GPE17 triggers are called from?
I am assumin
AceLan Kao,
In summary, I did not see any improvement, but perhaps some of the extended
debugging is helpful.
I did the following steps over the course of my work day, so I might have
missed a step, but here is the order of what I did:
I added the ubuntu kernel repo:
$ sudo add-apt-repository p
20240808_victus-syslog.txt
** Attachment added: "20240808_victus-syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+attachment/5803967/+files/20240808_victus-syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
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 inte
@anaf
The fix has been submitted and will be in the next kernel release 6.13
reference my comments here:
https://bugzilla.kernel.org/show_bug.cgi?id=219055#c16
** Bug watch added: Linux Kernel Bug Tracker #219055
https://bugzilla.kernel.org/show_bug.cgi?id=219055
--
You received this bu
16 matches
Mail list logo
