New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 909947 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 913145



Sign in to add a comment

No internal network

Reported by chasing....@gmail.com, Nov 29

Issue description

After boot up moblab, there is no internal network, the following setup does not work:

moblab -> ethernet -> access point -> ethernet (physical connection) -> USB adapter -> DUT

 
moblab_logs_gPlE3L.tgz
459 KB Download
Cc: haddowk@chromium.org mqg@chromium.org tbroch@chromium.org
Owner: mattmallett@chromium.org
Status: Assigned (was: Untriaged)
No internal network i.e. no DUT network? The network bridge init ran without error.

What is the purpose of the access point for wired connection? Why not connect the DUT directly to the moblab? Are you using it as an ethernet switch?
sometimes I do a physical network between AP and DUT so that AP just act as a switch. 
Same problem happened again. DUT have trouble connecting to wifi, indicating that the moblab internal network probably has some problems. 


moblab_logs_Ylc9O0.tgz
3.7 MB Download
I found these mobmonitor warnings:
{"health": false, "name": "UsbEthernet", "actions": [], "description": "No USB ethernet device detected. This may indicate that no DUT (or some other important device) is not connected."},
{"health": false, "name": "DutExists", "actions": [], "description": "No DUTs were detected. Please plug in a device for test."}

Can you check your moblab side USB dongle? Looks like it might have flaked out.
I will check my ethernet USB dongle next time. It has crashed before, so it's likely. 
Are there more details on the USB dongle crash?  I think Grant can help steer us at a stable device there.
Blocking: 913145

Sign in to add a comment