From: Adrian Huang12 <ahuang12@lenovo.com>
To: Baoquan He <bhe@redhat.com>, "joro@8bytes.org" <joro@8bytes.org>
Cc: "iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jsnitsel@redhat.com" <jsnitsel@redhat.com>
Subject: RE: [External] Re: [PATCH] Revert "iommu/amd: Treat per-device exclusion ranges as r/w unity-mapped regions"
Date: Wed, 23 Sep 2020 14:29:13 +0000 [thread overview]
Message-ID: <HK2PR0302MB259469A987E70869F5E7809EB3380@HK2PR0302MB2594.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <20200923023244.GK25604@MiWiFi-R3L-srv>
Hi Baoquan,
> -----Original Message-----
> From: Baoquan He <bhe@redhat.com>
> Sent: Wednesday, September 23, 2020 10:33 AM
> To: joro@8bytes.org; Adrian Huang12 <ahuang12@lenovo.com>
> Cc: iommu@lists.linux-foundation.org; linux-kernel@vger.kernel.org;
> jsnitsel@redhat.com
> Subject: [External] Re: [PATCH] Revert "iommu/amd: Treat per-device exclusion
> ranges as r/w unity-mapped regions"
>
> Forgot CC-ing Jerry, add him.
>
> On 09/23/20 at 10:26am, Baoquan He wrote:
> > A regression failure of kdump kernel boot was reported on a HPE system.
> > Bisect points at commit 387caf0b759ac43 ("iommu/amd: Treat per-device
> > exclusion ranges as r/w unity-mapped regions") as criminal. Reverting
> > it fix the failure.
> >
> > With the commit, kdump kernel will always print below error message,
> > then naturally AMD iommu can't function normally during kdump kernel
> bootup.
> >
> > ~~~~~~~~~
> > AMD-Vi: [Firmware Bug]: IVRS invalid checksum
> >
> > Why commit 387caf0b759ac43 causing it haven't been made clear.
>
> Hi Joerg, Adrian
>
> We only have one machine which can reproduce the issue, it's a gen10-01 of
> HPE. If any log or info are needed, please let me know, I can attach here.
Could you please provide the following info?
1. The booting log for both system kernel and kdump kernel by appending the kernel parameter 'amd_iommu_dump'
2. ACPI table (# acpidump > acpi-table) -> Send out the file 'acpi-table'.
-- Adrian
next prev parent reply other threads:[~2020-09-23 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 2:26 [PATCH] Revert "iommu/amd: Treat per-device exclusion ranges as r/w unity-mapped regions" Baoquan He
2020-09-23 2:32 ` Baoquan He
2020-09-23 14:29 ` Adrian Huang12 [this message]
2020-09-24 9:08 ` 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=HK2PR0302MB259469A987E70869F5E7809EB3380@HK2PR0302MB2594.apcprd03.prod.outlook.com \
--to=ahuang12@lenovo.com \
--cc=bhe@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).