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

Issue 795035 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
matthewjoseph@chromium.org
ka...@chromium.org
sontis@chromium.org
█ patricia@chromium.org
dchan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[usb_detect: Eve & Rikku] logging_GenerateCrashFiles.KERNEL test is failing with ' set(['kcrash', 'meta']) files not generated'

Project Member Reported by pgangishetty@chromium.org, Dec 14 2017

Comment 1 by ka...@chromium.org, Dec 14 2017 

There are few possibilities here, but I see we are checking for crash files fairly soon after provoking the kernel crash - 37 seconds.

12/14 09:36:50.226 DEBUG|          ssh_host:0301| Running (ssh) 'echo BUG > /sys/kernel/debug/provoke-crash/DIRECT' from 'execute|_call_run_once_with_retry|_call_run_once|run_once|run|run_very_slowly'
12/14 09:37:16.669 DEBUG|             utils:0280| [stderr] Write failed: Broken pipe
12/14 09:37:16.671 DEBUG|logging_GenerateCr:0067| Crash invoked!
12/14 09:37:16.671 DEBUG|             utils:0212| Running 'ping chromeos1-row1-rack4-host6 -w1 -c1'
12/14 09:37:16.769 DEBUG|             utils:0280| [stdout] PING chromeos1-row1-rack4-host6.cros.corp.google.com (172.27.212.87) 56(84) bytes of data.
12/14 09:37:16.770 DEBUG|             utils:0280| [stdout] 64 bytes from 172.27.212.87: icmp_seq=1 ttl=59 time=0.655 ms
12/14 09:37:16.770 DEBUG|             utils:0280| [stdout] 
12/14 09:37:16.770 DEBUG|             utils:0280| [stdout] --- chromeos1-row1-rack4-host6.cros.corp.google.com ping statistics ---
12/14 09:37:16.770 DEBUG|             utils:0280| [stdout] 1 packets transmitted, 1 received, 0% packet loss, time 0ms
12/14 09:37:16.770 DEBUG|             utils:0280| [stdout] rtt min/avg/max/mdev = 0.655/0.655/0.655/0.000 ms
12/14 09:37:16.783 DEBUG|          ssh_host:0301| Running (ssh) 'sync' from 'execute|_call_run_once_with_retry|_call_run_once|run_once|run|run_very_slowly'
12/14 09:37:27.221 DEBUG|          ssh_host:0301| Running (ssh) 'ls /var/spool/crash' from '_call_run_once_with_retry|_call_run_once|run_once|check_missing_crash_files|run|run_very_slowly'
12/14 09:37:27.541 INFO |logging_GenerateCr:0035| Crash files diff: set([])
12/14 09:37:27.542 DEBUG|              test:0410| Test failed due to set(['kcrash', 'meta']) files not generated.. Exception log follows the after_iteration_hooks.


AI_1: Check if kernel crash files are generated on Eve manually.

AI_2: Add a sleep time(just like line 74) before executing 'sync' at https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/server/site_tests/logging_GenerateCrashFiles/logging_GenerateCrashFiles.py?l=73
run the test locally and see if test is passing.

Comment 2 by ka...@chromium.org, Dec 14 2017 

For rikku board the failure is strongly flaky and it seems there are kcrash files in logs with timestamp 30 seconds after crash files check.

We should definitely add a wait or a timeout for the check.


Matt found out eve board is not generating crash files, and Prasanthi is double checking on this.
For Eve, lets reopen the old bug Matt created 3-4 months ago.

Comment 3 by pgangishetty@chromium.org, Dec 14 2017 

Checked manually and I do not see crash files generated on Eve for kernel crashes.

Comment 4 by matthewjoseph@chromium.org, Dec 14 2017 

I also manually verified no kcrash files generated on 10176.11.0.  Also noticed that the console-ramoops file is not present after the initial crash in /sys/fs/pstore or /dev/pstore.

Looked at the diff: https://crosland.corp.google.com/log/10132.0.0..10137.0.0

..and it appears that the fix for 777985 (Disable VMX extensions) was recently re-enabled with:
https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/4c7496b123895690a18ddd242ce52345ec50d4b9
►

Sign in to add a comment