high CPU usage

[luka6000]

I'm not using audio on hass. At all. How can I disable audio container? It is using a lot of CPU

ha > audio info audio: application: [] card: [] input: [] output:

• applications: [] card: null default: true description: Dummy Output index: 0 mute: false name: auto_null volume: 1 host: 172.30.32.4 update_available: false version: 2021.02.1 version_latest: 2021.02.1

It is the most CPU hungry process of all containers

PID USER PR NI VIRT RES %CPU %MEM TIME+ S COMMAND
1169 root 20 0 87.8m 39.3m 0.0 2.1 24:01.66 S python3 -m supervisor
1760 root 20 0 789.6m 17.6m 0.7 0.9 9:04.55 S coredns -conf /etc/corefile
2499 root 9 -11 77.2m 4.7m 8.7 0.2 594:06.99 S pulseaudio --system -vvv --disallow-exit --exit-idle-time=-+ 2761 root 20 0 0.7m 0.0m 0.0 0.0 3:10.00 S mdns-repeater -f eth0 hassio
3163 root 20 0 16.5m 15.8m 0.7 0.8 4:52.70 S mosquitto -c /etc/mosquitto.conf
3875 root 20 0 265.7m 67.9m 9.3 3.6 399:23.11 S deCONZ -platform xcb --auto-connect=1 --dbg-info=1 --dbg-ap+ 2936 root 20 0 430.9m 270.0m 9.3 14.1 41:33.77 S python3 -m homeassistant --config /config

Every second it takes 100% CPU core for a short while. It's 10x the actual homeassistant core process. And I don't even need it. So, how to disable audio support on hass?

[cogneato]

Can you include your system details? Is this HA OS? Debian?

[frenck]

(please post the output of ha info as that helps us reproducing). Thanks 👍

[luka6000]

This is hass os

ha > info arch: armv7 channel: stable docker: 19.03.13 features:

• reboot
• shutdown
• services
• network
• hostname
• hassos hassos: "5.12" homeassistant: 2021.3.4 hostname: homeassistant logging: info machine: raspberrypi4 operating_system: Home Assistant OS 5.12 state: running supervisor: 2021.03.6 supported: true supported_arch:
• armv7
• armhf timezone: Europe/Warsaw

[radicalmachine]

I too, am suffering with this issue. Running supervised in docker on a Pi4. Please advise what logs would be helpful in troubleshooting

output of 'docker stats'

CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 2c019c589295 hassio_audio 20.79% 0B / 0B 0.00% 59.9kB / 690B 0B / 57.3kB 9 45ba8d058a82 addon_core_configurator 0.02% 0B / 0B 0.00% 2.67MB / 1.29MB 15.2MB / 24.6kB 4 a1f72d777087 addon_core_duckdns 0.00% 0B / 0B 0.00% 2.82MB / 131kB 8.21MB / 20.5kB 7 d02c7c16fe31 hassio_multicast 0.00% 0B / 0B 0.00% 0B / 0B 4.15MB / 16.4kB 4 1c6b8a3ea3c8 hassio_cli 0.00% 0B / 0B 0.00% 2.43MB / 494B 152kB / 0B 5 43486b98bc20 hassio_dns 0.03% 0B / 0B 0.00% 2.79MB / 710kB 18.5MB / 20.5kB 13 3d81d13d6291 homeassistant 1.70% 0B / 0B 0.00% 0B / 0B 28.7kB / 149MB 17 f77cc835e228 hassio_observer 0.00% 0B / 0B 0.00% 2.57MB / 36.1kB 11.9MB / 4.1kB 8 81f23424dd4c hassio_supervisor 0.00% 0B / 0B 0.00% 5.81MB / 4.57MB 145MB / 381kB 13

output of 'ha info'

$ ha info arch: armv7 channel: stable docker: 20.10.7 features:

• reboot
• shutdown
• services
• network
• hostname
• timedate hassos: null homeassistant: 2021.6.6 hostname: raspberrypi logging: info machine: raspberrypi4 operating_system: Raspbian GNU/Linux 10 (buster) state: running supervisor: 2021.06.6 supported: false supported_arch:
• armv7
• armhf timezone: Europe/London

[soeffi]

Did anyone solve this yet?

I have the same problem on a fresh hass os install. (Home Assistant 2022.12.8 Supervisor 2022.11.2 Operating System 9.4 Frontend 20221213.1 - latest)

Any means to disable the audio container for now?

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[robotpandarocket]

Still happens to me on 2024.12.4 and OS 14.0

[agners]

@robotpandarocket can you share details about your system? E.g. the output of ha info.

There have been some PRs which do address high CPU usage at least in certain situations.

[robotpandarocket]

Sure. I'm running HA inside of Proxmox on a Trigkey Mini PC with a 8th Gen Intel 8109U. Sporadically (once a week or so), the cpu usage spikes from an average of 5-8% to 60+% and will not come back down with a regular Hassio restart. Instead, I need to restart the VM. I dug into the logs a while back, it's pulse audio related by the looks of it (I don't have the logs handy right now, but will post next time it spikes again)

➜ ~ ha info
arch: amd64 channel: stable docker: 27.2.0 features:

• reboot
• shutdown
• services
• network
• hostname
• timedate
• os_agent
• haos
• resolved
• journal
• disk
• mount hassos: "14.1" homeassistant: 2024.12.4 hostname: homeassistant logging: info machine: qemux86-64 operating_system: Home Assistant OS 14.1 state: running supervisor: 2024.12.0 supported: true supported_arch:
• amd64
• i386 timezone: Africa/Johannesburg

[Egorkat]

Same issue here, once in a week hassio_audio container starts to consume CPU. Only VM restart helps. Here are some logs and stats:

audio_2025-02-14T13-12-53.020Z.log

[agners]

I do have a couple of machines using HAOS on my test Proxmox instance on a Intel NUC10i5FNH. Do you have Audio hardware forwarded to the machine? How did you setup the virtual machine?

This is my hardware configuration:

[robotpandarocket]

I used to have the audio device forwarded (which had the same high CPU usage issues), but for the last year I've been

using an Anker Powerconf S330 via usb.

[Egorkat]

Indeed, I'm using USB audio device.

[Egorkat]

Any hints to troubleshoot? It happens each Friday almost at same time... HA restart doesn't help, only full VM restart

[agners]

Hm, I wonder if this is more USB related than anything else.

Has the Proxmox/host logs anything related to USB in its log maybe (e.g. kernel logs/dmesg)?

There was just this week a new release of the audio plug-in with Pulseaudio 17.0, see https://github.com/home-assistant/plugin-audio/releases/tag/2025.02.0.

The plug-in is currently on the beta channel. However, if you are using stable channel, you can manually only update that plug-in:

ha audio info
ha audio update --version 2025.02.0

[Egorkat]

did the update, will see this Friday :-) checked ProxMox logs, but nothing suspicious there..

[robotpandarocket]

Still happens

[Egorkat]

yes, happened again last Friday, also around 14. I wonder what kind of scheduled tasks can be causing this...

[agners]

I've setup an audio device in my Proxmox installation, let's see if I get the same behavior.

@robotpandarocket does this happen on Friday around 2pm for you too?

@Egorkat anything in the host or audio logs of the Home Assistant VM or in the system logs of the Proxmox server itself in that timeframe?

[robotpandarocket]

Thank you @agners, appreciate you looking into it. I completely overlooked checking the instance times, as they felt random. Looking at a few in Jan/Feb, it's a little all over the show, but it does seem like a scheduled process. Every 6/7 days at 15/45. I'll take a look what's scheduled.

1/1 14:45 1/8 01:45 1/14 12:15 1/20 22:45 1/27 10:45 2/3 01:15 2/12 02:45 2/18 12:15

[agners]

In my test Proxmox installation I noticed today high CPU usage. Checking top on the Home Assistant operating system shell (via port 22222) I've noticed that ksoftirqd/1 uses most of the CPU (~97%), and around 3% Pulseaudio. It seems to be audio related.

# cat /proc/interrupts
           CPU0       CPU1
...
 37:          0 2272525371  PCI-MSIX-0000:07:1b.0   0-edge      xhci_hcd

It seems that there are lots of xhci_hcd interrupts generated.

Using watch -n1 ... shows that pretty much exactly 50'000 interrupts are processed per second. The audio plug-in logs show underruns:

Apr 17 19:42:51 ha-virt-proxmox-dev hassio_audio[526]: I: [alsa-sink-USB Audio] alsa-sink.c: Underrun!
Apr 17 19:43:21 ha-virt-proxmox-dev hassio_audio[526]: I: [alsa-sink-USB Audio] alsa-sink.c: Underrun!
Apr 17 19:43:21 ha-virt-proxmox-dev hassio_audio[526]: I: [alsa-sink-USB Audio] alsa-sink.c: Underrun!
Apr 17 19:46:51 ha-virt-proxmox-dev hassio_audio[526]: I: [alsa-sink-USB Audio] alsa-sink.c: Underrun!
Apr 17 19:49:51 ha-virt-proxmox-dev hassio_audio[526]: I: [alsa-sink-USB Audio] alsa-sink.c: Underrun!
Apr 17 19:49:51 ha-virt-proxmox-dev hassio_audio[526]: I: [alsa-sink-USB Audio] alsa-sink.c: Underrun!
Apr 17 19:49:51 ha-virt-proxmox-dev hassio_audio[526]: I: [alsa-sink-USB Audio] alsa-sink.c: Underrun!
Apr 17 19:49:52 ha-virt-proxmox-dev hassio_audio[526]: I: [alsa-sink-USB Audio] alsa-sink.c: Underrun!

Proxmox host kernel version:

root@pve:~# uname -a
Linux pve 6.8.12-9-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-9 (2025-03-16T19:18Z) x86_64 GNU/Linux

This is using HAOS 15.2.dev20250410. Nothing relevant in dmesg. Restarting the audio plug-in using ha audio restart seems not to help, CPU spikes up to 100% shortly after.

It looks like a kernel issue (KVM) related to the USB forwarding.

[agners]

It seems that the original post was about Raspberry Pi 4, and CPU spikes even without using audio. There were no reports lately for that particular configuration, so I'd consider this issue closed.

@luka6000 (or someone else with a similar hardware setup as OP), in case you still see this on the Raspberry Pi 4, please report back.

As for Proxmox related CPU spikes, let's continue the conversation in the OS specific issue at https://github.com/home-assistant/operating-system/issues/4034.

If someone sees high CPU usage on other platforms the Raspberry Pi 4 or OVA with Proxmox, please open a new issue so this can be tracked separately.