Re: amd kdump failure with iommu=nopt

2020-05-14 Thread Jerry Snitselaar
On Thu May 14 20, Joerg Roedel wrote: On Thu, May 14, 2020 at 05:36:23PM +0200, Joerg Roedel wrote: This commit also removes the deferred attach of the device to its new domain. Does the attached diff fix the problem for you? +static int __iommu_attach_device_no_defer(struct iommu_domain *domain

Re: amd kdump failure with iommu=nopt

2020-05-14 Thread Joerg Roedel
On Thu, May 14, 2020 at 05:36:23PM +0200, Joerg Roedel wrote: > This commit also removes the deferred attach of the device to its new > domain. Does the attached diff fix the problem for you? > +static int __iommu_attach_device_no_defer(struct iommu_domain *domain, > +

Re: amd kdump failure with iommu=nopt

2020-05-14 Thread Joerg Roedel
Hi Jerry, On Wed, May 13, 2020 at 08:18:38PM -0700, Jerry Snitselaar wrote: > We've seen kdump failures with recent kernels (5.5, 5.6, 5.7-rc1) on > amd systems when iommu is enabled in translation mode. In the cases so > far there has been mpt3sas involved, but I'm also seeing io page > faults fo

amd kdump failure with iommu=nopt

2020-05-13 Thread Jerry Snitselaar
We've seen kdump failures with recent kernels (5.5, 5.6, 5.7-rc1) on amd systems when iommu is enabled in translation mode. In the cases so far there has been mpt3sas involved, but I'm also seeing io page faults for ahci right before mpt3sas has an io page fault: [ 15.156620] ahci :63:00.0: