Mainlinux : Works but boards stops responding after a while

Other OS Support Other OS-related topics
1

I have managed to run mainline linux with the instructions provided. It boots and shows up in adb devices but after some idling, the board seems to die and not respond any further.

I can see the following in dmesg:

[  921.818215] Filesystems sync: 0.012 seconds
[  921.836997] Freezing user space processes
[  921.843958] Freezing user space processes completed (elapsed 0.002 seconds)
[  921.851162] OOM killer disabled.
[  921.854505] Freezing remaining freezable tasks
[  921.860444] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[  921.868115] printk: Suspending console(s) (use no_console_suspend to debug)

Kernel version:

Linux rubikpi 7.0.0-00006-g7398c49933ff-dirty #3 SMP PREEMPT Fri May 22 17:05:15 IST 2026 aarch64 GNU/Linux

I am trying with usbcore.autosuspend=-1 mem_sleep_default=s2idle commandline and checking the issue crops up or not

2

It didn’t help. After few reboots, the rootfs cannot be mounted and failing to boot.

gcc-sc7280 100000.clock-controller: sync_state() pending due to a84000.i2c
qnoc-sc7280 1500000.interconnect: sync_state() pending due to a90000.spi
qnoc-sc7280 9100000.interconnect: sync_state() pending due to a90000.spi
qnoc-sc7280 interconnect: sync_state() pending due to a90000.spi
qcom-rpmhpd 18200000.rsc:power-controller: sync_state() pending due to a90000.spi
gcc-sc7280 100000.clock-controller: sync_state() pending due to a90000.spi
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  LABEL=writable does not exist.  Dropping to a shell!


BusyBox v1.37.0 (Debian 1:1.37.0-6+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)
3

This is a known issue and has been scheduled for development. It is expected to be fixed and integrated into the new software release.

4

Could you share any WIP patches to be tested. Would be helpful

5

Could you please share your specific use case?
Would you like the device to stay active without entering sleep mode?

6

I think I have disabled all sleep/suspend modes. But sometimes the board corrupts the rootfs and initramfs and refuses to boot again (which was booting earlier).

7

If you would like the device to stay active, you can try using the following command:
echo stay > /sys/power/wake_lock

8

systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target Is what I am using now.

9

Okay, thank you for your reply.