| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 1 Dec 2014 13:33:27 +0100 From: Joerg Roedel <joro@...tes.org> To: "Li, ZhenHua" <zhen-hual@...com> Cc: Takao Indoh <indou.takao@...fujitsu.com>, bhe@...hat.com, dwmw2@...radead.org, vgoyal@...hat.com, dyoung@...hat.com, iommu@...ts.linux-foundation.org, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, alex.williamson@...hat.com, ddutile@...hat.com, ishii.hironobu@...fujitsu.com, bhelgaas@...gle.com, doug.hatch@...com, jerry.hoemann@...com, tom.vaden@...com, li.zhang6@...com, lisa.mitchell@...com Subject: Re: [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO On Mon, Dec 01, 2014 at 02:31:38PM +0800, Li, ZhenHua wrote: > After I implement these two steps, there comes a new fault: > > [1.594890] dmar: DRHD: handling fault status reg 2 > [1.594894] dmar: INTR-REMAP: Request device [[41:00.0] fault index 4d > [1.594894] INTR-REMAP:[fault reason 34] Present field in the IRTE entry > is clear > > It is caused by similar reason, so I will fix it like fixing the DMAR > faults: Do NOT disable and re-enable the interrupt remapping, try to > use data from old kernel. Yes, that sounds right, thanks. Looking forward to your patches. Joerg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists