Observed this kernel panic on Coral system while sheriffing. Will try to see if there are more such instances from CQ runs.

Grant, could you check if we are getting reports of such panics from the field as well?  Marking it as a P2 for now since not sure how prevalent this issue is.

Kernel panic log here:
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/176964289-chromeos-test/chromeos2-row4-rack4-host5/sysinfo/var/spool/crash/

<4>[  534.372775] da7219 i2c-DLGS7219:00: SRM failed to lock
<0>[  558.589688] Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler
<0>[  559.647075] Shutting down cpus with NMI
<0>[  559.657666] Kernel Offset: 0x35e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
<0>[  559.659400] gsmi: Log Shutdown Reason 0x02
 

Deleted: kernel.20180215.043649.0.txt 79.0 KB

kernel.20180215.043649.0.txt 79.0 KB View Download