Skip to content

binder: undelivered transaction and binder_alloc_buf, no vma #12

@kungfooman

Description

@kungfooman

Dear Oculus team,

I used to be able to use my Oculus Go for VR development and I always had WLAN disabled to not receive any unwanted updates. However, a few days ago I decided to turn WLAN on again and it updated everything... first thing I had to do was a factory reset, because otherwise I would only see the three-dots-issue.

But after the update the entire Oculus browser fails to render anything. I connect to my local web server and the page is simply white. On one occasion it actually displayed the content, after I entered Firefox Reality, quit it and opened Oculus browser again (Firefox Reality renders properly). When I open a video, the sound plays but the video is just white aswell.

I tried to debug this issue, but since you took every opportunity to turn Linux into a straight jacket, it is very hard to do so even with years of C and Linux experience...

So the only pointer I have so far is dmesg:

[12512.492161] cnss_wlan_pci 0000:01:00.0: enabling device (0000 -> 0002)
[12512.505223] cnss: runtime resume status: 0
[12513.000839] binder: undelivered transaction 7300632
[12513.000858] binder: undelivered transaction 7300662
[12513.000865] binder: undelivered transaction 7300667
[12513.000870] binder: undelivered transaction 7300668
[12513.000927] binder: undelivered transaction 7300625
[12513.651903] binder: 12416: binder_alloc_buf, no vma
[12513.651924] binder: 963:1278 transaction failed 29201, size 76-0
[12513.660129] binder: undelivered transaction 7301501
[12513.749233] type=1400 audit(1659621008.024:321): avc: denied { getattr } for pid=14780 comm="boxed_process18" path="/data/data/com.oculus.browser" dev="sda8" ino=767072 scontext=u:r:isolated_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=0
[12514.152344] cnss: runtime suspend status: 0
[12514.333118] cnss_wlan_pci 0000:01:00.0: Refused to change power state, currently in D3
[12514.408594] cnss_wlan_pci 0000:01:00.0: enabling device (0000 -> 0002)
[12514.419848] cnss: runtime resume status: 0
[12514.818059] type=1400 audit(1659621009.091:322): avc: denied { getattr } for pid=14804 comm="boxed_process19" path="/data/data/com.oculus.browser" dev="sda8" ino=767072 scontext=u:r:isolated_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=0
[12514.832484] binder: undelivered transaction 7302950
[12514.832504] binder: undelivered transaction 7302974
[12514.832512] binder: undelivered transaction 7302992
[12514.832517] binder: undelivered transaction 7303004
[12514.832622] binder: undelivered transaction 7302945
[12515.209396] cnss: runtime suspend status: 0
[12516.538518] cnss_wlan_pci 0000:01:00.0: Refused to change power state, currently in D3
[12516.599372] cnss_wlan_pci 0000:01:00.0: enabling device (0000 -> 0002)
[12516.609398] cnss: runtime resume status: 0
[12518.465212] cnss: runtime suspend status: 0
[12518.478635] cnss_wlan_pci 0000:01:00.0: Refused to change power state, currently in D3
[12518.540408] cnss_wlan_pci 0000:01:00.0: enabling device (0000 -> 0002)
[12518.562003] cnss: runtime resume status: 0
[12518.602096] type=1400 audit(1659621012.864:323): avc: denied { getattr } for pid=14828 comm="boxed_process20" path="/data/data/com.oculus.browser" dev="sda8" ino=767072 scontext=u:r:isolated_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=0
[12521.094379] cnss: runtime suspend status: 0
[12521.105204] cnss_wlan_pci 0000:01:00.0: Refused to change power state, currently in D3
[12521.165429] cnss_wlan_pci 0000:01:00.0: enabling device (0000 -> 0002)
[12521.175963] cnss: runtime resume status: 0
pacific:/ $

Based on this article [1] [12513.651903] binder: 12416: binder_alloc_buf, no vma indicates that probably a Chrome background process crashed or maybe some right issue regarding /data/data/com.oculus.browser?

Hereby I also inform you about the European Right to repair which requires you to allow me to fix my own system [2].

That means:

  • allow to downgrade my system to a former working state
  • root access to actually USE my own compiled Linux kernel for repairing my broken system

[1] https://chengyihe.wordpress.com/2015/10/19/android-binder-error-log-binder_alloc_buf-no-vma/
[2] https://www.europarl.europa.eu/meetdocs/2014_2019/plmrep/COMMITTEES/IMCO/DV/2022/03-16/MfR_RighttoRepair_EN.pdf

Thank you for your attention,
Hermann Rolfes

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions