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 +0000, 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 usecase. We only care about the kdump case when
Looks like maybe sanitizing the message to make it less disturbing should be enough :-) > copying the old IR and DMAR tables into the new kernel, because in the > kdump case the old kernel crashed and left devices in an undefined > state, so that they might still send DMA and IRQ requests to the new > kernel, corrupting data or causing spurious/blocked irqs. Blocked IRQs > or DMA requests might even break devices so that the new kernel can't > initialize them anymore. Cheers, Ashok _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
