N4s on build40-b1 always going down |
|||||||
Issue descriptionhttp://shortn/_4VBp0Odqwg Is it due to device type? OS (jellybean)? Host-issue?
,
Sep 12 2016
,
Sep 12 2016
There was supposed to be 7 devices, and 6 of them have gradually gone missing since last friday (ssh into the bot and lsusb shows they aren't there). Can the sysadmin take a look on what happened to the devices or where they have gone? 027435465a23b4bb: missing [logdog] mako JWR67E 009ee842dbdd02ae [logdog] 009ef58c4b14b7bb: missing [logdog] 01cd034f1c20a3b6: missing [logdog] 0480c1d40b494a7f: missing [logdog] 02740f1a0b59aab6: missing [logdog] 01cd2ea51a1ba2b6: missing [logdog]
,
Sep 12 2016
+ labs for real Any chance we could leave one of the N4s down for investigation? I'd like to poke it a bit manually and see what there is to see.
,
Sep 13 2016
,
Sep 13 2016
3 are appear dead (black screen, totally unresponsive) 2 are stuck in the boot up animation. 1 has wedged while running a test. Ironically, the only one running has a swollen battery. This one needs to be replaced. Ben, did you want to take any of these to your desk? If not then I'll perform a power reset on them to get them back.
,
Sep 13 2016
Darn, I was hoping they'd all be in the same failure state. Any chance you could set aside one of the three phones that are dead/unresponsive? I can swing by later and pick it up.
,
Sep 13 2016
Will do. I'm out tomorrow so this will happen on Thursday.
,
Sep 15 2016
N4 with swollen battery replaced. Revived the other ones. Have one of the ones that appears dead set aside for you. Current device list is: List of devices attached 01cd034f1c20a3b6 device 02740f1a0b59aab6 device 009ef58c4b14b7bb device 0480c1d40b494a7f device 027435465a23b4bb device 009efddf521cb6bb device
,
Sep 19 2016
Well, the bot is back down to only 3 healthy devices. Not sure what's taking them offline. And the one I got at my desk produces spectacular results when trying to investigate. Without fail, connecting the device via debug cable crashes my macbook. Full stop; everything freezes. I've no idea what would cause that. Might be related to the failures we're seeing on the bot...? I'm open to ideas.
,
Sep 19 2016
Hang on. I just took a look at our flash station in the lab and it does not contain bootloader.img that comes with the distribution. So who knows what bootloader is currently running on these. I've just updated the flashstation target for JWR67E. I have to run to the shuttle but tomorrow I'm going to flash them all again.
,
Sep 28 2016
Marking this as a wontfix as the devices were removed as outlined in http://crbug.com/650402 |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jbudorick@chromium.org
, Sep 12 2016