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

Issue 731215 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 729621
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

[Rikku] cbmem crash observed at stress test

Project Member Reported by helenzhang@google.com, Jun 8 2017

Issue description

Google Chrome: 60.0.3112.10 (Official Build) dev (64-bit)
Platform: 9592.5.0 (Official Build) dev-channel rikku

What steps will reproduce the problem?
(1) Sign in 
(2) Run "sudo suspend_stress_test -c 70 --wake_min 90 --wake_max 1800 --suspend_min 900 --suspend_max 1800" 
(3) 

What is the expected result?
no crash 

What happens instead?
cbmem crashes 

output:
hronos@localhost / $ sudo suspend_stress_test -c 70 --wake_min 90 --wake_max 1800 --suspend_min 900 --suspend_max 1800
Running 70 iterations with:
  suspend: 900-1800 seconds
  wake: 90-1800 seconds
  backup_rtc: false
  errors_fatal: true
  fw_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 8354
tlsdated stop/waiting
Suspend     1 of 70: sleep for 1189 seconds...cbmem: cbmem.c:684: void dump_console(int): Assertion `!regcomp(&re, regex[i], 0)' failed.
Aborted (core dumped)

Settings:
- it has 2 monitors connected, with many usb peripherals like usb mouse/keyboard/webcam/usb stick/headphone
- it sets to run over weekend


crash id e.g.: 
9297a22e40000000
2e221caef0000000
client id: 
ee462eebe2cf4350a536cc59c5cff8cd 

 
Cc: rjahagir@chromium.org snanda@chromium.org ka...@chromium.org pgangishetty@chromium.org sontis@chromium.org
log: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/731215/

Comment 2 by son...@google.com, Jun 8 2017

Mergedinto: 729621
Status: Duplicate (was: Untriaged)

Comment 3 by ka...@chromium.org, Jun 8 2017

Summary: [Rikku] cbmem crash observed at stress test (was: [Rikku] cbmem kernel crash observed at stress test )
The parameters of wake and suspend timing were set on bigger values to picture more realistic scenario. (it should have been --wake_min 900, instead 90).
The crash does not affect the suspend-resume cycles.
Thanks sontis@ fro duplicating.

Sign in to add a comment