[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150503085530.GK15033@dhcp-16-116.nay.redhat.com>
Date: Sun, 3 May 2015 16:55:30 +0800
From: Baoquan He <bhe@...hat.com>
To: "Li, Zhen-Hua" <zhen-hual@...com>
Cc: alex.williamson@...hat.com, indou.takao@...fujitsu.com,
tom.vaden@...com, rwright@...com, dwmw2@...radead.org,
joro@...tes.org, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, lisa.mitchell@...com,
jerry.hoemann@...com, iommu@...ts.linux-foundation.org,
ddutile@...hat.com, doug.hatch@...com,
ishii.hironobu@...fujitsu.com, linux-pci@...r.kernel.org,
bhelgaas@...gle.com, billsumnerlinux@...il.com, li.zhang6@...com,
dyoung@...hat.com, vgoyal@...hat.com
Subject: Re: [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump
kernel
On 04/29/15 at 07:20pm, Baoquan He wrote:
> Bad news, I rebuilt a kernel with your patchset on 4.0.0+ (this commit
> f614c81). Now dmar fault is seen again.
>
> The lspci log and kdump log are attached, please check:
I found the lspci log previously attached is emtyp, resend it again.
View attachment "lspci.log" of type "text/plain" (35557 bytes)
Powered by blists - more mailing lists