Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Tomáš Janoušek" <tomi@nomi.cz>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Matthew Wilcox <matthew@wil.cx>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-pci@vger.kernel.org, linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: DMAR:[fault reason 02] Present bit in context entry is clear (firewire-ohci)
Date: Sat, 19 Nov 2011 18:21:27 +0100	[thread overview]
Message-ID: <20111119172127.GA31915@nomi.cz> (raw)
In-Reply-To: <20100522120905.154ff932@jbarnes-x201>

Hello guys,

On Sat, May 22, 2010 at 12:09:05PM -0700, Jesse Barnes wrote:
> On Sat, 22 May 2010 19:40:43 +0100
> David Woodhouse <dwmw2@infradead.org> wrote:
> > [...]
> > Yeah, the DMAR looks at the source-id in the PCIe transactions, and it
> > sounds like those are all 04:00.0. But we've probably set up the DMAR to
> > allow the transactions from 04:00.4, and then it naturally faults when a
> > "different" device actually ends up doing the transaction.
> > 
> > If you make the pci_find_upstream_pcie_bridge() function do the
> > appropriate thing for this device, does it then work as expected?
> > 
> > Whether that's a _sane_ thing to do or not is possibly more of a Jesse
> > question...
> 
> Well, if cardbus bridges tend to behave this way in general it would
> make sense to simply use the cardbus bride id everywhere, rather than
> the specific functions of the device.  Cc'ing Dominik.

Any news on this one? It is still an issue with current kernel on current
hardware (like my ThinkPad T420). :-(

Regards,
-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/

       reply	other threads:[~2011-11-19 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4BF7B147.9020502@s5r6.in-berlin.de>
     [not found] ` <20100522121212.GQ10452@parisc-linux.org>
     [not found]   ` <1274553643.11551.17300.camel@macbook.infradead.org>
     [not found]     ` <20100522120905.154ff932@jbarnes-x201>
2011-11-19 17:21       ` Tomáš Janoušek [this message]
2011-11-30 16:16         ` DMAR:[fault reason 02] Present bit in context entry is clear (firewire-ohci) 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=20111119172127.GA31915@nomi.cz \
    --to=tomi@nomi.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox