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

Issue 826986 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

link: firmware spew on suspend_stress_test

Project Member Reported by kirtika@google.com, Mar 29 2018

Issue description

suspend_stress_test -c N ( 1 < N < 5) is flaky on my borrowed link. 
/sys/firmware/log has this error: CBFS: ERROR: No file header found at fffff980, attempting to recover by searching for header
Is this WAI?


localhost ~ # suspend_stress_test -c 1                                                                                                                                                                                                                                                   
Running 1 iterations with:
  suspend: 5-10 seconds
  wake: 5-10 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: 
  pm_print_times:  true
powerd start/running, process 3749
tlsdated stop/waiting
Suspend     1 of 1: sleep for  8 seconds...CBFS: ERROR: No file header found at fffff980, attempting to recover by searching for header
Firmware error found.

powerd start/running, process 4038
tlsdated start/running, process 4048

Finished 1 iterations.
Suspend_failures: 0
Firmware log errors: 1

 

Comment 1 by kirtika@google.com, Mar 29 2018

This is on R66-10452.22.0, and the reason I care about link (or 3.8 devices) is this RVG bug: https://bugs.chromium.org/p/chromium/issues/detail?id=826900

Comment 2 by tbroch@chromium.org, Mar 29 2018

Seems to work fine (-c 10 ) on test lab device running R67-10522.0.0.

Perhaps something specific to your borrowed device.  
Is your FW up-to-date?
Does failure repro w/ 'cbmem -1'?
Perhaps try --nofw_errors_fatal as a workaround.
Status: WontFix (was: Untriaged)
Closing as I'm assuming its a one-off on your device.  Please re-open if you think there's something to pursue here.

Sign in to add a comment