BattOr not working on build45-b4 |
||||
Issue descriptionbuild45-b4 is a Linux host for an Android Nexus 5X perf bisector. The system should have a BattOr attached. However, this serial log (https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Ftryserver.chromium.perf%2Fandroid_nexus5X_perf_bisect%2F1334%2F%2B%2Frecipes%2Fsteps%2Fdevice_status%2F0%2Fstdout) from a failed bisect seems to indicate that the BattOr isn't working. Infra labs, can you confirm that this host has: 1) One 7 port USB hub attached with a healthy Nexus 5X attached to it 2) One 7 port USB hub attached with a healthy BattOr attached to it. This BattOr should have a blinking orange light on it. Help is very much appreciated!
,
Mar 15 2017
(if you could also sanity check the other Nexus 5X perf bisectors, build43-b4 and build44-b4 to ensure that they're hooked up correctly at the same time, that'd also be appreciated.)
,
Mar 15 2017
BattOrs show up in lsusb output as "Future Technology Devices International" which shows up with one device in the output of device_status.
,
Mar 15 2017
Sorry, not serial log: I meant the device status log. (Thanks for the correction, rnephew@)
,
Mar 15 2017
chrome-bot@build45-b4:(Linux 14.04):/b/c/b/android_nexus5X_perf_bisect/src/third_party/catapult/common/battor/bin/linux2/x86_64$ ./battor_agent [0315/100847.509094:INFO:battor_finder.cc(45)] Found BattOr with display name BattOr_v3.3 at path /dev/ttyUSB0 GetFirmwareGitHash [0315/100857.545473:ERROR:serial_io_handler.cc(152)] Failed to open serial port: FILE_ERROR_ACCESS_DENIED [0315/100857.545494:FATAL:battor_agent_bin.cc(89)] Fatal error when communicating with the BattOr: CONNECTION FAILED #0 0x00000043ffce base::debug::StackTrace::StackTrace() #1 0x00000042361b logging::LogMessage::~LogMessage() #2 0x00000040a27c battor::(anonymous namespace)::HandleError() #3 0x00000040a0b9 battor::BattOrAgentBin::OnGetFirmwareGitHashComplete() #4 0x00000044051e base::debug::TaskAnnotator::RunTask() #5 0x0000004250ad base::MessageLoop::RunTask() #6 0x0000004257f5 base::MessageLoop::DoWork() #7 0x0000004277e9 base::MessagePumpLibevent::Run() #8 0x000000424dd7 base::MessageLoop::RunHandler() #9 0x00000042818e base::RunLoop::Run() #10 0x000000434d87 base::Thread::ThreadMain() #11 0x000000431713 base::(anonymous namespace)::ThreadFunc() #12 0x7fe01a664184 start_thread #13 0x7fe01967337d clone
,
Mar 15 2017
The problem is we didn't add chromebot to the dialout group, so they could not communicate with the BattOr via serial-over-usb. I logged into build43-45-b4 and ran: sudo usermod -a -G dialout chrome-bot They should be working after the next reboot.
,
Mar 15 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by charliea@chromium.org
, Mar 15 2017