Hi.
I tried installing anbox on my system but it gave me this error:
modprobe: ERROR: could not insert ‘binder_linux’: Device or resource busy
I am a linux noob so if anybody knows how to fix it pls help!
Hi @bardiarajabi,
From what I could gather, that message means that the binder_linux kernel module is already present. It has been installed by something else.
Is there anything that could have installed it?
Did you install the AUR package or the Snap?
AUR btw
I don’t know but the problem is just… very bad
let me explain:
when I run this it says the error.
then after around 5~8 min, it causes the system livelock - Random Crash - System lock even with nohang and prelockd. Like when I open htop not even CPU, ram or hardware is fully used!!!
strange right?
but without the command system works fine.
okay see:
system causes live lock without being the CPU and ram full.
without the command, the system works fine.
nohang and prelockd cannot do anything at this moment.
GUI of all apps becomes unresponsible.
None of the Konsole command’s work(even shutdown or kill)
NOTHING WORKS EXCEPT HARD SHUTDOWN!
Had this same issue. Did some poking around in journalctl and found this:
-- Boot [redacted] --
Jun 06 21:33:31 linuspt2 systemd[1]: Mounting Android Binder File System...
Jun 06 21:33:31 linuspt2 systemd[1]: Mounted Android Binder File System.
Jun 06 22:27:42 linuspt2 baloo_file[1447]: 6843562234805760 "/home/nacl10/.cache/yay/anbox-git/dev-binderfs.mount" renaming "494eedd1ebead135_0" to "dev-binderfs.mount"
Jun 08 11:32:44 linuspt2 dbus-daemon[632]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.23977' (uid=0 pid=196694 comm="sudo modprobe binder_linux devices=binder,hwbinder")
Jun 08 11:32:47 linuspt2 sudo[196694]: nacl10 : TTY=pts/2 ; PWD=/home/nacl10 ; USER=root ; COMMAND=/usr/bin/modprobe binder_linux devices=binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_return' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_command' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_unmap_kernel_end' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_unmap_kernel_start' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_unmap_user_end' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_unmap_user_start' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_alloc_page_end' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_alloc_page_start' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_free_lru_end' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_free_lru_start' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_alloc_lru_end' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_alloc_lru_start' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_update_page_range' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_failed_buffer_release' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_buffer_release' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_alloc_buf' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_fd_recv' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_fd_send' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_ref_to_ref' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_ref_to_node' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_node_to_ref' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction_received' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_transaction' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_wait_for_work' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_read_done' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_write_done' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_ioctl_done' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_unlock' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_locked' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_lock' directory
Jun 08 11:32:47 linuspt2 kernel: Could not create tracefs 'binder_ioctl' directory
Jun 08 11:32:47 linuspt2 kernel: debugfs: Directory 'binder' with parent '/' already present!
Which seemed to me to indicate that the module might already be loaded. This seemed strange, since neither binder nor ashmem showed up in lsmod, but I decided I’d try just running Anbox anyway, after a clean boot. It worked.
(TL;DR: Just run Anbox. Don’t bother with loading the kernel modules.)
This looks to me like the Manjaro kernel is bundling binder and ashmem, meaning we don’t need to load them through DKMS and can just run Anbox—possibly without even installing them. (for reference, I’m running 5.15.41-1-MANJARO. I haven’t tried it with a realtime kernel)
Can someone with knowledge about the Manjaro kernel confirm?
Additional system info in case it's helpful
Kernel: 5.15.41-1-MANJARO (notably NOT a realtime kernel)
DE: Plasma 5.24.5
Machine: Lenovo Thinkpad P50
CPU: Intel i7-6820HQ
GPU: NVIDIA Quadro M2000M (regular video-nvidia driver, I’m not gonna mess with Optimus even though this computer can do it)
Anbox is installed from the AUR, version local-84f0268 (AUR package anbox-git)
Anbox image is anbox-image-gapps-rooted from the AUR, version 2018.07.19-7