From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1YqLob-00086y-P8 for kexec@lists.infradead.org; Thu, 07 May 2015 13:26:14 +0000 Date: Thu, 7 May 2015 21:25:36 +0800 From: Dave Young Subject: Re: [PATCH v9 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel Message-ID: <20150507132536.GA4559@localhost.localdomain> References: <1426743388-26908-1-git-send-email-zhen-hual@hp.com> <20150403084031.GF22579@dhcp-128-53.nay.redhat.com> <20150504110551.GD15736@8bytes.org> <20150505060931.GB31063@dhcp-128-4.nay.redhat.com> <20150505152343.GP15736@8bytes.org> <20150506014649.GA14065@dhcp-128-4.nay.redhat.com> <20150506081617.GB20611@8bytes.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20150506081617.GB20611@8bytes.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Joerg Roedel Cc: alex.williamson@redhat.com, indou.takao@jp.fujitsu.com, bhe@redhat.com, tom.vaden@hp.com, rwright@hp.com, linux-pci@vger.kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, lisa.mitchell@hp.com, jerry.hoemann@hp.com, iommu@lists.linux-foundation.org, "Li, Zhen-Hua" , ddutile@redhat.com, doug.hatch@hp.com, ishii.hironobu@jp.fujitsu.com, bhelgaas@google.com, billsumnerlinux@gmail.com, li.zhang6@hp.com, dwmw2@infradead.org, vgoyal@redhat.com On 05/06/15 at 10:16am, Joerg Roedel wrote: > On Wed, May 06, 2015 at 09:46:49AM +0800, Dave Young wrote: > > For the original problem, the key issue is dmar faults cause kdump kernel > > hang so that vmcore can not be saved. I do not know the reason why it hangs > > I think it is acceptable if kdump kernel boot ok with some dma errors.. > > It hangs because some devices can't handle the DMAR faults and the kdump > kernel can't initialize them and will hang itself. For that it doesn't > matter whether the fault was caused by a read or write request. Ok, thanks for explanation. so it explains sometimes kdump kernel boot ok with faults, sometimes it hangs instead. Dave _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec