RPC tracker not able to connect with handset


#1

After follow new compile and steps to treat cross compile using RPC, phone is not able to connect with RPC tracker. Any additional step need to follow?


#2

I met similar problems. I have uploaded the shared library, but remote.load_module() still doesn’t work.


#3

Do you follow this readme page https://github.com/dmlc/tvm/tree/master/apps/android_rpc ?

No extra step is required. After you start the server on the phone, you can query the tracker by
python3 -m tvm.exec.query_rpc_tracker. You are supposed to see one free “andoird” in the queue status.

cc @eqy We should print error messages in the app, so we know that happens.


#4

Can you share what error messages you are seeing?

@dayanandasiet
Can you verify that the tracker is on the same NAT as the phone and works (e.g., using another RPC server)?

@Faldict My current guess based on limited information is that the app needs to built with the correct libraries linked if they are used (e.g., OpenCL for GPUs).
We can consider pricing more information in the app, but for now you can get a decent idea of wha the app is doing by just inspecting stderr in logcat, as the current app is very chatty in stderr.


#5

Yes, Phone and Tracker on same NAT and phone under tracker que status

user@user-VirtualBox:/my-model$ python -m tvm.exec.query_rpc_tracker
Tracker address 0.0.0.0:9090

Server List
----------------------------
server-address	key
----------------------------
10.0.2.2:44105	server:android
----------------------------

Queue Status
----------------------------
key	free	pending
----------------------------
android	1	0
----------------------------

Local Computer Ip:
IPv4 Address. . . . . . . . . . . : 192.168.43.188

RPC Configuration:
Address : 192.168.43.188
Port : 9090
Key : android

Virtual Box Tracker Configuration:
user@user-VirtualBox:~/work_tvm/work$ python -m tvm.exec.rpc_tracker --port 9090
INFO:root:If you are running ROCM/Metal, fork will cause compiler internal error. Try to launch with arg --no-fork
INFO:RPCTracker:bind to 0.0.0.0:9090


#6

The RPC device address appears to be 10.0.2.2, which makes it look like it’s not on the same subnet as the local computer IP. Can you ping 10.0.2.2 from your VM?

We have not tested running a tracker in a VM before, and depending on this VM host setup this may complicate the networking setup.


#7

Thanks @eqy after set VM subnet address properly with my handset


#8

Thanks for addressing this issue together, maybe it make sense to create a RPC knowhow and troubleshooting to guide users on these issues