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

Issue 661332 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Servo V4 causes Asuka drops IP

Project Member Reported by haoweiw@chromium.org, Nov 1 2016

Issue description

Currently finding. Servo V4 is causing Asuka drops IP. 

I have tested few Servo V4 and none of them can keep Asuka alive more than 10 min. 

I switched one Asuka with Eth USB dongle. That DUT can be pingable consistently. 



 
Cc: elerner@chromium.org nsanders@chromium.org
Haowei,
can you add /var/log/messages and dmesg from an asuka when the dut loses connectivity from the v4's ethernet port.

Comment 2 by haoweiw@google.com, Nov 1 2016

I did not read the whole thing. But below message are suspicious

2016-11-01T14:54:47.348164-07:00 INFO avahi-daemon[5413]: Withdrawing address record for 100.115.130.137 on eth0.
2016-11-01T14:54:47.348168-07:00 INFO avahi-daemon[5413]: Leaving mDNS multicast group on interface eth0.IPv4 with address 100.115.130.137.
2016-11-01T14:54:47.373797-07:00 INFO avahi-daemon[5413]: Interface eth0.IPv4 no longer relevant for mDNS.


meessage
306 KB View Download
dmesg
50.2 KB View Download
Components: Infra>Client>ChromeOS
Labels: -Hardware-Lab
Thanks Haowei, I'm going to try and recreate it at my desk as well.

Comment 5 by autumn@chromium.org, Nov 16 2016

Owner: kevcheng@chromium.org
Kevin, were you able to reproduce this? 
Status: WontFix (was: Untriaged)
I wasn't able to reproduce this at my desk but since this was an EVT unit, asuka will be moving to atlantis (and not use v4). Assuming this is due to early hw/sw quirks, we'll try again when this is in MP. Closing out as wontfix.

Sign in to add a comment