New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 790745 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ChromeOS issue: Lenovo N23 (Hana) are unable to turn back on after closing the lid

Project Member Reported by ykrychala@google.com, Nov 30 2017

Issue description

ChromeOS version: 61.0.3163.123 
ChromeOS device model: Lenovo N23 Yoga 
Case#: 13967730

Description:
Customer is reporting his Lenovo devices are unable to turn back on after leaving the devices charging over night with their chargers and closed lid, the only way to get the devices to turn back on is to plug the charger in the device once again
Also he has received reports from devices that have been experiencing the same issue while just closing the lid without turning the device off nor plugging the charger in. 

Steps to reproduce: 
1. Close the lid of the device 
2. Plug the charger and leave it charging over night 
3. Unplug the charger and proceed to open the lid and try to turn the device on 
4. The device will not turn on, even after pressing the power button repeatedly 
5. Plug the charger and the device will turn on and show it is fully charged 

Current Behavior / Reproduction: 
devices are unable to turn back on

Expected Behavior: 
devices turn on

Drive link to logs: 
https://drive.google.com/open?id=17gOKxP12hKgret7u6uoek8AYrQexLk6Q
https://drive.google.com/open?id=1rzoU9sZ_wnBKuJdpq-a8rJBuA3IKIPVg
https://drive.google.com/open?id=16N2fkHn-JDAnapQ7oVho_HdWImHRG8v5
 

Comment 1 by roy...@google.com, Nov 30 2017

Cc: nsale@chromium.org
Labels: -Pri-2 Pri-0
Owner: vineeths@chromium.org
Vineet: Do you know who can review this quickly and make a call on whats going on ?

Comment 2 by roy...@google.com, Nov 30 2017

Cc: bhthompson@chromium.org
Cc: djkurtz@chromium.org
+djkurtz for MTK stuff, whom may know whom knows the most about about the EC and battery configuration used here.

Looking at the first log it seems like we suspended but never came back. 

messages:
...
2017-11-03T11:36:11.195051-05:00 NOTICE powerd_suspend[4606]: Finalizing suspend
2009-12-31T18:00:06.859009-06:00 INFO kernel: [    0.000000] Booting Linux on physical CPU 0x0
...

eventlog:
...
347 | 2017-11-03 11:18:58 | Wake
348 | 2017-11-03 11:36:10 | Sleep
349 | 2009-12-31 18:00:00 | System boot | 0
350 | 2009-12-31 18:00:02 | System boot | 0
...

The loss of time indicates the system may have lost power to the real time clock (RTC).

We may want to engage with the OEM here, the problem appears to be below Chrome OS, if we could reproduce it reliably and get an EC UART trace out of it that might give some more indication of what is going on, but beyond that this seems like it could be a problem in the battery, likely inadvertently going into battery cut off.

Comment 4 by roy...@google.com, Dec 1 2017

FYI: This is a dup of b/67033247 which is fixed in M63

Status: WontFix (was: Unconfirmed)
Per #4 and linked issue.
What issue number was this a duplicate of?  I wanted to review that as well.  The search yields no results for issue 67033247 or b/67033247.  

Comment 7 by armandoa@google.com, Dec 21 2017

Hi team, 

I noticed that as per #4 M63 will resolved this issue. However, as per http://cros-omahaproxy.appspot.com, M63 has not been rolled out for Lenovo N23 Yoga/Flex 11 Chromebook. Is this intended? I was able to confirm this with an affected customer that their Lenovo N23 Yoga/Flex 11 Chromebook have not updated to M63 yet. 

Thank you.
Still looking for an update on this.  Has M63 been confirmed to correct the firmware problems on the battery?  When is this scheduled to be pushed to the N23 yoga systems if the release does fix?
M63 is going through final approvals at the moment for the N23 yoga devices. Can't confirm exact schedule at the moment. 
M63 has started to roll out to devices. Please check again.
Cc: ryutas@chromium.org
vineeths@
One of the customer who is affected this issue has reported about the issue still remains after upgraded to M63(63.0.3239.140).
Please refer the log file and let me know if you require additional information from the customer.

I can see the same massages as #3 from the provided log.

Messages:
2018-01-17T08:35:05.577573-06:00 NOTICE powerd_suspend[21325]: Finalizing suspend
2009-12-31T18:00:03.776912-06:00 INFO kernel: [    0.000000] Booting Linux on physical CPU 0x0

Event log:
381 | 2018-01-17 06:59:24 | Wake
382 | 2018-01-17 06:59:27 | Sleep
383 | 2018-01-17 07:28:15 | Wake
384 | 2018-01-17 08:35:05 | Sleep
385 | 2009-12-31 18:00:00 | System boot | 0
386 | 2009-12-31 18:00:00 | System boot | 0
387 | 2009-12-31 18:00:00 | System boot | 0
388 | 2009-12-31 18:00:02 | System boot | 0

Device log.
https://drive.google.com/open?id=1wr6z86gfM5IQ3vUmzkG9WpsSJtV9jEmr

Device info.
https://drive.google.com/open?id=1Em8mIYJQXZIJxlO-dtdGqydFx2Tn2DjEHH6GHpwnZGA
(Model	Lenovo N23 Yoga/Flex 11 Chromebook, Google Chrome Version	63.0.3239.140)

How many devices are showing this problem now with version 63.0.3239.140?
Status: Assigned (was: WontFix)
Labels: -Pri-0 Pri-2
Components: OS>Kernel>Power
Components: OS>Firmware>EC
Owner: ryutas@chromium.org
 vineeths@
sorry for late reply.
I will update once confirmed.

Status: WontFix (was: Assigned)
the tech case was closed due to no response back from the customer.

Sign in to add a comment