Issue metadata
Sign in to add a comment
|
[Eve] Kernel crash logs not generated in /var/spool/crash |
||||||||||||||||||||||||
Issue description
OS: ChromeOS R64-10176.74.0 (Official Build) stable-channel eve
What steps will reproduce the problem?
1) Recover device with R64-10176.74.0
2) Log into User Account
3) Open VT2 or crosh shell
4) Execute: echo BUG > /sys/kernel/debug/provoke-crash/DIRECT
a) Or Alt + F10 + X
5) Wait for system to restart
6) Look for crashes in /var/spool/crash
What is the expected result?
.kcrash and .meta files should be present after a crash
What happens instead?
No .kcrash or .meta kernal crash files are in /var/spool/crash
Notes:
- Original issue I filed which is marked as fixed: https://bugs.chromium.org/p/chromium/issues/detail?id=777985
- Issue does not occur on R65 or R66
As per Stainless, this was working with R64-10176.69.0:
https://stainless.corp.google.com/search?view=list&first_date=2018-02-09&last_date=2018-02-22&suite=usb_detect&test=logging_GenerateCrashFiles.KERNEL&build=%5ER64&board=%5Eeve%24&status=GOOD&status=WARN&status=FAIL&status=ERROR&exclude_cts=false&exclude_not_run=false&exclude_non_release=false&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true
,
Feb 22 2018
,
Feb 22 2018
Looks like this issue not fixed on R64 https://stainless.corp.google.com/search?view=matrix&row=build&col=board&first_date=2018-01-01&last_date=2018-02-22&suite=usb_detect&test=logging_GenerateCrashFiles.KERNEL&build=R64-*&exclude_cts=false&exclude_not_run=true&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true
,
Feb 22 2018
As per crbug.com/777985#c37 this issue is fixed on Eve BIOS 9584.107.0 @Matt, Can you please confirm the bios version for M64 build.
,
Feb 22 2018
From crossystem:
fwid: 9584.107.0
ro_fwid: 9584.76.0
,
Feb 22 2018
Few recent builds passed the test - R64-10176.62.0 and R64-10176.69.0 What did made it passed? How correct is the build image on the boards 1) you tested manually 2) in high-touch lab we have Do they need FW update?
,
Feb 22 2018
$ ssh root@chromeos1-row1-rack4-host6 "crossystem | grep fwid" fwid = Google_Eve.9584.107.0 # Active firmware ID ro_fwid = Google_Eve.9584.107.0 # Read-only firmware ID Looks like the firmware is updated on the eve device in the lab
,
Feb 22 2018
Can we have a bit more context for the M64 block? Impacts eve only? Confirmed regression for M64 (it worked in M63)? Have we been able to confirm this as an issue, or still investigating?
,
Feb 22 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by matthewjoseph@chromium.org
, Feb 22 2018