This bug was fixed in the package linux - 4.15.0-29.31
---
linux (4.15.0-29.31) bionic; urgency=medium
* linux: 4.15.0-29.31 -proposed tracker (LP: #1782173)
* [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler
(LP: #116)
- ipmi_ssif: Fix kernel panic
This bug was fixed in the package linux - 4.15.0-24.26
---
linux (4.15.0-24.26) bionic; urgency=medium
* linux: 4.15.0-24.26 -proposed tracker (LP: #1776338)
* Bionic update: upstream stable patchset 2018-06-06 (LP: #1775483)
- drm: bridge: dw-hdmi: Fix overflow workaround
Verified:
[ 330.966942] EINJ: Error INJection is initialized.
[ 350.598563] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 2
[ 350.598586] {1}[Hardware Error]: It has been corrected by h/w and requires
no further action
[ 350.598589] {1}[Hardware Error]: event
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770244
Title:
Decode ARM CPER records in kernel
To manage
** Description changed:
[Impact]
When an ARM-specific platform error (CPER) comes occurs, the kernel will emit
an error with an opaque hex error type. The user would then need to consult the
UEFI specification to decode it. It is far easier for the kernel to do the
decoding itself, and
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Description changed:
[Impact]
- When an ARM-specific platform error (CPER) comes occurs, the kernel will emit
an error with an opaque hex
** Description changed:
[Impact]
- TBD
+ When an ARM-specific platform error (CPER) comes occurs, the kernel will emit
an error with an opaque hex error type. The user would then need to consult the
UEFI specification to decode it. It would be better to actually do the decoding
for the user
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Description changed:
[Impact]
TBD
[Test Case]
TBD
[Fix]
- TBD
+ c6d8c8ef1d0d94fdae9f5d72982963db89f9cdad
