Hi Joerg Roedel,
> From: j...@8bytes.org [mailto:j...@8bytes.org]
> Yes, that is true. But the messages are harmless and you are safe to ignore
> them in your usecase.
> We only care about the kdump case when copying the old IR and DMAR tables
> into the new kernel,
> because in the kdump
Hi Joerg,
On Thu, Apr 27, 2017 at 06:12:38PM +0200, j...@8bytes.org wrote:
> On Thu, Apr 27, 2017 at 03:34:06PM +, Zhuo, Qiuxu wrote:
> > It looks like the printk is misleading and it’s nothing actually
> > failed, but just it isn’t copying if the new kernel is not a kdump
> > kernel.
>
>
On Thu, Apr 27, 2017 at 03:34:06PM +, Zhuo, Qiuxu wrote:
> It looks like the printk is misleading and it’s nothing actually
> failed, but just it isn’t copying if the new kernel is not a kdump
> kernel.
Yes, that is true. But the messages are harmless and you are safe to
ignore them in your
Hi Joerg Roedel,
When we run below command, the kernel message showed below confusing failed
messages:
sudo kexec -l /boot/vmlinuz-4.11.0-rc7
--append=root=UUID=276659dd-77f0-47f9-967c-7643c260b746
--initrd=/boot/initrd.img-4.11.0-rc7
sudo kexec -e
---
[
