Disk hibernation not working

[TheCryNex]

mother asrock j4125 installed arpl v1.0-beta10, DSM 7.1.1 buil 42962

along the way /var/log/messages spams errors every minute, because of this it does not go into hibernation... Any ideas what the problem is and how to win?

root@HomeNasSynology:~# tail -f /var/log/messages 2023-01-11T00:49:26+03:00 HomeNasSynology kernel: [ 7652.126309] <redpill/pmu_shim.c:234> Unknown 1 byte PMU command with signature hex="44" ascii="D" 2023-01-11T00:49:27+03:00 HomeNasSynology kernel: [ 7652.367854] synobios get empty ttyS current 2023-01-11T00:50:27+03:00 HomeNasSynology kernel: [ 7712.858896] <redpill/pmu_shim.c:234> Unknown 1 byte PMU command with signature hex="44" ascii="D" 2023-01-11T00:50:27+03:00 HomeNasSynology kernel: [ 7713.100187] synobios get empty ttyS current 2023-01-11T00:51:28+03:00 HomeNasSynology kernel: [ 7773.588841] <redpill/pmu_shim.c:234> Unknown 1 byte PMU command with signature hex="44" ascii="D"

[fbelavenuto]

#309

Please do a test, return to loader, go to advanced menu, change the LKM from DEV to PROD, rebuild the loader and test again.

[chenxudong2020]

me too

[chenxudong2020]

It seems that the current version has this problem, which is a major error. It has been fed back to Jumkey and other authors

[chenxudong2020]

I use https://github.com/wjz304/Redpill_CustomBuild Built. The default lkm used is redpill

[chenxudong2020]

The LKM from DEV to PROD has been compiled and modified


Visual inspection or log
You can enter commands dmesg -n 1
Turn off kernel log
Then modify：
/etc.defaults/syslog-ng/patterndb.d/scemd.conf
/etc.defaults/syslog-ng/patterndb.d/vi postgresql.conf
These two files are output to /dev/null
Or execute the following command:

sed -i 's//var/log/scemd.log//tmp/scemd.log/g' /etc.defaults/syslog-ng/patterndb.d/scemd.conf
sed -i 's//var/log/postgresql.log//tmp/postgresql.log/g' /etc.defaults/syslog-ng/patterndb.d/postgresql.conf
sed -i 's/support_led_behavior_v2="yes"/support_led_behavior_v2="no"/g' /etc.defaults/synoinfo.conf
sed -i 's/support_led_brightness_adjustment="yes"/support_led_brightness_adjustment="no"/g' /etc.defaults/synoinfo.conf

Observe whether to hibernate after setting hibernation and restarting
@TheCryNex @fbelavenuto

[TheCryNex]

#309

Please do a test, return to loader, go to advanced menu, change the LKM from DEV to PROD, rebuild the loader and test again.

Changed LKM from Dev to PROD. In "/var/log/scemd.log", "/var/log/kern.log" and "in/var/log/messages" spam the following errors:

scemd.log:

2023-01-14T11:29:53+03:00 HomeNasSynology scemd[11546]: polling_sys_current.c:38 ioctl device failed
2023-01-14T11:30:54+03:00 HomeNasSynology scemd[11546]: polling_sys_current.c:38 ioctl device failed
2023-01-14T11:31:55+03:00 HomeNasSynology scemd[11546]: polling_sys_current.c:38 ioctl device failed

messages:

2023-01-14T11:34:57+03:00 HomeNasSynology kernel: [ 759.832802] synobios get empty ttyS current
2023-01-14T11:35:58+03:00 HomeNasSynology kernel: [ 820.642297] synobios get empty ttyS current
2023-01-14T11:36:59+03:00 HomeNasSynology kernel: [ 881.453713] synobios get empty ttyS current

kern.log:

2023-01-14T11:35:58+03:00 HomeNasSynology kernel: [ 820.642297] synobios get empty ttyS current
2023-01-14T11:36:59+03:00 HomeNasSynology kernel: [ 881.453713] synobios get empty ttyS current
2023-01-14T11:38:00+03:00 HomeNasSynology kernel: [ 942.266083] synobios get empty ttyS current

I think they are not critical and they can be hidden using filters in /etc.defaults/syslog-ng/patterndb.d/
as advised by chenxudong2020

[chenxudong2020]

I tested it and still can't

[fbelavenuto]

#309