AdnanHodzic / AdnanHodzic/auto-cpufreq

Kernel Panic when starting auto-cpufreq & changing governor with Ubuntu's 6.17 HWE kernel

Abierto
#940 3 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
7.8k
Forks
357
Merge medio
3 d 8 h
PR fusionados (30 d)
14

Descripción

#### Before submitting an issue, it is strongly recommended to use the **[auto-cpufreq-genAI-chatbot](https://foolcontrol.org/?p=4903)** to get an immediate answer to your question.

### Have you tried?
Yes

- [Searching through existing/closed issues](https://github.com/AdnanHodzic/auto-cpufreq/issues) to see if your bug has already been already submitted?
Yes

- If installation failed with [auto-cpufreq-installer](https://github.com/AdnanHodzic/auto-cpufreq/#auto-cpufreq-installer),have you tried installing auto-cpufreq using [Snap package](https://github.com/AdnanHodzic/auto-cpufreq/#snap-store)?
N/A

- Have you tried [configuring auto-cpufreq](https://github.com/AdnanHodzic/auto-cpufreq/#configuring-auto-cpufreq)?
N/A

- Have you tried suggestions in [troubleshooting section](https://github.com/AdnanHodzic/auto-cpufreq#troubleshooting)?
Yes

### Error output:

Image

---

### System information:

Add/paste output of:

```

Using settings defined in /etc/auto-cpufreq.conf file
conservation mode is on

-------------------------------------------------------------------------------

Linux distro: Ubuntu 24.04 Noble Numbat
Linux kernel: 6.17.0-19-generic
Processor: AMD Ryzen 5 7535HS with Radeon Graphics
Cores: 12
Architecture: x86_64
Driver: amd-pstate-epp

Using settings defined in /etc/auto-cpufreq.conf

------------------------------ Current CPU stats ------------------------------

CPU max frequency: 3301 MHz
CPU min frequency: 416 MHz

Core Usage Temperature Frequency
CPU0 2.0% 48 °C 3267 MHz
CPU1 1.0% 48 °C 416 MHz
CPU2 1.0% 48 °C 416 MHz
CPU3 1.0% 48 °C 3268 MHz
CPU4 4.0% 48 °C 3269 MHz
CPU5 5.0% 48 °C 3265 MHz
CPU6 5.1% 48 °C 416 MHz
CPU7 0.0% 48 °C 416 MHz
CPU8 13.3% 48 °C 3267 MHz
CPU9 5.1% 48 °C 3266 MHz
CPU10 2.0% 48 °C 3269 MHz
CPU11 0.0% 48 °C 3267 MHz

auto-cpufreq version: 3.0.0

Python: 3.12.3
psutil package: 6.0.0
platform package: 1.0.8
click package: 8.1.7
distro package: 1.9.0

Computer type: Notebook
Battery is: charging

auto-cpufreq system resource consumption:
cpu usage: 0.0 %
memory use: 0.31 %

Total CPU usage: 1.6 %
Total system load: 0.46
Average temp. of all cores: 36.00 °C

Currently using: performance governor
Currently turbo boost is: off

-------------------------------------------------------------------------------
```

Also please be descriptive about the issue you're reporting, i.e: what you tried & what's the expected behaviour.

---
The kernel panic (when starting auto-cpufreq & changing governor) usually happens with Ubuntu's HWE kernel 6.17.0-20-generic (latest for Ubuntu Cinnamon 24.04 at present).
It doesn't happen every single time, and exact conditions still need to be determined, but sometimes e.g. when I click auto-cpufreq icon on Cinnamon panel - Kernel panic happens IMMEDIATELY auto-cpufreq icon click.
Therefore I believe its directly auto-cpufreq related.

Another time Kernel panic happened immediately after clicking to change governor in the GUI.
I know approximate time of the latest kernel panic, there doesn't seem to be anything relevant going on around that time in any log.

I **never** observed Kernel panic unless I do smth with auto-cpufreq.

Currently trying previous kernel 6.17.0-19 (don't know yet whether kernel panic is reproducible or not with it).

FS: BTRFS+LUKS/NVME.
Ubuntu Cinnamon 24.04.4.
Thank you.

================================
HWE installed packages:
```
linux-generic-hwe-24.04/now 6.17.0-20.20~24.04.1 amd64 [installed,upgradable to: 6.17.0-22.22~24.04.1]
linux-headers-generic-hwe-24.04/now 6.17.0-20.20~24.04.1 amd64 [installed,upgradable to: 6.17.0-22.22~24.04.1]
linux-hwe-6.14-headers-6.14.0-36/noble-updates,noble-updates,noble-security,noble-security,now 6.14.0-36.36~24.04.1 all [installed,automatic]
linux-hwe-6.14-headers-6.14.0-37/noble-updates,noble-updates,noble-security,noble-security,now 6.14.0-37.37~24.04.1 all [installed,automatic]
linux-hwe-6.17-headers-6.17.0-19/noble-updates,noble-updates,noble-security,noble-security,now 6.17.0-19.19~24.04.2 all [installed,automatic]
linux-hwe-6.17-headers-6.17.0-20/noble-updates,noble-updates,noble-security,noble-security,now 6.17.0-20.20~24.04.1 all [installed,automatic]
linux-hwe-6.17-tools-6.17.0-19/noble-updates,noble-security,now 6.17.0-19.19~24.04.2 amd64 [installed,automatic]
linux-hwe-6.17-tools-6.17.0-20/noble-updates,noble-security,now 6.17.0-20.20~24.04.1 amd64 [installed,automatic]
linux-image-generic-hwe-24.04/now 6.17.0-20.20~24.04.1 amd64 [installed,upgradable to: 6.17.0-22.22~24.04.1]
systemd-hwe-hwdb/noble-updates,noble-updates,now 255.1.7 all [installed]
```

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

No source file or test is named. First try to reproduce the panic on Ubuntu Cinnamon 24.04.4 with Ubuntu's 6.17.0-20 HWE kernel by starting auto-cpufreq and changing the governor through the Cinnamon panel or GUI, then compare with 6.17.0-19. Done means isolating reliable reproduction conditions and documenting whether the trigger is auto-cpufreq or the kernel interaction.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
linux, python
Área
operating-systems, performance
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Necesita aclaración
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.