diff options
| author | Ryan Grimm <grimm@linux.vnet.ibm.com> | 2018-05-04 14:06:41 +1000 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.ibm.com> | 2018-05-04 03:25:05 -0500 |
| commit | eddff9bf40cfbd6e2ac36012607173e6e299267a (patch) | |
| tree | 91566e9b15e06e346b76ff0132be50ab3d61e79c /.travis.yml | |
| parent | 854bf69e1c7df94edd3b97266739623e85098496 (diff) | |
| download | skiboot-eddff9bf40cfbd6e2ac36012607173e6e299267a.zip skiboot-eddff9bf40cfbd6e2ac36012607173e6e299267a.tar.gz skiboot-eddff9bf40cfbd6e2ac36012607173e6e299267a.tar.bz2 | |
hmi: Clear unknown debug trigger
On some systems, seeing hangs like this when Linux starts:
[ 170.027252763,5] OCC: All Chip Rdy after 0 ms
[ 170.062930145,5] INIT: Starting kernel at 0x20011000, fdt at 0x30ae0530 366247 bytes)
[ 171.238270428,5] OPAL: Switch to little-endian OS
If you look at the in memory skiboot console (or do 'nvram -p
ibm,skiboot --update-config log-level-driver=7') we see the console get
spammed with:
[ 5209.109790675,7] HMI: Received HMI interrupt: HMER = 0x0000400000000000
[ 5209.109792716,7] HMI: Received HMI interrupt: HMER = 0x0000400000000000
[ 5209.109794695,7] HMI: Received HMI interrupt: HMER = 0x0000400000000000
[ 5209.109796689,7] HMI: Received HMI interrupt: HMER = 0x0000400000000000
We're taking the debug trigger (bit 17) early on, before the
hmi_debug_trigger function in the kernel is set up.
This clears the HMI in Skiboot and reports to the kernel instead of
bringing down the machine.
Signed-off-by: Ryan Grimm <grimm@linux.vnet.ibm.com>
Signed-off-by: Michael Neuling <mikey@neuling.org>
Reviewed-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Diffstat (limited to '.travis.yml')
0 files changed, 0 insertions, 0 deletions