Bug 34446 - RX300S8: Hardware error from APEI Generic Hardware Error Source
RX300S8: Hardware error from APEI Generic Hardware Error Source
Status: RESOLVED WORKSFORME
Product: UCS
Classification: Unclassified
Component: Kernel
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-x
Assigned To: Kernel maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-03 11:33 CEST by Janis Meybohm
Modified: 2017-04-21 12:14 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 7: Crash: Bug causes crash or data loss
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.200
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2014040321000805
Bug group (optional):
Max CVSS v3 score:


Attachments
Screenshot of the APEI generic hardware error (2.37 MB, image/jpeg)
2014-04-03 11:33 CEST, Janis Meybohm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Janis Meybohm univentionstaff 2014-04-03 11:33:56 CEST
Created attachment 5849 [details]
Screenshot of the APEI generic hardware error

Ticket#: 2014040321000805

Customer reported UCS 3.2 is not booting on FTS RX300 S8 after recent BIOS Update (Changes BIOS V4.6.5.4 R1.6.0 for D2939-B1x; 12.02.2014).

Looks similar to the report here:
https://groups.google.com/forum/#!topic/fa.linux.kernel/ZBD_Ab1GWhM


Workaround:
Downgrade to previous BIOS version.
Comment 1 Nico Gulden univentionstaff 2014-05-07 10:55:24 CEST
I have feedback from Fujitsu. Their Debian certification partner recommends to start the system with the following kernel parameter set: ghes.disable=1
Comment 2 Philipp Hahn univentionstaff 2014-10-28 12:13:52 CET
Happened again also with Fujitsu BX920-S4: The installer silently reboots. With "verbose loglevel=8" the APEI error message is visible.
Comment 3 Philipp Hahn univentionstaff 2017-04-21 12:14:07 CEST
Might be fixed by v3.10-rc4~11^2.
UCS-3.2 is OoM.
Not reported again and workaround exists.