[Bug 1770244] Re: Decode ARM CPER records in kernel
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 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: #136) - scsi: hisi_sas: Update a couple of register settings for v3 hw * hisi_sas: Add missing PHY spinlock init (LP: #134) - scsi: hisi_sas: Add missing PHY spinlock init * hisi_sas: improve read performance by pre-allocating slot DMA buffers (LP: #127) - 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 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770244 Title: Decode ARM CPER records in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770244] Re: Decode ARM CPER records in kernel
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 for Amlogic Meson GX SoCs
- i40e: Fix attach VF to VM issue
- tpm: cmd_ready command can be issued only after granting locality
- tpm: tpm-interface: fix tpm_transmit/_cmd kdoc
- tpm: add retry logic
- Revert "ath10k: send (re)assoc peer command when NSS changed"
- bonding: do not set slave_dev npinfo before slave_enable_netpoll in
bond_enslave
- ipv6: add RTA_TABLE and RTA_PREFSRC to rtm_ipv6_policy
- ipv6: sr: fix NULL pointer dereference in seg6_do_srh_encap()- v4 pkts
- KEYS: DNS: limit the length of option strings
- l2tp: check sockaddr length in pppol2tp_connect()
- net: validate attribute sizes in neigh_dump_table()
- llc: delete timers synchronously in llc_sk_free()
- tcp: don't read out-of-bounds opsize
- net: af_packet: fix race in PACKET_{R|T}X_RING
- tcp: md5: reject TCP_MD5SIG or TCP_MD5SIG_EXT on established sockets
- net: fix deadlock while clearing neighbor proxy table
- team: avoid adding twice the same option to the event list
- net/smc: fix shutdown in state SMC_LISTEN
- team: fix netconsole setup over team
- packet: fix bitfield update race
- tipc: add policy for TIPC_NLA_NET_ADDR
- pppoe: check sockaddr length in pppoe_connect()
- vlan: Fix reading memory beyond skb->tail in skb_vlan_tagged_multi
- amd-xgbe: Add pre/post auto-negotiation phy hooks
- sctp: do not check port in sctp_inet6_cmp_addr
- amd-xgbe: Improve KR auto-negotiation and training
- strparser: Do not call mod_delayed_work with a timeout of LONG_MAX
- amd-xgbe: Only use the SFP supported transceiver signals
- strparser: Fix incorrect strp->need_bytes value.
- net: sched: ife: signal not finding metaid
- tcp: clear tp->packets_out when purging write queue
- net: sched: ife: handle malformed tlv length
- net: sched: ife: check on metadata length
- llc: hold llc_sap before release_sock()
- llc: fix NULL pointer deref for SOCK_ZAPPED
- net: ethernet: ti: cpsw: fix tx vlan priority mapping
- virtio_net: split out ctrl buffer
- virtio_net: fix adding vids on big-endian
- KVM: s390: force bp isolation for VSIE
- s390: correct module section names for expoline code revert
- microblaze: Setup dependencies for ASM optimized lib functions
- commoncap: Handle memory allocation failure.
- scsi: mptsas: Disable WRITE SAME
- cdrom: information leak in cdrom_ioctl_media_changed()
- m68k/mac: Don't remap SWIM MMIO region
- block/swim: Check drive type
- block/swim: Don't log an error message for an invalid ioctl
- block/swim: Remove extra put_disk() call from error path
- block/swim: Rename macros to avoid inconsistent inverted logic
- block/swim: Select appropriate drive on device open
- block/swim: Fix array bounds check
- block/swim: Fix IO error at end of medium
- tracing: Fix missing tab for hwlat_detector print format
- s390/cio: update chpid descriptor after resource accessibility event
- s390/dasd: fix IO error for newly defined devices
- s390/uprobes: implement arch_uretprobe_is_alive()
- ACPI / video: Only default only_lcd to true on Win8-ready _desktops_
- docs: ip-sysctl.txt: fix name of some ipv6 variables
- net: mvpp2: Fix DMA address mask size
- net: stmmac: Disable ACS Feature for GMAC >= 4
- l2tp: hold reference on tunnels in netlink dumps
- l2tp: hold reference on tunnels printed in pppol2tp proc file
- l2tp: hold reference on tunnels printed in l2tp/tunnels debugfs file
- l2tp: fix {pppol2tp, l2tp_dfs}_seq_stop() in case of seq_file overflow
- s390/qeth: fix error handling in adapter command callbacks
- s390/qeth: avoid control IO completion stalls
- s390/qeth: handle failure on workqueue creation
- bnxt_en: Fix memory fault in bnxt_ethtool_init()
- virtio-net: add missing virtqueue kick when flushing packets
- VSOCK: make af_vsock.ko removable again
- hwmon: (k10temp) Add temperature offset for Ryzen 2700X
- hwmon: (k10temp) Add support for AMD Ryzen w/ Vega graphics
- s390/cpum_cf: rename IBM z13/z14 counter names
- kprobes: Fix random address output of blacklist file
- Revert "pinctrl: intel: Initialize GPIO properly when used through
irqchip"
* Lenovo V330 needs patch in ideapad_laptop module for rfkill (LP: #1774636)
- SAUCE: Add Lenovo V330 to the ideapad_laptop rfkill blacklist
* bluetooth controller fail after suspend with USB autosuspend on XPS 13 9360
(LP: #1775217)
- Bluetooth: btusb: Add Dell XPS 13 9360 to btusb_needs_reset_resume_table
* [Hyper-V] PCI: hv: Fix 2 hang issues in
[Bug 1770244] Re: Decode ARM CPER records in kernel
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 severity: corrected
[ 350.598598] {1}[Hardware Error]: precise tstamp: 2018-06-14 22:31:22
[ 350.598602] {1}[Hardware Error]: Error 0, type: corrected
[ 350.598612] {1}[Hardware Error]: section_type: ARM processor error
[ 350.598618] {1}[Hardware Error]: MIDR: 0x510fc001
[ 350.598632] {1}[Hardware Error]: Multiprocessor Affinity Register (MPIDR):
0x0201
[ 350.598640] {1}[Hardware Error]: error affinity level: 2
[ 350.598644] {1}[Hardware Error]: running state: 0x1
[ 350.598648] {1}[Hardware Error]: Power State Coordination Interface state: 0
[ 350.598654] {1}[Hardware Error]: Error info structure 0:
[ 350.598656] {1}[Hardware Error]: num errors: 2
[ 350.598661] {1}[Hardware Error]:first error captured
[ 350.598664] {1}[Hardware Error]:error_type: 0, cache error
[ 350.598668] {1}[Hardware Error]:error_info: 0x04c6007f
[ 350.598674] {1}[Hardware Error]: transaction type: Generic
[ 350.598677] {1}[Hardware Error]: operation type: Generic read (type of
instruction or data request cannot be determined)
[ 350.598680] {1}[Hardware Error]: cache level: 3
[ 350.598684] {1}[Hardware Error]: processor context not corrupted
[ 350.598688] {1}[Hardware Error]: the error has been corrected
[ 350.598691] {1}[Hardware Error]: PC is imprecise
[ 350.598695] {1}[Hardware Error]:physical fault address:
0x12345000
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770244] Re: Decode ARM CPER records in kernel
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 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770244] Re: Decode ARM CPER records in kernel
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770244] Re: Decode ARM CPER records in kernel
** 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 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: 0x04c6007f
[ 388.094341] {2}[Hardware Error]:physical fault address:
0x12345000
But with the fix, you'll see:
[ 388.094304] {2}[Hardware Error]:error_info: 0x04c6007f
[ 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:
0x12345000
[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.
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770244] Re: Decode ARM CPER records in kernel
** 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 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 directly.
+ 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: 0x04c6007f
[ 388.094341] {2}[Hardware Error]:physical fault address:
0x12345000
But with the fix, you'll see:
[ 388.094304] {2}[Hardware Error]:error_info: 0x04c6007f
[ 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:
0x12345000
-
[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]
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770244] Re: Decode ARM CPER records in kernel
** 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 directly.
[Test Case]
- TBD
+ 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: 0x04c6007f
+ [ 388.094341] {2}[Hardware Error]:physical fault address:
0x12345000
+
+ But with the fix, you'll see:
+
+ [ 388.094304] {2}[Hardware Error]:error_info: 0x04c6007f
+ [ 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:
0x12345000
+
[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]
- TBD
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770244] Re: Decode ARM CPER records in kernel
** 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 efi: Move ARM CPER code to new file + 301f55b1a9177132d2b9ce8a90bf0ae4b37bb850 efi: Parse ARM error information value [Regression Risk] TBD ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
