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 Kernel
Packages, which is subscribed to linux-aws-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2081745

Title:
  Anbox 1.23 Version Application failing

Status in Anbox Cloud:
  In Progress
Status in linux-aws-6.8 package in Ubuntu:
  New

Bug description:
  Hi Team,

  I recently deployed the latest version of Anbox on AWS and encountered
  several issues during the application setup:

  1.The instance is responding very slowly.
  2.Upon checking the serial console logs, I found the following errors:
  yaml
  Copy code
  [ 1587.721879] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1587.748032] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1587.777123] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1591.774328] binder_alloc_new_buf: 348 callbacks suppressed
  [ 1591.774333] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1591.820201] binder_debug: 706 callbacks suppressed
  [ 1591.820202] binder_linux: cannot allocate buffer: vma cleared, target dead 
or dying
  [ 1591.843000] binder_linux: 74645:74645 transaction call to 72068:0 failed 
19034/29189/-3, size 0-0 line 3253
  [ 1591.926911] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1591.952585] binder_linux: cannot allocate buffer: vma cleared, target dead 
or dying
  [ 1591.952588] binder_linux: 74647:74647 transaction call to 72068:0 failed 
19035/29189/-3, size 0-0 line 3253
  [ 1592.035897] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1592.061996] binder_linux: cannot allocate buffer: vma cleared, target dead 
or dying
  [ 1592.061999] binder_linux: 73114:73114 transaction call to 72068:0 failed 
19036/29189/-3, size 0-0 line 3253
  [ 1592.145473] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1592.171126] binder_linux: cannot allocate buffer: vma cleared, target dead 
or dying
  [ 1592.171129] binder_linux: 79431:79431 transaction call to 72068:0 failed 
19037/29189/-3, size 0-0 line 3253
  [ 1592.254447] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1592.280506] binder_linux: cannot allocate buffer: vma cleared, target dead 
or dying
  [ 1592.280507] binder_linux: 74623:74623 transaction call to 72068:0 failed 
19038/29189/-3, size 0-0 line 3253
  [ 1592.363856] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1592.389666] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1592.415762] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1592.444104] binder_linux: 72068: binder_alloc_buf, no vma
  [ 1592.467334] binder_li
  3. The application is stuck in initialization mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/anbox-cloud/+bug/2081745/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to