Rockpi5b:
Armbian 23.02.2 Jammy with Linux 5.10.110-rockchip-rk3588
The system boots from its “nvme” drive.
I have cron that executes every night. I have tried both: “reboot” and “shutdown -r now”. Some nights it re boots fine. Sometimes it makes the system unresponsive.
Turn on verbose output and try to catch error on UART. Try same thing with fresh image on card/different drive.
If it’s unresponsive there may be some kernel panic left on console.
for hard reboot - push power button little longer
Turned on logging. I set cron to reboot every 3 min. After about 10 reboots it hung. Weirdly power button reset, no matter how long I hold it wont reboot. Pulled the power and it started again. The following is what looks odd in the logs.
Looks like its an erorr trying to read data from the ES8316 audio codec chip using the ASoC (Audio System on Chip) driver. Do you think its related?
What do you think?
/var/log/dmesg
[ 11.109125] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.112614] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.115903] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.119001] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.121915] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.124901] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.127670] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.130755] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.133423] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
[ 11.136123] kernel: es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
/var/kern.log
Mar 27 12:13:05 pg-592 kernel: [ 9.147656] zram2: detected capacity change from 0 to 4031315968
Mar 27 12:13:05 pg-592 kernel: [ 9.236142] EXT4-fs (zram2): mounted filesystem without journal. Opts: discard
Mar 27 12:13:05 pg-592 kernel: [ 9.298587] EXT4-fs (zram1): mounted filesystem without journal. Opts: discard
Mar 27 12:13:05 pg-592 kernel: [ 11.109125] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Mar 27 12:13:05 pg-592 kernel: [ 11.112614] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Mar 27 12:13:05 pg-592 kernel: [ 11.115903] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Mar 27 12:13:05 pg-592 kernel: [ 11.119001] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Mar 27 12:13:05 pg-592 kernel: [ 11.121915] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Mar 27 12:13:05 pg-592 kernel: [ 11.124901] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Mar 27 12:13:05 pg-592 kernel: [ 11.127670] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Mar 27 12:13:05 pg-592 kernel: [ 11.130755] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Mar 27 12:13:05 pg-592 kernel: [ 11.133423] es8316 7-0011: ASoC: error at soc_component_read_no_lock on es8316.7-0011: -6
Its indeed an issue… I get these a lot everytime I opt by doing shutdown other than reboot and most of times it requires me do a power cut… nobody seems to talk about this much but I doubt I am the only one with this issue… a fix seems to be non-existent so far.
It happens on other images too not just on armbian.
It wasnt happening on default armbian 22.0 but on 23.0 is… I started to have the same issue on openfyde and its hard to figure why
Well that didn’t work. But I think this did. I recompiled the kernel editing es8316 in rk3588-rock-5b.dts. Give it a try if you don’t need the audio. place in /boot/dtb/rockchip. backup before you try it.
I ran it overnight. rebooting every 5 min via cron. crashed again. So it is not the audio. I don’t really have any other logging that looks helpful so I’m going to try dietpi next or ubunto.
Both ubuntu and dietpi both hang on reboot too. I have also tried multiple nmve cards and a 5b 4GB and a 5B8GB board. All the same behavior. So at this point I’m kind a stumped. Maybe its a firmware issue?
Reboot/hang is pretty random. It often takes 1 time to fail and hang. Sometimes 10 + . Any idea would be appreciated. I was planning on using these on an iot edge project but it’s now a no go if I can’t get a reliable reboot.
Set up a cron (every 2 min or whatever) : */2 * * * * /usr/sbin/reboot
See if you get the same problem.