Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*_memory_percent not working after update to 14.1 #3765

Open
etomm opened this issue Dec 27, 2024 · 1 comment · May be fixed by #3772
Open

*_memory_percent not working after update to 14.1 #3765

etomm opened this issue Dec 27, 2024 · 1 comment · May be fixed by #3772
Labels

Comments

@etomm
Copy link

etomm commented Dec 27, 2024

Describe the issue you are experiencing

After upgrading to 14.1 the varions addons _memory_percent sensors stopped working.

image

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

14.1

Did the problem occur after upgrading the Operating System?

No

Hardware details

RPI4 with 4GB ram

Steps to reproduce the issue

  1. Just upgrading to 14.1
  2. Adding a *_memory_percent sensor.

Anything in the Supervisor logs that might be useful for us?

NOTHING RELEVANT

Anything in the Host logs that might be useful for us?

NOTHING RELEVANT

System information

System information
Version core-2024.12.5
Installation type Home Assistant OS
Development false
Supervisor true
Docker true
User root
Virtual environment false
Python version 3.13.0
Operating system family Linux
Operating system version 6.6.62-haos-raspi
CPU architecture aarch64
Timezone Europe/Rome
Configuration directory /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.1
Stage running
Available Repositories 1497
Downloaded Repositories 29
Home Assistant Cloud
Logged In false
Reach certificate server ok
Reach authentication server ok
Reach Home Assistant Cloud ok
Home Assistant Supervisor
Host operating system Home Assistant OS 14.1
Update channel stable
Supervisor version supervisor-2024.12.0
Agent version 1.6.0
Docker version 27.2.0
Disk total 116.8 GB
Disk used 13.3 GB
Healthy true
Supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
Board rpi4-64
Supervisor API ok
Version API ok
Installed add-ons Matter Server (6.6.1), Studio Code Server (5.18.0), Samba share (12.3.2), Silicon Labs Multiprotocol (2.4.5), Mosquitto broker (6.4.1), Zigbee2MQTT (1.42.0-2), EMQX (0.7.2), Advanced SSH & Web Terminal (19.0.0), Let's Encrypt (5.2.0)
Dashboards
Dashboards 8
Resources 15
Views 26
Mode storage
Recorder
Oldest run start time December 17, 2024 at 02:10
Current run start time December 27, 2024 at 16:34
Estimated database size (MiB) 639.57 MiB
Database engine sqlite
Database version 3.45.3

Additional information

No response

@etomm etomm added the bug label Dec 27, 2024
@adekloet
Copy link

adekloet commented Jan 3, 2025

I noticed that to, I see no Additional logging or anything. All sensors which display memory % are reporting 0.

sairon added a commit that referenced this issue Jan 3, 2025
With "cgroup: Use kernel command line to disable memory cgroup" merged to RPi
kernel as 86099de [1], the device tree now contains "cgroup_disable=memory"
parameter. The parameters are parsed in the order defined in the cmdline and
with the previous order, the memory CG ends up disabled. Switching the order
fixes that and makes the order similar to what we get with standard bootloader
and parameters in cmdline.txt only.

The possible downside is that it won't be possible to override parameters from
hardcoded bootargs_hassos using cmdline.txt anymore, however, it's unlikely any
of these parameters will need to be adjusted by users.

Fixes #3765

[1] raspberrypi/linux@86099de
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants