>------- Comment From bren...@br.ibm.com 2018-03-05 09:46 EDT-------
>Hi Cascardo,
>
>(In reply to comment #19)
>> We are working on getting those fixes to 16.04, on the -updates repository.
>> But it's not part of 16.04.4.
>
>I am not sure I understood the following statement. Do you mean that the fix 
>will be pushed to >-updates archive after the 16.04.4, thus, it will not make 
>the 16.04.4 cut date?
>
>If that is the case, that might cause some impacts, because we are making a 
>release that contains >some known regressions. Should we document it somewhere?
>
>Thank you,
>Breno

Hi, Breno.

>From my testing on xenial and hwe kernel, kexec still works and
makedumpfile will fallback to cp. Then, one can copy that dump to a
bionic system and use crash from bionic to analyze it. Can you test that
such a produced dump can be analyzed by crash on bionic? I want to make
sure we are still producing valid dumps on most cases, or identify when
dumps are not valid. Some of the hwe kernels with kpti backports are not
dumpable, but the next artful and hwe release, to be in -proposed by
next week, should have that fixed in the kernel side.

I am still investigating the possibility of getting all this into a
better situation, but I want to make sure that the current situation is
not that bad as you are saying.

Thanks.
Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746088

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to