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: #1777716)
- ipmi_ssif: Fix kernel panic at msg_done_handler
* Update to ocxl driver for 18.04.1 (LP: #1775786)
- misc: ocxl: use put_device() instead of device_unregister()
- powerpc: Add TIDR CPU feature for POWER9
- powerpc: Use TIDR CPU feature to control TIDR allocation
- powerpc: use task_pid_nr() for TID allocation
- ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action
- ocxl: Expose the thread_id needed for wait on POWER9
- ocxl: Add an IOCTL so userspace knows what OCXL features are available
- ocxl: Document new OCXL IOCTLs
- ocxl: Fix missing unlock on error in afu_ioctl_enable_p9_wait()
* Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after
suspend (LP: #1776887)
- ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL
* Hard LOCKUP observed on stressing Ubuntu 18 04 (LP: #1777194)
- powerpc: use NMI IPI for smp_send_stop
- powerpc: Fix smp_send_stop NMI IPI handling
* IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on
CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n (LP: #1773964)
- rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709)
- SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm
stress-ng: Corrupt inode bitmap"
- SAUCE: ext4: check for allocation block validity with block group locked
linux (4.15.0-28.30) bionic; urgency=medium
* linux: 4.15.0-28.30 -proposed tracker (LP: #1781433)
* Cannot set MTU higher than 1500 in Xen instance (LP: #1781413)
- xen-netfront: Fix mismatched rtnl_unlock
- xen-netfront: Update features after registering netdev
linux (4.15.0-27.29) bionic; urgency=medium
* linux: 4.15.0-27.29 -proposed tracker (LP: #1781062)
* [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99:
comm stress-ng: Corrupt inode bitmap (LP: #1780137)
- SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode
bitmap
linux (4.15.0-26.28) bionic; urgency=medium
* linux: 4.15.0-26.28 -proposed tracker (LP: #1780112)
* failure to boot with linux-image-4.15.0-24-generic (LP: #1779827) // Cloud-
init causes potentially huge boot delays with 4.15 kernels (LP: #1780062)
- random: Make getrandom() ready earlier
linux (4.15.0-25.27) bionic; urgency=medium
* linux: 4.15.0-25.27 -proposed tracker (LP: #1779354)
* hisi_sas_v3_hw: internal task abort: timeout and not done. (LP: #1777736)
- scsi: hisi_sas: Update a couple of register settings for v3 hw
* hisi_sas: Add missing PHY spinlock init (LP: #1777734)
- scsi: hisi_sas: Add missing PHY spinlock init
* hisi_sas: improve read performance by pre-allocating slot DMA buffers
(LP: #1777727)
- scsi: hisi_sas: use dma_zalloc_coherent()
- scsi: hisi_sas: Use dmam_alloc_coherent()
- scsi: hisi_sas: Pre-allocate slot DMA buffers
* hisi_sas: Failures during host reset (LP: #1777696)
- scsi: hisi_sas: Only process broadcast change in phy_bcast_v3_hw()
- scsi: hisi_sas: Fix the conflict between dev gone and host reset
- scsi: hisi_sas: Adjust task reject period during host reset
- scsi: hisi_sas: Add a flag to filter PHY events during reset
- scsi: hisi_sas: Release all remaining resources in clear nexus ha
* Fake SAS addresses for SATA disks on HiSilicon D05 are non-unique
(LP: #1776750)
- scsi: hisi_sas: make SAS address of SATA disks unique
* Vcs-Git header on bionic linux source package points to zesty git tree
(LP: #1766055)
- [Packaging]: Update Vcs-Git
* large KVM instances run out of IRQ routes (LP: #1778261)
- SAUCE: kvm -- increase KVM_MAX_IRQ_ROUTES to 2048 on x86
-- Stefan Bader <stefan.ba...@canonical.com> Tue, 17 Jul 2018 10:57:50
+0200
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770244
Title:
Decode ARM CPER records in kernel
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[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 just tell the user what the problem is.
[Test Case]
On a server that supports EINJ, generate a fake CE (thanks to Tyler Baicar
for this example):
modprobe einj
echo 0x12345000 > /sys/kernel/debug/apei/einj/param1
echo $((-1 << 12)) > /sys/kernel/debug/apei/einj/param2
echo 5 > /sys/kernel/debug/apei/einj/param3
echo 0x3 > /sys/kernel/debug/apei/einj/flags
echo 0x1 > /sys/kernel/debug/apei/einj/error_type
echo 1 > /sys/kernel/debug/apei/einj/error_inject
In the output, look for a decoded message. Without this fix, you'll see:
[ 388.094304] {2}[Hardware Error]: error_info: 0x0000000004c6007f
[ 388.094341] {2}[Hardware Error]: physical fault address:
0x0000000012345000
But with the fix, you'll see:
[ 388.094304] {2}[Hardware Error]: error_info: 0x0000000004c6007f
[ 388.094317] {2}[Hardware Error]: transaction type: Generic
[ 388.094322] {2}[Hardware Error]: operation type: Generic read (type of
instruction or data request cannot be determined)
[ 388.094326] {2}[Hardware Error]: cache level: 3
[ 388.094330] {2}[Hardware Error]: processor context not corrupted
[ 388.094333] {2}[Hardware Error]: the error has been corrected
[ 388.094337] {2}[Hardware Error]: PC is imprecise
[ 388.094341] {2}[Hardware Error]: physical fault address:
0x0000000012345000
[Fix]
These upstream fixes add ARM decoding support:
c6d8c8ef1d0d94fdae9f5d72982963db89f9cdad efi: Move ARM CPER code to new
file
301f55b1a9177132d2b9ce8a90bf0ae4b37bb850 efi: Parse ARM error
information value
[Regression Risk]
The code changed is specific to ARM, and has been tested there. There's a
small change to arch-independent code, but it just involves renaming an array
and adding the obviously correct const attribute.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
