[Regression] crashkernel fails on HiSilicon D05
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
dann frazier | ||
Cosmic |
Fix Released
|
Undecided
|
dann frazier | ||
Disco |
Fix Released
|
Undecided
|
dann frazier |
Bug Description
[Impact]
kdump support isn't usable on HiSilicon D05 systems. This previously worked in bionic.
[Test Case]
sudo apt install linux-crashdump
echo 'GRUB_CMDLINE_
sudo tee /etc/default/
sudo update-grub
sudo reboot
echo 1 | sudo tee /proc/sys/
echo c | sudo tee /proc/sysrq-trigger
On failure:
[ 2.362261] ------------[ cut here ]------------
[ 2.362263] [CRTC:29:crtc-0] vblank wait timed out
[ 2.362294] WARNING: CPU: 0 PID: 143 at drivers/
[ 2.362295] Modules linked in: hibmc_drm(+) ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm hisi_sas_v2_hw(+) hisi_sas_main ehci_platform libsas scsi_transport_sas
[ 2.362309] CPU: 0 PID: 143 Comm: systemd-udevd Tainted: G C 4.19.0-7-generic #8-Ubuntu
[ 2.362310] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.50 06/01/2018
[ 2.362312] pstate: 60400005 (nZCv daif +PAN -UAO)
[ 2.362324] pc : drm_atomic_
[ 2.362335] lr : drm_atomic_
[ 2.362336] sp : ffff00000a2fb1f0
[ 2.362337] x29: ffff00000a2fb1f0 x28: 0000000000000001
[ 2.362339] x27: 0000000000000000 x26: 0000000000000001
[ 2.362342] x25: 0000000000000038 x24: ffff8000208c5800
[ 2.362344] x23: 0000000000000000 x22: 0000000000000001
[ 2.362346] x21: ffff80001eebb818 x20: ffff800025b18600
[ 2.362349] x19: 0000000000000000 x18: 0000000000000001
[ 2.362351] x17: 0000000000000000 x16: 0000000000000000
[ 2.362353] x15: ffffffffffffffff x14: ffff000009848708
[ 2.362355] x13: 0000000000000074 x12: ffff000009a12000
[ 2.362357] x11: ffff00000986d000 x10: ffff000009a122f8
[ 2.362359] x9 : 0000000000000001 x8 : ffff000009a15104
[ 2.362361] x7 : 0000000000000000 x6 : 0000004ce5700bb7
[ 2.362363] x5 : 00ffffffffffffff x4 : 0000000000000000
[ 2.362365] x3 : 0000000000000000 x2 : ffffffffffffffff
[ 2.362367] x1 : 0b15ae454042e100 x0 : 0000000000000000
[ 2.362370] Call trace:
[ 2.362381] drm_atomic_
[ 2.362392] drm_atomic_
[ 2.362402] commit_
[ 2.362413] drm_atomic_
[ 2.362440] drm_atomic_
[ 2.362451] restore_
[ 2.362461] restore_
[ 2.362472] drm_fb_
[ 2.362482] drm_fb_
[ 2.362488] fbcon_init+
[ 2.362491] visual_
[ 2.362492] do_bind_
[ 2.362494] do_take_
[ 2.362495] do_fbcon_
[ 2.362497] fbcon_event_
[ 2.362501] notifier_
[ 2.362502] blocking_
[ 2.362504] fb_notifier_
[ 2.362506] register_
[ 2.362516] __drm_fb_
[ 2.362526] drm_fb_
[ 2.362530] hibmc_fbdev_
[ 2.362534] hibmc_pci_
[ 2.362537] local_pci_
[ 2.362539] pci_device_
[ 2.362541] really_
[ 2.362543] driver_
[ 2.362544] __driver_
[ 2.362545] bus_for_
[ 2.362547] driver_
[ 2.362548] bus_add_
[ 2.362550] driver_
[ 2.362551] __pci_register_
[ 2.362555] hibmc_init+
[ 2.362557] do_one_
[ 2.362560] do_init_
[ 2.362561] load_module+
[ 2.362563] __se_sys_
[ 2.362565] __arm64_
[ 2.362567] el0_svc_
[ 2.362568] el0_svc_
[ 2.362570] el0_svc+0x8/0xc
[ 2.362571] ---[ end trace 8031150f999972d9 ]---
[Fix]
2 upstream patch series are required to fix this:
https://<email address hidden>
Which provides an EFI facility consumed by:
https:/
There were also some follow-on fixes to deal with ARM-specific problems associated with this usage:
https:/
[Regression Risk]
The EFI changes are in architecture independent code where they add a new table and an API for adding regions to that table. However, this API is only used by the gic-v3-its driver, which is ARM-specific. On other architectures, this will be an empty table. It's possible that there is a bug in the table creation code that could cause regressions on other architectures, which would likely be seen in the form of a boot time error message ("Failed to install memreserve config table").
Risk mitigated by testing on both x86 ARM and EFI systems.
CVE References
description: | updated |
Changed in linux (Ubuntu Disco): | |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Cosmic): | |
status: | Incomplete → In Progress |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu Disco): | |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu Disco): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Cosmic): | |
status: | In Progress → Fix Committed |
tags: |
added: kernel-fixup-verification-needed-bionic removed: verification-needed-bionic |
tags: | added: verification-done-bionic |
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1806766
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.