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

Issue 644818 link

Starred by 1 user

Issue metadata

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

Blocking:
issue 645710



Sign in to add a comment

cyan-chrome-pfq provision_Autoupdate flake

Project Member Reported by achuith@chromium.org, Sep 7 2016

Issue description

Failing build:
https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/141

It looks like a bug wasn't automatically filed for some reason.

Not sure if this is related to http://crbug.com/641424

 
Status log:

stdout:
  dm:dm bht[DEBUG] Setting block_count 448000
  dm:dm bht[DEBUG] Setting depth to 3.
  dm:dm bht[DEBUG] depth: 0 entries: 1
  dm:dm bht[DEBUG] depth: 1 entries: 28
  dm:dm bht[DEBUG] depth: 2 entries: 3500
  Traceback (most recent call last):
    File "/usr/local/autotest/client/common_lib/test.py", line 804, in _call_test_function
      return func(*args, **dargs)
    File "/usr/local/autotest/client/common_lib/test.py", line 461, in execute
      dargs)
    File "/usr/local/autotest/client/common_lib/test.py", line 347, in _call_run_once_with_retry
      postprocess_profiled_run, args, dargs)
    File "/usr/local/autotest/client/common_lib/test.py", line 376, in _call_run_once
      self.run_once(*args, **dargs)
    File "/usr/local/autotest/server/site_tests/provision_AutoUpdate/provision_AutoUpdate.py", line 147, in run_once
      force_full_update=force)
    File "/usr/local/autotest/server/afe_utils.py", line 239, in machine_install_and_update_labels
      image_name, host_attributes = host.machine_install(*args, **dargs)
    File "/usr/local/autotest/server/hosts/cros_host.py", line 836, in machine_install
      updater.run_update()
    File "/usr/local/autotest/site-packages/statsd/timer.py", line 95, in _decorator
      return function(*args, **kwargs)
    File "/usr/local/autotest/client/common_lib/cros/autoupdater.py", line 515, in run_update
      self.revert_boot_partition()
    File "/usr/local/autotest/client/common_lib/cros/autoupdater.py", line 400, in revert_boot_partition
      return self._run('/postinst %s 2>&1' % part)
    File "/usr/local/autotest/client/common_lib/cros/autoupdater.py", line 301, in _run
      return self.host.run(cmd, *args, **kwargs)
    File "/usr/local/autotest/server/hosts/ssh_host.py", line 190, in run
      options, stdin, args, ignore_timeout)
    File "/usr/local/autotest/server/hosts/ssh_host.py", line 157, in _run
      raise error.AutoservRunError("command execution error", result)
  AutoservRunError: command execution error
  * Command: 
      /usr/bin/ssh -a -x    -o ControlPath=/tmp/_autotmp_IU7Gr3ssh-
      master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
      -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o
      ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22
      chromeos4-row12-rack11-host1 "export LIBC_FATAL_STDERR_=1; if type
      \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\"
      \"server[stack::run_update|revert_boot_partition|_run] ->
      ssh_run(/postinst /dev/mmcblk0p3 2>&1)\";fi; /postinst /dev/mmcblk0p3
      2>&1"
  Exit status: 255
  Duration: 1080.55535603
  
  stdout:
  dm:dm bht[DEBUG] Setting block_count 448000
  dm:dm bht[DEBUG] Setting depth to 3.
  dm:dm bht[DEBUG] depth: 0 entries: 1
  dm:dm bht[DEBUG] depth: 1 entries: 28
  dm:dm bht[DEBUG] depth: 2 entries: 3500
  
	END FAIL	provision_AutoUpdate	provision_AutoUpdate	timestamp=1473232530	localtime=Sep 07 00:15:30	
Cc: -dshi@chromium.org gwendal@chromium.org
Gwendal, does this seem like the stale firmware that doesn't have MMC fix issue?

[  907.012209] mmc0: Timeout waiting for hardware interrupt.
[  907.012229] sdhci: =========== REGISTER DUMP (mmc0)===========
[  907.012243] sdhci: Sys addr: 0x00000200 | Version:  0x00001002
[  907.012257] sdhci: Blk size: 0x00007200 | Blk cnt:  0x00000180
[  907.012270] sdhci: Argument: 0x006a2100 | Trn mode: 0x0000003b
[  907.012283] sdhci: Present:  0x1fff0206 | Host ctl: 0x00000035
[  907.012296] sdhci: Power:    0x0000000b | Blk gap:  0x00000080
[  907.012309] sdhci: Wake-up:  0x00000000 | Clock:    0x00000007
[  907.012322] sdhci: Timeout:  0x00000005 | Int stat: 0x00000000
[  907.012335] sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[  907.012348] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[  907.012361] sdhci: Caps:     0x446cc8b2 | Caps_1:   0x00000807
[  907.012374] sdhci: Cmd:      0x0000123a | Max curr: 0x00000000
[  907.012386] sdhci: Host ctl2: 0x0000008b
[  907.012396] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x78d26008
[  907.012407] sdhci: ===========================================
[  907.014449] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
[  907.014466] sdhci: =========== REGISTER DUMP (mmc0)===========
[  907.014497] sdhci: Sys addr: 0x00000200 | Version:  0x00001002
[  907.014527] sdhci: Blk size: 0x00007200 | Blk cnt:  0x00000180
[  907.014561] sdhci: Argument: 0x00000000 | Trn mode: 0x00000033
[  907.014596] sdhci: Present:  0x1fff0000 | Host ctl: 0x00000035
[  907.014631] sdhci: Power:    0x0000000b | Blk gap:  0x00000080
[  907.014651] sdhci: Wake-up:  0x00000000 | Clock:    0x00000007
[  907.014664] sdhci: Timeout:  0x00000005 | Int stat: 0x00000000
[  907.014678] sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[  907.014691] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[  907.014704] sdhci: Caps:     0x446cc8b2 | Caps_1:   0x00000807
[  907.014717] sdhci: Cmd:      0x00000c1a | Max curr: 0x00000000
[  907.014729] sdhci: Host ctl2: 0x0000008b
[  907.014739] sdhci: ADMA Err: 0x00000001 | ADMA Ptr: 0x78d26008
console-ramoops.txt
127 KB View Download
On the next run HWTest fails like:
https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/142/steps/HWTest%20%5Barc-bvt-cq%5D/logs/stdio

 provision                                                         [ FAILED ]
  provision                                                           FAIL: Failed to install device image using payload at http://100.115.219.131:8082/update/cyan-chrome-pfq/R55-8779.0.0-rc1 on chromeos4-row12-rack11-host1. SSH reports a generic error (255) which is probably a lab network failure
 
Blocking: 645710
Components: Infra>Client>ChromeOS

Comment 6 by cindyb@chromium.org, May 31 2018

Hi, this bug has not been updated recently and remains untriaged. Please acknowledge the bug and provide status within two weeks (6/8/2018), or the bug will be closed. Thank you.
Status: Archived (was: Untriaged)

Sign in to add a comment