Chrome Version:
DVT4 Platform 3824.0.0 with a more recent version of Cr (r187599) and WK (r145357)
Describe the steps to reproduce:
All of a sudden it was having trouble powering on and off. While powered on, the screen would go black. By holding down the power button it would sometimes come back to life. This would let me interact for a minute maybe. Then it would go black again. I did this a couple of times and then holding down the power and plugging and unplugging would help. At this point I thought a power cycle was in order. I got the nice log out animation and then it won't boot up.
Leaving the machine for about 10 minutes (plugged in) and coming back seemed to allow it to power up. Flagging as a power issue for now (feel free to relabel).
- log-031213-113856.tar.bz2 893.27KB
Comment #1
Posted on Mar 12, 2013 by Massive Giraffe(No comment was entered for this change.)
Comment #2
Posted on Mar 12, 2013 by Grumpy Camel(No comment was entered for this change.)
Comment #3
Posted on Mar 12, 2013 by Massive GiraffeFrom the description, it seems that the screen was going dark when it was not supposed to, but the device was still working.
Were the power button presses short, medium, or long?
After you shut down the system, did you wait a few seconds before pressing the power button again? The EC imposes a delay.
I scanned the logs but found nothing that indicates a malfunction.
(Adding Sameer since "power" is mentioned, but I doubt it has anything to do with it.)
Comment #4
Posted on Mar 13, 2013 by Massive GiraffeI'm pretty sure that I tried sshing into the Pixel when the screen was dark, but couldn't (it's got a test image on it). Not 100% certain of this though.
I tried both short (tap) and long (10s) button presses.
Comment #5
Posted on Mar 13, 2013 by Massive GiraffeOK. So machine is in an "off" state. Currently unplugged. No glowing light bar. No ping.
Tapping power does not bring it up. Holding for 2 seconds does not bring it up. Holding for 10 seconds does not bring it up.
Just plugged it in. Tapping power does not bring it up. Holding for 2 seconds does not bring it up. Holding for 10 seconds does not bring it up.
Comment #6
Posted on Mar 13, 2013 by Helpful KangarooWhen you plug in the power, does the light charger come on?
Comment #7
Posted on Mar 13, 2013 by Massive Giraffe+duncan, mark
Have we seen this problem? From comment #5 it seems to me that either the EC is stuck somehow or there is a HW problem.
Jonathan Backer is in Waterloo so the device is not immediately accessible.
Comment #8
Posted on Mar 13, 2013 by Massive GiraffeI just pressed the power button (quickly) for kicks and it's back on.
Comment #9
Posted on Mar 14, 2013 by Massive GiraffeI grepped the log file and ec_info.txt indicates link_v1.2.109-97b1886
Unfortunately, I can't do a firmware update because I can't power on.
Comment #10
Posted on Mar 14, 2013 by Massive GiraffeI've got someone here who may be able to servo the unit (he's done daisy, not link).
Should I try that, or can I swap someone for a working unit?
Comment #11
Posted on Mar 14, 2013 by Massive PandaRegarding #8, did you mean that the Pixel is "back on" i.e. it powered on again? But then in #9 you say you can't power on. Can you clarify?
Comment #12
Posted on Mar 14, 2013 by Massive GiraffeYeah. I was able to power on in #8. When I tried to do it the next day (#9 --- it must have suspended or powered off), I couldn't bring it up.
I just opened the lid now --- the keyboard backlight flickered and now it's off again.
Just plugged in and powered on. Seems like the battery was drained.
I got to a log in screen. Went to console, stopped ui, and just ran "chromeos-firmwareupdate --mode=todev" with success. It says the ec updated to 1.2.120 (fingers crossed). However, on reboot "ectool version" says I'm still at 1.2.109 :(
Comment #13
Posted on Mar 14, 2013 by Massive Girafferharrison@ tells me that to update the EC, I need to disassemble the device, remove a screw, and run a recovery image. Should I proceed?
Comment #14
Posted on Mar 14, 2013 by Massive Giraffe(No comment was entered for this change.)
Comment #15
Posted on Mar 14, 2013 by Massive GiraffeAdding Simon to see if he can help.
However, I am not sure we need to play around with the EC. I don't think the update can make much difference.
It may be more useful if you let the battery charge, and then see if the erratic behavior persists (or test under AC power). In that case it would seem a HW problem, and we'll ping the HW team.
Thanks.
Comment #16
Posted on Mar 14, 2013 by Massive Giraffe@15: I was seeing this behaviour with a full battery yesterday. It drained overnight.
Comment #17
Posted on Mar 19, 2013 by Quick RabbitMoved to: Issue chromium:221935
Status: Moved
Labels:
Type-Bug
Pri-2
Cr-OS-Kernel-Power
OS-Chrome