From: David Brownell <david-b@pacbell.net>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ashok.raj@intel.com, shaohua.li@intel.com,
anil.s.keshavamurthy@intel.com, Dave Airlie <airlied@linux.ie>
Subject: Re: DMAR EHCI failures
Date: Sat, 9 Feb 2008 18:02:41 -0800 [thread overview]
Message-ID: <200802091802.41596.david-b@pacbell.net> (raw)
In-Reply-To: <47A74B02.8050704@gmail.com>
On Monday 04 February 2008, Jiri Slaby wrote:
> Hi,
>
> I have this in dmesg:
> DMAR:[DMA Write] Request device [00:02.0] fault addr ee1512000
> DMAR:[fault reason 05] PTE Write access is not set
> PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
> DMAR:[DMA Read] Request device [00:1d.7] fault addr 7d5f0000
> DMAR:[fault reason 06] PTE Read access is not set
> DMAR:[DMA Read] Request device [00:1a.7] fault addr 7d5f1000
> DMAR:[fault reason 06] PTE Read access is not set
> PCI-GART: No AMD northbridge found.
> DMAR:[DMA Read] Request device [00:1a.2] fault addr 7d5f7000
> DMAR:[fault reason 06] PTE Read access is not set
>
> CONFIG_DMAR=y
> CONFIG_DMAR_GFX_WA=y
> CONFIG_DMAR_FLOPPY_WA=y
>
> Without the gfx workaround, there is much more output regarding 00:02.0. Is
> there problem with broken hw, bios or drivers?
No idea. Someone who knows the DMA Remapping stuff should have
an answer. Presumably it works with DMAR disabled, yes? If so,
then just don't use DMAR. :)
> /sys/firmware/acpi/tables/DMAR:
> http://www.fi.muni.cz/~xslaby/sklad/DMAR.bin
> dmesg:
> http://www.fi.muni.cz/~xslaby/sklad/DMAR.dmesg
>
> # for a in 00:02.0 00:1d.7 00:1a.7 00:1a.2; do lspci -vxxx -s $a; done
> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
> Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
> ... deletia ...
>
next prev parent reply other threads:[~2008-02-10 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 17:27 DMAR EHCI failures Jiri Slaby
2008-02-10 2:02 ` David Brownell [this message]
2008-02-11 17:51 ` Raj, Ashok
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=200802091802.41596.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=airlied@linux.ie \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashok.raj@intel.com \
--cc=dbrownell@users.sourceforge.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=stern@rowland.harvard.edu \
/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