All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: kdump boot failing with IVRS checksum failure
Date: Thu, 24 Sep 2020 11:23:48 +0200	[thread overview]
Message-ID: <20200924092348.GI27174@8bytes.org> (raw)
In-Reply-To: <87o8lzvtzp.fsf@redhat.com>

Hi Jerry,

On Mon, Sep 21, 2020 at 11:56:42AM -0700, Jerry Snitselaar wrote:
> We are seeing a kdump kernel boot failure in test on an HP DL325 Gen10
> and it was tracked down to 387caf0b759a ("iommu/amd: Treat per-device
> exclusion ranges as r/w unity-mapped regions"). Reproduced on 5.9-rc5
> and goes away with revert of the commit. There is a follow on commit
> that depends on this that was reverted as well 2ca6b6dc8512 ("iommu/amd:
> Remove unused variable"). I'm working on getting system access and want
> to see what the IVRS table looks like, but thought I'd give you heads
> up.

Thanks for looking into this, we really need to find the root-cause to
avoid the revert.

Thanks,

	Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Adrian Huang <adrianhuang0701@gmail.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: kdump boot failing with IVRS checksum failure
Date: Thu, 24 Sep 2020 11:23:48 +0200	[thread overview]
Message-ID: <20200924092348.GI27174@8bytes.org> (raw)
In-Reply-To: <87o8lzvtzp.fsf@redhat.com>

Hi Jerry,

On Mon, Sep 21, 2020 at 11:56:42AM -0700, Jerry Snitselaar wrote:
> We are seeing a kdump kernel boot failure in test on an HP DL325 Gen10
> and it was tracked down to 387caf0b759a ("iommu/amd: Treat per-device
> exclusion ranges as r/w unity-mapped regions"). Reproduced on 5.9-rc5
> and goes away with revert of the commit. There is a follow on commit
> that depends on this that was reverted as well 2ca6b6dc8512 ("iommu/amd:
> Remove unused variable"). I'm working on getting system access and want
> to see what the IVRS table looks like, but thought I'd give you heads
> up.

Thanks for looking into this, we really need to find the root-cause to
avoid the revert.

Thanks,

	Joerg

  reply	other threads:[~2020-09-24  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 18:56 kdump boot failing with IVRS checksum failure Jerry Snitselaar
2020-09-21 18:56 ` Jerry Snitselaar
2020-09-24  9:23 ` Joerg Roedel [this message]
2020-09-24  9:23   ` Joerg Roedel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200924092348.GI27174@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jsnitsel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.