Open alxchk opened 2 years ago
Having the same problem. This crash seems very critical, because rebooting is basically broken. systemd cannot shut down processes which are stuck.
Kernel version: 6.6.16-current-sunxi64
Board: Orange Pi 3 LTS
OS: Armbian
HAd it with orangepizero3 - check your /boot/armbianEnv.txt (or orangepiEnv.txt)
for
disp_mode=1920x1080p60
<-- seems not to like anything else
also please make sure that /boot/boot.cmd
and /boot/boot.scr
are aligned, (do not change boot.cmd without recompiling boot.scr) <-- you can always recompile with sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
I can't say if that was all, but it helped: also please make sure voltage is stable, and avoid having double services active for networking (like networkmanager and systemd-resolved AND ifupdown scripts + avahi-daemon)
Orange Pi os is based on an old armbian framework, kernel version from vendor is old aswell hope it help, fingers crossed
HAd it with orangepizero3 - check your
/boot/armbianEnv.txt (or orangepiEnv.txt)
fordisp_mode=1920x1080p60
<-- seems not to like anything else also please make sure that/boot/boot.cmd
and/boot/boot.scr
are aligned, (do not change boot.cmd without recompiling boot.scr) <-- you can always recompile withsudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
I can't say if that was all, but it helped: also please make sure voltage is stable, and avoid having double services active for networking (like networkmanager and systemd-resolved AND ifupdown scripts + avahi-daemon)
Orange Pi os is based on an old armbian framework, kernel version from vendor is old aswell hope it help, fingers crossed
@alexl83 Thank you, will try that!
sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
Looks like regeneration of boot script (or whatever it is) helped me, but I am not sure. Gonna monitor it more. To be honest, I can't understand how these things are related, but okay :)
sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
Looks like regeneration of boot script (or whatever it is) helped me, but I am not sure. Gonna monitor it more. To be honest, I can't understand how these things are related, but okay :)
Same for me, every time I update armbianEnv.txt I need to recompile boot.scr Else I get any kind of boot error or inability to boot I haven't understood yet if that's the supposed way or editing the .txt alone should be enough to change boot parameters and options
This happens after first cold boot every time. After that any access to cpufreq info causes hang. The kernel is 5.16 from official orange pi debian distro.