New issue
Advanced search Search tips

Issue 626118 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 618413



Sign in to add a comment

suspend_stress_test not working on samus-cheets test image

Project Member Reported by kirtika@chromium.org, Jul 6 2016

Issue description

OS: chromeos, samus-cheets, 8517.0.0 or later. 

What steps will reproduce the problem?
(1) On a test image, run activate_short_dark_resume 
(2) run 'suspend_stress_test -c 1'


What is the expected output?
Should suspend and resume normally. 

What do you see instead?
Samus hangs, can only restore via alt-volUp-R or alt-volUp-X combination. 



 
Update: rebooted the system, doing just suspend_stress_test - and that causes a restart. 

Summary: suspend_stress_test not working on samus-cheets test image (was: activate_short_dark_resume not working)

Comment 3 by tbroch@chromium.org, Jul 15 2016

Components: OS>Kernel>Power
Labels: M-54
for 8578.0.0 'suspend_stress_test -c 1' separately works for me.

I still see original (dark resume) failure however.


just simple echo mem > /sys/power/state make host unrecoverable (resume fails).  Need to connect servo as there's nothing in ramoops to debug and I'm having to long-press power to shutdown and then power back on.

Comment 4 by tbroch@chromium.org, Jul 15 2016

localhost ~ # activate_short_dark_resume 
powerd start/running, process 14302

localhost ~ # suspend_stress_test -c 1
Running 1 iterations with:
  suspend: 5-10 seconds
  wake: 5-10 seconds
  backup_rtc: false
  errors_fatal: true
  bugs fatal:  true
  warnings fatal:  false
  crcs fatal:  true
  suspend command: powerd_dbus_suspend --delay=0
  wakeup source to ignore: none
  record_dmesg_dir: 
powerd start/running, process 24406
tlsdated stop/waiting
Suspend     1 of 1: sleep for  6 seconds...

And on the EC side,

[61.893814 HC 0x8a]
[61.894089 HC 0x8b]
[61.894328 ACPI query = 0]
[62.030680 Port 80: 0x1002]
[62.030996 LPC RESET# asserted]
[62.031200 power state 3 = S0, in 0x01db]
[62.031516 power state 7 = S0->S3, in 0x01d3]
[62.034760 power state 2 = S3, in 0x01db]
[62.035061 power state 2 = S3, in 0x01db]
[62.049595 Disabling console in deep sleep]
[64.412768 LB cur_seq 6 S0S3 returned pending msg 2 S3]
[64.413174 LB running cur_seq 2 S3. prev_seq 6 S0S3]
[64.413429 LB_off]
[64.413894 LB_init_vals]
[69.280194 power state 2 = S3, in 0x01fb]
[69.280596 power state 6 = S3->S0, in 0x01fb]
[69.301015 Port 80: 0x1001]
[69.301732 USB charge p0 m2]
[69.301912 USB charge p1 m2]
[69.308495 power state 3 = S0, in 0x01fb]
[69.309309 Lid: Done Init type:0x0 range:2 rate:100000]
[69.311687 Base Gyro: MS Done Init type:0x1 range:2000 odr:119000]
[69.364556 LPC RESET# deasserted]
[69.467816 Port 80: 0x31]
[69.468069 HC 0x06]
[69.468644 HC 0x87]
[69.539128 Port 80: 0xf0]
[69.539338 HC 0x8d]
[69.539622 HC 0x8e]


and in this case I saw a reboot instead of a hang.


Here's working output of S0 -> S3 -> S0 from EC perspective.

[562.435137 Port 80: 0x1002]
[562.435431 LPC RESET# asserted]
[562.435615 power state 3 = S0, in 0x01db]
[562.435908 power state 7 = S0->S3, in 0x01db]
[562.438894 power state 2 = S3, in 0x01db]
[562.439137 power state 2 = S3, in 0x01db]
[564.474411 LB cur_seq 6 S0S3 returned pending msg 2 S3]
[564.474825 LB running cur_seq 2 S3. prev_seq 6 S0S3]
[564.475087 LB_off]
[564.475561 LB_init_vals]
[572.836085 KB poll]
[572.843878 event set 0x00001000]
[572.844529 power state 2 = S3, in 0x01fb]
[572.844937 power state 6 = S3->S0, in 0x01fb]
[572.865354 Port 80: 0x1001]
[572.866867 USB charge p0 m2]
[572.867121 USB charge p1 m2]
[572.874309 power state 3 = S0, in 0x01fb]
[572.877784 Lid: Done Init type:0x0 range:2 rate:100000]
[572.882533 Base Gyro: MS Done Init type:0x1 range:2000 odr:119000]
[572.930739 LPC RESET# deasserted]
[573.033877 Port 80: 0x31]
[573.034130 HC 0x06]
[573.035416 HC 0x87]
[573.105880 Port 80: 0xf0]
[573.106111 HC 0x8d]
[573.106401 HC 0x8e]
[573.106748 event clear 0x00001000]
[573.106957 ACPI query = 13]

No 'event clear' in failure cases so I'll focus there initially.

Comment 5 by tbroch@chromium.org, Jul 21 2016

Labels: OS-Chrome
Status: Assigned (was: Untriaged)

Comment 6 by tbroch@chromium.org, Jul 21 2016

Blocking: 618413
Status: Archived (was: Assigned)

Comment 8 by ketakid@google.com, Mar 18 2017

Labels: Pri-3
Status: Available (was: Archived)
Activating. Please assign to the right owner and the appropriate priority.

Comment 9 by tbroch@chromium.org, Dec 15 2017

Owner: ----
Project Member

Comment 10 by sheriffbot@chromium.org, Dec 17

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -M-54
Status: WontFix (was: Untriaged)
Closing as dark resume is disabled on samus

Sign in to add a comment