Experiencing freezing and rebooting issues when starting the container.

[TTT-TYL]

Test device: OnePlus 15, kernel version 6.12. Encountering freezing and rebooting when starting the container, which prevents the container from starting.

[ravindu644]

hey, to know what's wrong, please take these steps:

1. reproduce the issue (let the freeze and panic happen - then boot back to the system)
2. dump the last kernel message - this should contain all the details regarding your issue:

cp /proc/last_kmsg /sdcard/last_kmsg.txt <- run this inside a termux root shell

3. upload it here.

[ravindu644]

Okay. Install the latest APK from the CI:

https://github.com/ravindu644/Droidspaces-OSS/actions/runs/23694407235/artifacts/6161242588

Generate the bug report after your issue happened (even after reboot after a panic)

Drop the bugreport tarball to here.

[TTT-TYL]

There is no last_kmsg file in my proc directory. I can only generate a bug report to submit to you. Thank you.

Droidspaces-bugreport_2026-03-29_08-06-18.tar.gz

[ravindu644]

There is no last_kmsg file in my proc directory. I can only generate a bug report to submit to you. Thank you.

Droidspaces-bugreport_2026-03-29_08-06-18.tar.gz

Hmm, it is hard to judge what exactly caused your panic.

I guess modern kernel stores panic logs under /sys/fs/pstore/..

Can you check that path and send everything there inside a ZIP, AFTER the panic happened ?

[ravindu644]

I also added the ability to get pstore logs. please check this one out:

https://github.com/ravindu644/Droidspaces-OSS/actions/runs/23703042943/artifacts/6164019628

[TTT-TYL]

Hello, I have configured CONFIG_PSTORE=y in my kernel, but the "/sys/fs/pstore/" directory is still empty.

[TTT-TYL]

After the first container startup crashes and restarts, the second startup does not crash and restart, but the container still cannot start. The logs are as follows.
Starting start operation...
Command: /data/local/Droidspaces/bin/droidspaces --config='/data/local/Droidspaces/Containers/ubuntu/container.config' start

[-] Container name is mandatory (--name).
[-] No rootfs target specified (requires -r or -i).

Command failed (exit code: 1)

Operation failed!

[MengHanLOVE1027]

I have the same problem

Droidspaces-bugreport_2026-03-29_16-27-54.tar.gz

[adk23333]

I guess modern kernel stores panic logs under /sys/fs/pstore/..

My device is the Redmi K90 Pro Max (myron). My attempt was to add configurations to the kernel, such as enabling cgroup devices as shown in this workflow, which allowed the device to boot normally and function properly.

However, after additionally enabling PIDS as demonstrated in this subsequent workflow, the kernel started crashing repeatedly and failed to boot.

The pmsg-ramoops-0 log file I retrieved is as follows:

pmsg-ramoops-0.txt

P.S.: In the 6.12 kernel, the file paths of several patches have changed, so the patch files may need to be updated accordingly.

[ravindu644]

After the first container startup crashes and restarts, the second startup does not crash and restart, but the container still cannot start. The logs are as follows. Starting start operation... Command: /data/local/Droidspaces/bin/droidspaces --config='/data/local/Droidspaces/Containers/ubuntu/container.config' start

[-] Container name is mandatory (--name). [-] No rootfs target specified (requires -r or -i).

Command failed (exit code: 1)

Operation failed!

okay - this happens due to a corrupted container.config generated during your crash :(

you can re-install the container again to fix this issue.

[ravindu644]

I have the same problem

Droidspaces-bugreport_2026-03-29_16-27-54.tar.gz

it seems like your phone crashes when mounting the rootfs.img, which is strange:

[2026-03-29 08:18:29.315] [main] Image checked and repaired successfully.

can you try without using the rootfs.img ?

also, your log lacks last_kmesg or pstore logs too.. so, it's hard to exactly tell what's going on..

but, I have an idea..!

[ravindu644]

@TTT-TYL @MengHanLOVE1027

Hey, this is the plan:

First of all, we need to access the live dmesg when starting the container using ADB shell. Whenever a kernel panic happens, the logs will show exactly what caused it and print all the details we need to debug.

If you have Linux, you can easily pipe the dmesg output to a text file and attach it here:

# Clear the kernel message buffer so we won’t see any log noise
adb shell "su -c 'dmesg -C'"

# Start watching dmesg in real time while saving its output to a file
adb shell "su -c 'dmesg -w'" | tee kernel_logs.txt

This will tell us exactly what's causing the panics :)

[ravindu644]

It seems like building GKI kernels by nuking CRC checks and patching KABI is unreliable on modern 6.x+ kernels.

The recommended approach is to compile as many LKMs as possible and distribute them across the vendor_boot, vendor_dlkm, and system_dlkm partitions. This fixes all the issues AND doesn’t require any patches at all, like I did with my GKI kernel:

https://github.com/ravindu644/android_kernel_a166p

But it’s very complicated, and not all manufacturers release the source code for their out-of-tree modules.

[ravindu644]

PIDS

Okay, do not enable it. it's not required for Droidspaces anyways

[MengHanLOVE1027]

@TTT-TYL @MengHanLOVE1027

Hey, this is the plan:

First of all, we need to access the live dmesg when starting the container using ADB shell. Whenever a kernel panic happens, the logs will show exactly what caused it and print all the details we need to debug.

If you have Linux, you can easily pipe the dmesg output to a text file and attach it here:

Clear the kernel message buffer so we won’t see any log noise

adb shell "su -c 'dmesg -C'"

Start watching dmesg in real time while saving its output to a file

adb shell "su -c 'dmesg -w'" | tee kernel_logs.txt
This will tell us exactly what's causing the panics :)

Then i get this successfully:

kernel_logs.txt

Droidspaces-bugreport_2026-03-29_16-27-54.tar.gz

Without using the rootfs.img, i get the different zip