New issue
Advanced search Search tips

Issue 702905 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Can't charge cave with official charger after 9202.53.0

Reported by set...@gmail.com, Mar 18 2017

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 9202.53.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.112 Safari/537.36
Platform: 9202.53.0 (Official Build) beta-channel cave

Steps to reproduce the problem:
1. Plug in official ASUS charger (ADP 45EW)

What is the expected behavior?
Chromebook starts to charge.

What went wrong?
Chromebook doesn't charge.

Keeps logging the following to /var/log/messages:

[   60.656148] PDLOG 2017/03/18 16:09:38.1489853377 P1 Disconnected
[   60.656665] PDLOG 2017/03/18 16:09:39.1489853378 P1 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA
[   60.657153] PDLOG 2017/03/18 16:09:39.1489853378 P1 Disconnected
[   60.657664] PDLOG 2017/03/18 16:09:39.1489853378 P1 SNK (not charging) Charger ??? 5000mV max 5000mV / 3000mA
[   60.658172] PDLOG 2017/03/18 16:09:40.1489853379 P1 SNK (not charging) Charger ??? 5000mV max 5000mV / 500mA
[   60.658691] PDLOG 2017/03/18 16:09:40.1489853379 P1 SNK Charger ??? 908mV max 5000mV / 500mA
[   60.659191] PDLOG 2017/03/18 16:09:40.1489853379 P1 Disconnected
[   60.659694] PDLOG 2017/03/18 16:09:40.1489853379 P1 Disconnected

Charger can charge properly other devices (PD) without any issues (tested with Pixel and a power bank), and also worked before the latest Beta upgrade.

Did this work before? Yes 57.0.2987.100 (Platform version: 9202.51.0)

Chrome version: 57.0.2987.112  Channel: beta
OS Version: 9202.53.0
Flash Version:
 

Comment 1 by set...@gmail.com, Mar 18 2017

Additionally, I tried two other PD chargers (which work with other devices), same symptom. Interestingly I can charge the device with low-power non-PD chargers, but obviously very slowly.

Comment 2 by set...@gmail.com, Mar 19 2017

After two powerwashes... results:
Powerwash on beta channel: same issue.
Powerwash to stable channel: issue gone.
Restart to beta channel: issue still gone.

I guess something went wrong during the update process. Anyway, probably this can be closed...
Components: OS>Kernel>Power

Comment 4 by derat@chromium.org, Nov 3 2017

Status: WontFix (was: Unconfirmed)

Sign in to add a comment