linux-kernel - Re: DMAR:[fault reason 02] Present bit in context entry is clear (firewire-ohci)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 1 Dec 2011 10:14:41 +0100
From:	Tomáš Janoušek <tomi@...i.cz>
To:	Clemens Ladisch <clemens@...isch.de>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Matthew Wilcox <matthew@....cx>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Dominik Brodowski <linux@...inikbrodowski.net>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux1394-devel@...ts.sourceforge.net,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: DMAR:[fault reason 02] Present bit in context entry is clear
	(firewire-ohci)

Hi,

On Wed, Nov 30, 2011 at 05:16:54PM +0100, Clemens Ladisch wrote:
> Try the patch in <https://bugzilla.redhat.com/show_bug.cgi?id=605888>
> that is intended to work around the bug in your Ricoh chip.  Alternatively,
> disable VT-d or FireWire in the BIOS, or add the kernel parameter
> "intel_iommu=off".

Yeah, I guess that would work, I was just concerned with a fix not being in
the mainline. Surely we don't expect every ThinkPad user who wants to use
firewire and VT-d to apply the patch himself (the Fedora fix was to forcefully
disable IOMMU in presence of that Ricoh device). :-)

Regards,
-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/
--
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/