Chromebox for Meetings CfM dropping ethernet connection |
|||||||
Issue descriptionChrome Version: 56 / 9000.91.0 / 56.0.2924.110 OS: Chrome OS Device: Asus Chromebox CN62 (Guado) What is the expected result? Ethernet connection works What happens instead? Chromebox for Meetings CfM dropping ethernet connection and does not reconnect From the log file it seems like connection got dropped due to a shill error: 2017-04-13T12:42:09.220085-07:00 WARNING kernel: [ 165.839728] init: debugd main process (684) killed by TERM signal 2017-04-13T12:42:09.250574-07:00 ERR shill[908]: [ERROR:object_proxy.cc(582)] Failed to call method: org.chromium.dhcpcd.Release: object_path= /org/chromium/dhcpcd: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.45 was not provided by any .service files 2017-04-13T12:42:09.250611-07:00 ERR shill[908]: [ERROR:dbus_method_invoker.h(111)] CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=org.freedesktop.DBus.Error.ServiceUnknown, Message=The name :1.45 was not provided by any .service files ................... 2017-04-13T12:42:09.252176-07:00 INFO avahi-daemon[1337]: Interface eth0.IPv4 no longer relevant for mDNS. 2017-04-13T12:42:09.260123-07:00 INFO kernel: [ 165.879742] r8169 0000:01:00.0 eth0: link down logs: https://drive.google.com/open?id=0By9xEkAUmm_cVjBDZXZST3hXamM
,
Apr 21 2017
,
Apr 21 2017
56 is outdated, 57 has been stable for some time and 58 should be stable in the next couple weeks, is this seen on 57 or newer? The part you are looking at looks like it was part of the shut down sequence, in the power_manager log we see: ... [0413/124209:INFO:daemon.cc(1145)] Got RequestShutdown message from :1.11 [0413/124209:INFO:display_power_setter.cc(80)] Asking Chrome to turn all displays off [0413/124209:INFO:daemon.cc(1503)] Shutting down, reason: user-request ... In the more recent log we do see a lot of eth0 disconnecting, this could indicate a hardware issue (maybe loose cable)? ... 2017-04-13T12:45:03.069125-07:00 INFO kernel: [ 168.036520] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:03.076154-07:00 INFO kernel: [ 168.043062] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:13.864120-07:00 INFO kernel: [ 178.840275] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:13.871159-07:00 INFO kernel: [ 178.846762] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:24.328121-07:00 INFO kernel: [ 189.312699] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:24.335157-07:00 INFO kernel: [ 189.319224] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:34.824118-07:00 INFO kernel: [ 199.817180] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:34.831153-07:00 INFO kernel: [ 199.823710] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:44.309099-07:00 INFO kernel: [ 209.309797] r8169 0000:01:00.0 eth0: link down 2017-04-13T12:45:44.316097-07:00 INFO kernel: [ 209.316358] r8169 0000:01:00.0 eth0: link down ... Maybe this is a dupe of https://buganizer.corp.google.com/issues/34394866 ?
,
Apr 21 2017
57 is currently blocked for CFM due to other issues. But we should definitely ask this customer to test with 57 if possible.
,
Apr 21 2017
Based on the description this looked similar (in a slightly different way) to b/34394866 which Abhishek is already looking at.
,
Apr 21 2017
The assigned owner "abhishekbh@chromium.org" is not able to receive e-mails, please re-triage. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 21 2017
,
Apr 26 2017
I have confirmed with customer and this issue does not appear on beta - 9334.42.0 (Official Build) beta-channel guado
,
Apr 26 2017
,
Jul 4 2017
Since we are moving to 59, should this be closed? Are we sure that this is no longer a problem?
,
Jul 5 2017
Closing per #9 and #11. Please reopen if the issue is observed again on M59. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 Deleted