From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-pci@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: DMAR:[fault reason 02] Present bit in context entry is clear (firewire-ohci)
Date: Sat, 22 May 2010 12:26:15 +0200 [thread overview]
Message-ID: <4BF7B147.9020502@s5r6.in-berlin.de> (raw)
Hi,
I came across a report of the subject message. What does it mean; what
type of bug should be look for?
https://bugzilla.redhat.com/show_bug.cgi?id=587178
>>>
firewire_ohci 0000:04:00.4: PCI INT C -> GSI 16 (level, low) -> IRQ 16
firewire_ohci 0000:04:00.4: setting latency timer to 64
firewire_ohci: Added fw-ohci device 0000:04:00.4, OHCI version 1.0
DRHD: handling fault status reg 2
DMAR:[DMA Read] Request device [04:00.0] fault addr fffff000
DMAR:[fault reason 02] Present bit in context entry is clear
DMAR:[DMA Read] Request device [04:00.0] fault addr fffff000
DMAR:[fault reason 02] Present bit in context entry is clear
DMAR:[DMA Read] Request device [04:00.0] fault addr fffff000
DMAR:[fault reason 02] Present bit in context entry is clear
<<<
The log sounds as if this happens during from-device DMA of 04:00.4 into
a consistent buffer, yet the fault is logged for device 04:00.0. The
log is from a Dell M4500. The devices are, according to a web search,
04:00.0 CardBus bridge [0607]: Ricoh Co Ltd Device [1180:e476] (rev 02)
04:00.4 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd Device [1180:e832]
(rev 03) (prog-if 10)
Thanks for any hint,
--
Stefan Richter
-=====-==-=- -=-= =-==-
http://arcgraph.de/sr/
next reply other threads:[~2010-05-22 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 10:26 Stefan Richter [this message]
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
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=4BF7B147.9020502@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®