Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Solved: 9.3.2: dmesg full with "mempolicy: Request to set policy to 3 ignored" messages
#1
Star 
Since installing Moode 9.3.2 the dmesg log is continually spammed with these messages: 
```
[Fri Apr 18 17:20:31 2025] mempolicy: Request to set policy to 5 ignored
[Fri Apr 18 17:20:31 2025] mempolicy: Request to set policy to 3 ignored
[Fri Apr 18 17:20:31 2025] mempolicy: Request to set policy to 5 ignored
[Fri Apr 18 17:20:31 2025] mempolicy: Request to set policy to 3 ignored
[Fri Apr 18 17:20:31 2025] mempolicy: Request to set policy to 5 ignored
[Fri Apr 18 17:20:31 2025] mempolicy: Request to set policy to 3 ignored
[Fri Apr 18 17:20:31 2025] mempolicy: Request to set policy to 5 ignored
[Fri Apr 18 17:20:31 2025] mempolicy: Request to set policy to 3 ignored
[Fri Apr 18 17:20:37 2025] mempolicy: Request to set policy to 5 ignored
[Fri Apr 18 17:20:37 2025] mempolicy: Request to set policy to 3 ignored
[Fri Apr 18 17:20:37 2025] mempolicy: Request to set policy to 5 ignored
[Fri Apr 18 17:20:37 2025] mempolicy: Request to set policy to 3 ignored
[Fri Apr 18 17:20:37 2025] mempolicy: Request to set policy to 5 ignored
[Fri Apr 18 17:20:37 2025] mempolicy: Request to set policy to 3 ignored
[Fri Apr 18 17:20:38 2025] mempolicy: Request to set policy to 5 ignored
[Fri Apr 18 17:20:38 2025] mempolicy: Request to set policy to 3 ignored

```
I know it's not a Moode problem, it's a Raspbian problem with kernel 6.12, see for instance this conversation: https://forums.raspberrypi.com/viewtopic.php?t=386126.

I'm just signaling it, and I suppose we will have to live with it until it's solved in Raspbian.
Reply
#2
libnuma1 was the issue.
I fixed it on my moOde instance by doing: sudo apt install libnuma1
This installed a newer version of the lib where the issue is fixed.
Reply
#3
Here's the version that ships with r932

Code:
pi@moode9:~ $ dpkg -l | grep libnuma1

ii  libnuma1:arm64                       2.0.18-1~rpt1                          arm64        Libraries for controlling NUMA policy
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#4
2.0.18-1 is indeed the version that works. However, if you do an inplace update, this one wasn't upgraded I believe, and this is when you've the issue.
Reply
#5
Correct. The in-place update only does the kernel and the list of moode packages below.

Code:
# Part 2: List of package updates (cumulative)
PKG_UPDATES=(
moode-player=9.3.3-1moode1
alsa-cdsp=1.2.0-2moode1
mpd=0.24.3-1moode1
mpc=0.35-1moode1
bluez-alsa-utils=4.2.0-2moode1
libasound2-plugin-bluez=4.2.0-2moode1
camilladsp=3.0.0-1moode1
camillagui=3.0.2-1moode1
mpd2cdspvolume=2.0.0-1moode2
python3-camilladsp-plot=3.0.0-1moode1
python3-camilladsp=3.0.0-1moode1
shairport-sync=4.3.6-1moode1
shairport-sync-metadata-reader=1.0.2~git20250413.9caf251-1moode1
log2ram=1.7.2
librespot=0.6.0-1moode1
libnpupnp13=6.2.0-1moode1
libupnpp16=0.26.7-1moode1
pleezer=0.16.0-1moode1
upmpdcli=1.9.0-1moode1
upmpdcli-qobuz=1.9.0-1moode1
upmpdcli-tidal=1.9.0-1moode1
)

There used to be some additional firmware- packages but those were removed to avoid any of them possibly failing and causing the entire update to be cancelled.

Since moode packages are "apt-mark hold" its possible to "apt update && apt -y upgrade" a system and not break anything unless the upgrade contains a new Kernel or version of PHP. A kernel upgrade would cause the aloop and pcm1794a drivers to revert to stock and thus not support 384K rate. A new version of PHP always has its version string as part of its /etc dir and so it causes breakage in moode.

Code:
pi@moode9:~ $ cat /etc/moode-apt-mark.conf
# List of packages which should be frozen with apt-mark
alsa-cdsp
alsacap
# bluez
bluez-alsa-utils
# boss2-oled-p3
# bs2b-ladspa
camilladsp
camillagui
caps
# v126 chromium package group
chromium-browser
chromium-browser-l10n
chromium-codecs-ffmpeg-extra
# v130 chromium package group
chromium
# chromium-browser
chromium-common
chromium-sandbox
rpi-chromium-mods
#
libasound2-plugin-bluez
librespot
mediainfo
minidlna
moode-player
mpd
mpd2cdspvolume
pleezer
python3-camilladsp
python3-camilladsp-plot
python3-libupnpp
python3-camilladsp
python3-camilladsp-plot
raspberrypi-kernel
raspberrypi-bootloader
shairport-sync
shairport-sync-metadata-reader
squeezelite
trx
udisks
udisks-glue
upmpdcli
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#6
(04-18-2025, 04:31 PM)ils1974 Wrote: libnuma1 was the issue.
I fixed it on my moOde instance by doing:  sudo apt install libnuma1
This installed a newer version of the lib where the issue is fixed.

I can confirm that
Code:
sudo apt install libnuma1
fixes the issue, thanks!
Reply


Forum Jump: