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

Issue 618020 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 617557
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

High number of test provision_AutoUpdate failures.

Project Member Reported by haddowk@chromium.org, Jun 7 2016

Issue description


High number of test provision failures.

06/07 10:49:26.076 ERROR|provision_AutoUpda:0138| Build R53-8423.0.0 failed to boot on chromeos4-row8-rack8-host14; system rolled back to previous build
06/07 10:49:26.078 WARNI|              test:0606| Autotest caught exception when running test:
Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  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 139, in run_once
    raise error.TestFail(str(e))
TestFail: Build R53-8423.0.0 failed to boot on chromeos4-row8-rack8-host14; system rolled back to previous build

Example jobs that failed with provision issues:

http://cautotest/afe/#tab_id=view_job&object_id=66036136

http://cautotest/afe/#tab_id=view_job&object_id=66037182

http://cautotest/afe/#tab_id=view_job&object_id=66037387

 
Owner: autumn@chromium.org
Status: Assigned (was: Untriaged)
Assigning to autumn@ for triage
Owner: ----
Status: Available (was: Assigned)
Reverting change in comment 1 so that this shows up in infra bug traige
Status: Untriaged (was: Available)
checking
Cc: vpalatin@chromium.org xixuan@chromium.org
Labels: -current-issue
Owner: sha...@chromium.org
Seems to be a boot failure on the DUT with the new software being tested. ChromeOS infra can help with log collection if they aren't showing up correctly + Xixuan as current deputy for that 
The update-engine log shows that:

rollback-version not present in /mnt/stateful_partition/unencrypted/preserve/update_engine/prefs, 

so seems it can't do roll back, and can't reboot from the updated version, so fail and fail again.
Looking at haddowk@'s tests, things were passing on edgar at 8406 and failing at 8409.

https://crosland.corp.google.com/log/8406.0.0..8409.0.0

So, I'll grab an edgar unit and try a 8409 install.

I assume that devices are provisioned by booting a test image and running chromeos-install?
the devices are provisioned by booting from a current image, check the status, if it's NEED_REBOOT, which shows that the DUTs have been successfully updated. So it will directly reboot to the updated image. If not, do update and then reboot. 

These DUTs's status is already NEED_REBOOT, but everytime they fail to reboot and can't do roll back. So it's a dead loop.
Mergedinto: 617557
Status: Duplicate (was: Untriaged)
I grabbed the panic log below from my Edgar after booting a TOT image. Looks like a dupe of  issue 617557 . I'll investigate more and post replies on that bug.

[   20.446316] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
[   20.446521] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[   20.446777] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[   20.473491] BUG: unable to handle kernel paging request at ffffffffc06b3def
[   20.473511] IP: [<ffffffff99223bf4>] strcpy+0xc/0x18
[   20.473528] PGD 19c1b067 PUD 19c1d067 PMD 166c25067 PTE 8000000166eb0161
[   20.473544] Oops: 0003 [#1] PREEMPT SMP
[   20.477156] gsmi: Log Shutdown Reason 0x03
[   20.477163] Modules linked in: snd_soc_sst_cht_bsw_rt5645(+) iwlmvm(+) memconsole_x86 memconsole btusb uvcvideo btrtl btbcm btintel snd_hda_codec_hdmi videobuf2_vmalloc videobuf2_memops videobuf2_core bluetooth snd_intel_sst_acpi snd_hda_intel iwlwifi snd_soc_rt5645 snd_hda_codec iwl7000_mac80211 snd_hwdep snd_hda_core snd_soc_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform snd_soc_rl6231 zram fuse cfg80211 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables joydev snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device ppp_async ppp_generic slhc tun
[   20.477286] CPU: 1 PID: 1465 Comm: udevd Tainted: G        W      3.18.0-12381-gaf3c754 #1
[   20.477298] Hardware name: GOOGLE Edgar, BIOS Google_Edgar.7287.167.2 03/03/2016
[   20.477310] task: ffff880077dc2d00 ti: ffff880167f88000 task.ti: ffff880167f88000
[   20.477321] RIP: 0010:[<ffffffff99223bf4>]  [<ffffffff99223bf4>] strcpy+0xc/0x18
[   20.477336] RSP: 0018:ffff880167f8bb98  EFLAGS: 00010246
[   20.477345] RAX: ffffffffc06b3def RBX: 0000000000000001 RCX: 0000000000000069
[   20.477356] RDX: 0000000000000000 RSI: ffff880167f8bbc0 RDI: ffffffffc06b3def
[   20.477367] RBP: ffff880167f8bb98 R08: 0000000000000003 R09: 000000000000ffff
[   20.477378] R10: 0000000000000001 R11: ffff88017b02aee8 R12: ffffffffc06b4100
[   20.477388] R13: ffff88017b29b010 R14: ffff88017b29b000 R15: ffff88007822b428
[   20.477400] FS:  00007fc5c425e780(0000) GS:ffff88017fd00000(0000) knlGS:0000000000000000
[   20.477412] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   20.477421] CR2: ffffffffc06b3def CR3: 0000000167f48000 CR4: 00000000001007e0
[   20.477431] Stack:
[   20.477436]  ffff880167f8bc08 ffffffffc06b2389 0000000000000001 0000000166eb7708
[   20.477452]  01ff880167f8bbf8 434530312d633269 0030303a30353635 000000003d30d8d1
[   20.477467]  0000000000000000 ffff88017b29b010 ffffffffc06b4028 ffffffffc06b4028
[   20.477482] Call Trace:
[   20.477493]  [<ffffffffc06b2389>] init_module+0x2f6389/0x2f63e5 [snd_soc_sst_cht_bsw_rt5645]
[   20.477510]  [<ffffffff993a9fc2>] platform_drv_probe+0x4b/0x91
[   20.477522]  [<ffffffff993a5592>] ? devices_kset_move_last+0x60/0x64
[   20.477534]  [<ffffffff993a8684>] driver_probe_device+0x109/0x2b1
[   20.477546]  [<ffffffff993a88f2>] __driver_attach+0x5e/0x81
[   20.477557]  [<ffffffff993a8894>] ? __device_attach_driver+0x68/0x68
[   20.477569]  [<ffffffff993a7755>] bus_for_each_dev+0x8c/0xaf
[   20.477580]  [<ffffffff993a8112>] driver_attach+0x1e/0x20
[   20.477590]  [<ffffffff993a7d9a>] bus_add_driver+0xeb/0x1e3
[   20.477601]  [<ffffffff993a90d5>] driver_register+0x8f/0xcc
[   20.477612]  [<ffffffffc03bc000>] ? 0xffffffffc03bc000
[   20.477623]  [<ffffffff993a9f3c>] __platform_driver_register+0x4a/0x4c
[   20.477636]  [<ffffffffc03bc017>] init_module+0x17/0x1000 [snd_soc_sst_cht_bsw_rt5645]
[   20.477650]  [<ffffffff990003b5>] do_one_initcall+0x188/0x19d
[   20.477663]  [<ffffffff991091ae>] ? __vunmap+0xac/0xb7
[   20.477675]  [<ffffffff990a0481>] load_module+0x15e4/0x1bb4
[   20.477687]  [<ffffffff990a0bd2>] SyS_finit_module+0x86/0xab
[   20.477700]  [<ffffffff99621e5c>] system_call_fastpath+0x1c/0x21
[   20.477709] Code: 9b 99 31 c0 e8 1a 84 3f 00 48 89 de 48 c7 c7 3a 76 99 99 31 c0 e8 09 84 3f 00 5b 41 5c 5d c3 55 48 89 f8 31 d2 48 89 e5 8a 0c 16 <88> 0c 10 48 ff c2 84 c9 75 f3 5d c3 55 48 89 f8 31 c9 48 89 e5
[   20.477811] RIP  [<ffffffff99223bf4>] strcpy+0xc/0x18
[   20.477822]  RSP <ffff880167f8bb98>
[   20.477828] CR2: ffffffffc06b3def
[   20.477836] ---[ end trace ea526d334ccae537 ]---
[   20.484295] Kernel panic - not syncing: Fatal exception
[   20.484311] Kernel Offset: 0x18000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[   20.484535] gsmi: Log Shutdown Reason 0x02
[   20.490974] ACPI MEMORY or I/O RESET_REG.

Cc: -mshe...@chromium.org

Sign in to add a comment