Thank you for the bug report. To summarize our investigation so far:
After deploying Anbox Cloud on Ubuntu 22.04 (Jammy), we encountered a
similar situation where Android instances fail to start after upgrading
the Linux kernel from 6.5.0 to 6.8.0. However, the same kernel version
works fine on Ubuntu 24.04.
We tested various kernel and Ubuntu combinations, and the results are as
follows:
Kernel 6.8.0-1015-aws on 22.04: Affected
Kernel 6.8.0-1016 on 24.04: Not affected
Kernel 6.8.0-45-generic on 22.04: Not affected
Kernel 6.8.0-1016 on 22.04: Affected
Kernel 6.8.0-1014-aws on 22.04: Affected
Kernel 6.8.0-1009-aws on 22.04: Affected
Kernel 6.8.0-1016-aws (noble kernel) on 22.04: Not affected
Kernel 6.5.0-1024-aws on 22.04: Not affected
This issue occurs on both amd64 and arm64 architectures.
Based on warning messages found from the kernel log,
https://pastebin.ubuntu.com/p/w4F8stP2KB/, we suspected the following commit
introduced a difference
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/drivers/android?h=aws-6.8-next&id=1cfa54f15ac51aad041c17c78a822e9e6d490f7a
The only scenario that leads to binder_alloc_do_buffer_copy returning an error
is during the offset alignment check.
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/drivers/android/binder_alloc.c?h=aws-6.8-next&id=1cfa54f15ac51aad041c17c78a822e9e6d490f7a#n1266
We will report this issue to the kernel team for further investigation.
BR
Gary
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081745
Title:
Anbox 1.23 Version Application failing
To manage notifications about this bug go to:
https://bugs.launchpad.net/anbox-cloud/+bug/2081745/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
