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

Issue 827232 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 782857
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

logging_UdevCrash HWTest failure on caroline-tot-chrome-pfq-informational

Project Member Reported by afakhry@chromium.org, Mar 29 2018

Issue description

The FYI builder https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/caroline-tot-chrome-pfq-informational/builds/1328 failed the HWTest [bvt-cq] step due to the following error:

03/29 09:51:57.207 WARNI|              test:0637| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 631, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 831, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 495, in execute
    dargs)
  File "/usr/local/autotest/common_lib/test.py", line 362, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 400, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/logging_UdevCrash/logging_UdevCrash.py", line 91, in run_once
    self.run_crash_tests(['udev_report_atmel'], True)
  File "/usr/local/autotest/cros/crash/crash_test.py", line 711, in run_crash_tests
    getattr(self, '_test_' + test_name)()
  File "/usr/local/autotest/tests/logging_UdevCrash/logging_UdevCrash.py", line 87, in _test_udev_report_atmel
    exception=error.TestFail('No valid Atmel crash reports'))
  File "/usr/local/autotest/common_lib/utils.py", line 2724, in poll_for_condition
    value = condition()
  File "/usr/local/autotest/tests/logging_UdevCrash/logging_UdevCrash.py", line 49, in CheckAtmelCrashes
    'content %s' % bad_lines)
TestFail: Crash report contains invalid content ['2018-03-29T09:47:28.173295-07:00 DEBUG kernel: [    0.581015] acpi ATML0001:00: GPIO: looking up atmel,reset-gpios', '2018-03-29T09:47:28.173300-07:00 DEBUG kernel: [    0.581019] acpi ATML0001:00: GPIO: looking up atmel,reset-gpio', '2018-03-29T09:47:28.173744-07:00 DEBUG kernel: [    0.816849] acpi ATML0000:00: GPIO: looking up atmel,reset-gpios', '2018-03-29T09:47:28.173755-07:00 DEBUG kernel: [    0.816854] acpi ATML0000:00: GPIO: looking up atmel,reset-gpio']


Looking at /var/log/messages, the following logs are found:

2018-03-29T09:51:56.893478-07:00 ERR crash_reporter[9750]: Signature does not match the data or can not be verified!
2018-03-29T09:51:56.893537-07:00 ERR crash_reporter[9750]: Policy signature verification failed!
2018-03-29T09:51:56.893609-07:00 ERR crash_reporter[9749]: Signature does not match the data or can not be verified!
2018-03-29T09:51:56.893657-07:00 ERR crash_reporter[9749]: Policy signature verification failed!
2018-03-29T09:51:56.894292-07:00 INFO crash_reporter[9750]: Consent given - collect udev crash info.
2018-03-29T09:51:56.894526-07:00 INFO crash_reporter[9749]: Consent given - collect udev crash info.
2018-03-29T09:51:57.171179-07:00 WARNING crash_reporter[9750]: Error writing sanitized log to /var/spool/crash/change__i2c_atmel_mxt_ts.20180329.095156.0.log
2018-03-29T09:51:57.171206-07:00 ERR crash_reporter[9750]: Error reading udev log info crash_reporter-udev-collection-change--i2c-atmel_mxt_ts
2018-03-29T09:51:57.178468-07:00 WARNING kernel: [  269.584336] udevd[9748]: Process '/sbin/crash_reporter --udev=SUBSYSTEM=i2c-atmel_mxt_ts:ACTION=change' failed with exit code 1.


vapier@ can you please take a look?
 

Comment 1 by vapier@chromium.org, Mar 29 2018

Labels: -Restrict-View-Google
Mergedinto: 782857
Status: Duplicate (was: Assigned)

Sign in to add a comment