moblab: firmware_ConsecutiveBoot test failed due to moblab reboot( kernel Panic) |
||
Issue descriptionType of hardware : ultima PVT SKU5 Chrome OS Version : 9173.0.0 (Official Build) dev-channel ultima test BIOS VERSION : Google_Ultima.7287.131.21 / Google_Ultima.7287.131.63 EC Version : ultima_v1.1.3595-26c4cdd / ultima_v1.1.3599-994205e PD Version : N/A CPU arch : x86_64 CPU model : Intel(R) Celeron(R) CPU N3150 @ 1.60GHz CPU speed : 2165.8000 Total Memory : 3989572 kB Memory Type : 1-44: Micron Technology | 00000000 | EDF8132A3MA-JD-F MMC Model : AGND3R MMC Firmware : 0x0100000000000000 Moblab 4 : Test tracker test case: https://testtracker.googleplex.com/efforts/testcase/detail/10639301?tp_id=382&result=&environment= Source Branch: MOBLAB (R55-8872.73.0) Test location: moblab Test command: test_that -b {BOARD_NAME} {device IP} f:.*firmware_ConsecutiveBoot/control.2500 Steps to reproduce the issue: 1. Run firmware_ConsecutiveBoot test for 2500 iterations test_that -b {BOARD_NAME} {device IP} f:.*firmware_ConsecutiveBoot/control.2500 - What is the expected result? Test should PASS - What was observed instead? Test failed due to moblab reboot (257 | 2017-01-18 18:43:15 | Kernel Event | Panic) Moblab eventlog: 252 | 2017-01-18 10:58:39 | Power Button Override 253 | 2017-01-18 10:58:39 | System Reset 254 | 2017-01-18 10:58:39 | Wake Source | Power Button | 0 255 | 2017-01-18 10:58:39 | Wake Source | GPIO | 27 256 | 2017-01-18 10:58:40 | Chrome OS Developer Mode 257 | 2017-01-18 18:43:15 | Kernel Event | Panic 258 | 2017-01-18 18:43:16 | System boot | 621 259 | 2017-01-18 18:43:16 | System Reset 260 | 2017-01-18 18:43:16 | Wake Source | GPIO | 27 261 | 2017-01-18 18:43:16 | Chrome OS Developer Mode
,
Jan 19 2017
seen the same issue in another moblab (moblab5).
,
Jan 19 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by venkatar...@chromium.org
, Jan 19 2017