Issue metadata
Sign in to add a comment
|
caroline: battery no longer charges after upgrading from 63 stable to 64 stable
Reported by
sun...@gmail.com,
Mar 6 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10176.72.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Platform: 10176.72.0 (Official Build) stable-channel caroline Steps to reproduce the problem: 1. Upgrade chromeos from version 63 to 64 on stable channel 2. Observe that chromebook battery no longer charges via its own USB-C power adapter: 3. Observe that battery symbol in the system tray next to the wifi icon does not show a thunderbolt/electricity symbol 4. Observe that power LED on chromebook remains blue (which indicates discharging) and does not change to green (which indicates charging) 5. Observe blinking light pattern on USB-C power adapter that came with chromebook: (comma represents short double blink, period represents long single blink) .,,,,.,,,.,...,,,,.,,,,.,..,,,,,,....,,.,,,.,,,,,.........,.,,,,,. and I guess this repeats afterwards What is the expected behavior? Plugging in the USB-C charger cable that came with my chromebook should have started charging it: the battery icon in the system tray (next to the wifi signal icon) should change to show a thunderbolt/electricity symbol. Also, the power LED on the chromebook should change from blue to green to indicate that it is charging up. What went wrong? I upgraded ChromeOS from version 63 stable to 64 stable today and my Samsung Chromebook Pro no longer charges the battery: neither plugging its own USB-C power adapter nor connecting an external powered USB-C hub. In addition, it no longer detects external displays (connected via USB-C to DisplayPort/HDMI adapter) as reported in Chromium Issue 818825 . I tried switching from the stable channel to beta channel and then to dev channel in hopes that these issues might have been fixed: unfortunately they were not. As a result, I have lost the ability to reset my chromebook back to version 63. Please help (it's only a matter of time before my chromebook's battery runs out and since it won't charge up anymore, I'm out of luck). Thank you. Did this work before? Yes 63 stable Chrome version: 64.0.3282.167 Channel: n/a OS Version: 10176.72.0 Flash Version: 28.0.0.161
,
Mar 6 2018
Feedback report is at http://feedback/#/Report/85149018827.
,
Mar 6 2018
Looks like VBUS is collapsing [ 60.654880] PDLOG 2018/03/06 01:36:16.1520300175 P1 SNK Charger ??? 2431mV max 5000mV / 500mA [ 60.655613] PDLOG 2018/03/06 01:36:16.1520300175 P1 Disconnected [ 60.656049] PDLOG 2018/03/06 01:36:16.1520300175 P1 Disconnected [ 60.656497] PDLOG 2018/03/06 01:36:17.1520300176 P1 SNK (not charging) Charger ??? 5000mV max 5000mV / 3000mA [ 60.656926] PDLOG 2018/03/06 01:36:18.1520300177 P1 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA [ 60.657382] PDLOG 2018/03/06 01:36:18.1520300177 P1 SNK Charger ??? 791mV max 5000mV / 500mA [ 60.657815] PDLOG 2018/03/06 01:36:18.1520300177 P1 Disconnected [ 60.658252] PDLOG 2018/03/06 01:36:18.1520300177 P1 Disconnected [ 421.614467] PDLOG 2018/03/06 01:44:18.1520300657 P0 Disconnected [ 421.615098] PDLOG 2018/03/06 01:44:18.1520300657 P0 Disconnected [ 421.615709] PDLOG 2018/03/06 01:44:20.1520300659 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA [ 421.616398] PDLOG 2018/03/06 01:44:20.1520300659 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 3000mA [ 421.617125] PDLOG 2018/03/06 01:44:20.1520300659 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA [ 421.617657] PDLOG 2018/03/06 01:44:20.1520300659 P0 SNK Charger ??? 1113mV max 5000mV / 500mA [ 421.618150] PDLOG 2018/03/06 01:44:20.1520300659 P0 Disconnected [ 421.618667] PDLOG 2018/03/06 01:44:20.1520300659 P0 Disconnected [ 481.774401] PDLOG 2018/03/06 01:45:18.1520300717 P0 Disconnected [ 481.774877] PDLOG 2018/03/06 01:45:20.1520300719 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA [ 481.775387] PDLOG 2018/03/06 01:45:20.1520300719 P0 Disconnected [ 481.775865] PDLOG 2018/03/06 01:45:20.1520300719 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 3000mA [ 481.777065] PDLOG 2018/03/06 01:45:20.1520300719 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA [ 481.777583] PDLOG 2018/03/06 01:45:20.1520300719 P0 SNK Charger ??? 1083mV max 5000mV / 500mA [ 481.778059] PDLOG 2018/03/06 01:45:20.1520300719 P0 Disconnected [ 481.778567] PDLOG 2018/03/06 01:45:20.1520300719 P0 Disconnected [ 541.934390] PDLOG 2018/03/06 01:46:18.1520300777 P0 Disconnected [ 541.934819] PDLOG 2018/03/06 01:46:20.1520300779 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA [ 541.935408] PDLOG 2018/03/06 01:46:20.1520300779 P0 Disconnected [ 541.935835] PDLOG 2018/03/06 01:46:20.1520300779 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 3000mA [ 541.936266] PDLOG 2018/03/06 01:46:20.1520300779 P0 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA [ 541.936697] PDLOG 2018/03/06 01:46:20.1520300779 P0 SNK Charger ??? 1054mV max 5000mV / 500mA [ 541.937388] PDLOG 2018/03/06 01:46:20.1520300779 P0 Disconnected [ 541.937826] PDLOG 2018/03/06 01:46:20.1520300779 P0 Disconnected Note in each of the groups the voltage going down to much less than 5000mV (791, 113, 1083, 1054) at which point there's a disconnect. And power_supply_info, Device: Line Power path: online: no type: enum type: Disconnected voltage (V): 0 current (A): 0 max voltage (V): 0 max current (A): 0 active source: available sources: supports dual-role: yes Does look like caroline's most recent FW upgrade was, 7820.356.0 and was part of R64 https://b.corp.google.com/issues/71387863 https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-caroline-private/+/537998 landed in 10176.36.0 And previous version was 7820.349.0 also part of R64 https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-caroline-private/+/524158 landed in 10176.8.0 So if there's a FW dep we hopefully have a small window to debug.
,
Mar 6 2018
,
Mar 6 2018
Nothing looks that interesting here: https://crosland.corp.google.com/log/7820.349.0..7820.356.0 In fact even going back to I believe the release in R62 I still don't see anything that smells like a charging / PD change https://crosland.corp.google.com/log/7820.329.0..7820.356.0
,
Mar 6 2018
It sounds like the PD chips are not working properly if external display is also not working, does a hard refresh (Refresh+Power) do anything to fix it? This change looks like it could affect the PD chips: https://chromium.googlesource.com/chromiumos/platform/ec/+/20baa933615fa6942005953e1e0ea3a3b16bbd5f
,
Mar 7 2018
Thank you! The hard refresh (Refresh+Power) did the trick: plugging in the charger and doing the hard refresh seems to have fixed both problems: my chromebook is now charging properly and it's also detecting/rendering the external display properly. ^_^
,
Mar 23 2018
Glad the 'hard reboot' successfully un-wedged charging. Please let us know if the problem returns. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Mar 6 2018