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.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Changed in: linux (Ubuntu Cosmic)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  [Regression] crashkernel fails on HiSilicon D05

Status in linux package in Ubuntu:
Status in linux source package in Cosmic:
Status in linux source package in Disco:

Bug description:
  kdump support isn't usable on HiSilicon D05 systems. This previously worked 
in bionic.

  [Test Case]
  sudo apt install linux-crashdump
crashkernel=512M"' | \
    sudo tee /etc/default/grub.d/kdump-tools.cfg
  sudo update-grub
  sudo reboot
  echo 1 | sudo tee /proc/sys/kernel/sysrq
  echo c | sudo tee /proc/sysrq-trigger

  2 upstream patch series are required to fix this:
  Which provides an EFI facility consumed by:
  There were also some follow-on fixes to deal with ARM-specific problems 
associated with this usage:

  [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 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).

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to