From: "Tomáš Janoušek" <tomi@nomi.cz>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Matthew Wilcox <matthew@wil.cx>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Dominik Brodowski <linux@dominikbrodowski.net>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-devel@lists.sourceforge.net,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: DMAR:[fault reason 02] Present bit in context entry is clear (firewire-ohci)
Date: Thu, 1 Dec 2011 10:14:41 +0100 [thread overview]
Message-ID: <20111201091441.GA32731@nomi.cz> (raw)
In-Reply-To: <4ED656F6.4080709@ladisch.de>
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/
prev parent reply other threads:[~2011-12-01 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 10:26 DMAR:[fault reason 02] Present bit in context entry is clear (firewire-ohci) Stefan Richter
2010-05-22 12:12 ` Matthew Wilcox
2010-05-22 18:40 ` David Woodhouse
2010-05-22 19:09 ` Jesse Barnes
2010-05-30 14:18 ` Stefan Richter
2011-11-19 17:21 ` Tomáš Janoušek
2011-11-30 16:16 ` Clemens Ladisch
2011-12-01 9:14 ` Tomáš Janoušek [this message]
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=20111201091441.GA32731@nomi.cz \
--to=tomi@nomi.cz \
--cc=clemens@ladisch.de \
--cc=dwmw2@infradead.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linux@dominikbrodowski.net \
--cc=matthew@wil.cx \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.