New issue
Advanced search Search tips

Issue 906699 link

Starred by 1 user
Status: Assigned
Owner:
mqg@chromium.org
Cc:
matthewjoseph@chromium.org
ka...@chromium.org
sontis@chromium.org
puthik@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

vayne/pantheon/nocturne: Suspend_stress_test fails at <100 iterations on multiple boards with peripherals connected through MOSHI USB-C dock

Project Member Reported by pgangishetty@google.com, Nov 19 
Chrome/OS Version: M71 & M72

DUTs used - Nocturne, Vayne & Pantheon
Peripherals - External monitor, KB & mouse
Docking station - MOSHI compact USB-C dock

What steps will reproduce the problem?
(1) Connect above peripherals to DUT through Moshi docking hub
(2) Run suspend_stress_test from crosh terminal for max iterations (sudo suspend_stress_test --suspend_max=70 --suspend_min=60 --wake_max=60 --wake_min=70) 
(3)Observe the test (test ran over the weekend)

What is the expected result?
Successful test completion without any errors.


What happens instead?
Test ran for <100 iterations. 
Pantheon --> 24 iterantions
Nocturne --> 98
Vayne --> 95

Note: Logs attached.

Comment 2 by tbroch@google.com, Dec 19

Cc: puthik@chromium.org
Owner: mqg@chromium.org
Status: Assigned (was: Untriaged)
Summary: vayne/pantheon/nocturne: Suspend_stress_test fails at <100 iterations on multiple boards with peripherals connected through MOSHI USB-C dock (was: Suspend_stress_test fails at <100 iterations on multiple boards with peripherals connected through MOSHI USB-C dock)
Pantheon failure looks like device failed to suspend returning EBUSY (errno:-16)

from var/log/messages.1

2018-11-17T01:44:42.056524+00:00 NOTICE powerd_suspend[22437]: --- begin /sys/kernel/debug/suspend_stats ---
2018-11-17T01:44:42.061255+00:00 NOTICE powerd_suspend[22442]: success: 23
2018-11-17T01:44:42.061268+00:00 NOTICE powerd_suspend[22442]: fail: 2
2018-11-17T01:44:42.061275+00:00 NOTICE powerd_suspend[22442]: failed_freeze: 0
2018-11-17T01:44:42.061281+00:00 NOTICE powerd_suspend[22442]: failed_prepare: 0
2018-11-17T01:44:42.061287+00:00 NOTICE powerd_suspend[22442]: failed_suspend: 0
2018-11-17T01:44:42.061294+00:00 NOTICE powerd_suspend[22442]: failed_suspend_late: 0
2018-11-17T01:44:42.061300+00:00 NOTICE powerd_suspend[22442]: failed_suspend_noirq: 2
2018-11-17T01:44:42.061335+00:00 NOTICE powerd_suspend[22442]: failed_resume: 0
2018-11-17T01:44:42.061365+00:00 NOTICE powerd_suspend[22442]: failed_resume_early: 0
2018-11-17T01:44:42.061393+00:00 NOTICE powerd_suspend[22442]: failed_resume_noirq: 0
2018-11-17T01:44:42.061425+00:00 NOTICE powerd_suspend[22442]: failures:
2018-11-17T01:44:42.061452+00:00 NOTICE powerd_suspend[22442]:   last_failed_dev: 
2018-11-17T01:44:42.061482+00:00 NOTICE powerd_suspend[22442]:   last_failed_errno: -16
2018-11-17T01:44:42.061522+00:00 NOTICE powerd_suspend[22442]:    -16
2018-11-17T01:44:42.061551+00:00 NOTICE powerd_suspend[22442]:   last_failed_step: suspend_noirq
2018-11-17T01:44:42.061564+00:00 NOTICE powerd_suspend[22442]:    suspend_noirq
2018-11-17T01:44:42.062187+00:00 NOTICE powerd_suspend[22448]: --- end /sys/kernel/debug/suspend_stats ---
2018-11-17T01:44:42.065165+00:00 NOTICE powerd_suspend[22453]: wakeup_count is 68
2018-11-17T01:44:42.068354+00:00 NOTICE powerd_suspend[22457]: Enabling Bluetooth HCI mode change event after resume

Menqgi can you have a deeper look?
►

Sign in to add a comment