[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180403170830.29282-5-mr.nuke.me@gmail.com>
Date: Tue, 3 Apr 2018 12:08:30 -0500
From: Alexandru Gagniuc <mr.nuke.me@...il.com>
To: linux-acpi@...r.kernel.org
Cc: rjw@...ysocki.net, lenb@...nel.org, tony.luck@...el.com,
bp@...en8.de, tbaicar@...eaurora.org, will.deacon@....com,
james.morse@....com, shiju.jose@...wei.com, zjzhang@...eaurora.org,
gengdongjiu@...wei.com, linux-kernel@...r.kernel.org,
alex_gagniuc@...lteam.com, austin_bolen@...l.com,
shyam_iyer@...l.com, Alexandru Gagniuc <mr.nuke.me@...il.com>
Subject: [RFC PATCH 4/4] acpi: apei: Warn when GHES marks correctable errors as "fatal"
There seems to be a culture amongst BIOS teams to want to crash the
OS when an error can't be handled in firmware. Marking GHES errors as
"fatal" is a very common way to do this.
However, a number of errors reported by GHES may be fatal in the sense
a device or link is lost, but are not fatal to the system. When there
is a disagreement with firmware about the handleability of an error,
print a warning message.
Signed-off-by: Alexandru Gagniuc <mr.nuke.me@...il.com>
---
drivers/acpi/apei/ghes.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
index 7243a99ea57e..d9123c5fa3d9 100644
--- a/drivers/acpi/apei/ghes.c
+++ b/drivers/acpi/apei/ghes.c
@@ -521,6 +521,11 @@ static int ghes_do_proc(struct ghes *ghes,
corrected_sev = max(corrected_sev, sec_sev);
}
+
+ if ((sev >= GHES_SEV_PANIC) && (corrected_sev < sev)) {
+ pr_warn("FIRMWARE BUG: Firmware sent fatal error that we were able to correct");
+ pr_warn("BROKEN FIRMWARE: Complain to your hardware vendor");
+ }
return corrected_sev;
}
--
2.14.3
Powered by blists - more mailing lists