diff options
| author | Chen Gong <gong.chen@linux.intel.com> | 2012-11-05 22:11:26 -0500 |
|---|---|---|
| committer | Chen Gong <gong.chen@linux.intel.com> | 2012-11-07 01:43:43 -0500 |
| commit | b2e97bf75c5e22eedd05a3e2058baad96f1562af (patch) | |
| tree | d9dd139bf317da18cc666f45df4bd6d5096b6ba7 | |
| parent | ff1dcca1138df58e486c08884ab191a9c1b1c807 (diff) | |
| download | mce-test-b2e97bf75c5e22eedd05a3e2058baad96f1562af.tar.gz | |
add check for parameter notrigger in APEI/SRAR test case
On some platforms OS doesn't support parameter notrigger.
Under this kind of situation, injection procedure is dangerous
because it maybe causes sytem oops/crash. If no this parameter,
the test should be teminated.
Signed-off-by: Chen Gong <gong.chen@linux.intel.com>
| -rwxr-xr-x | cases/function/core_recovery/srar_recovery.sh | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/cases/function/core_recovery/srar_recovery.sh b/cases/function/core_recovery/srar_recovery.sh index c6d0c4d..e41ef82 100755 --- a/cases/function/core_recovery/srar_recovery.sh +++ b/cases/function/core_recovery/srar_recovery.sh @@ -42,7 +42,9 @@ if [ ! -d $g_debugfs/apei/einj ]; then modprobe einj param_extension=1 > /dev/null 2>&1 [ $? -eq 0 ] || invalid "module einj isn't supported?" fi -[ -f $g_debugfs/apei/einj/param1 ] || invalid "no BIOS extension support for APEI on this platform" +[ -f $g_debugfs/apei/einj/param1 ] || invalid "No BIOS extension support for APEI on this platform" +[ -f $g_debugfs/apei/einj/notrigger ] || + invalid "No parameter *notrigger*. Injection maybe causes system crash. Please check commit v3.3-3-gee49089" #check if the platform supports Uncorrectable non-fatal Memory Error injection cat $g_debugfs/apei/einj/available_error_type | grep -q $inject_type |