From: Andrew Morton <akpm@linux-foundation.org>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: mgross@linux.intel.com, linux-kernel@vger.kernel.org,
ashok.raj@intel.com, shaohua.li@intel.com,
anil.s.keshavamurthy@intel.com, jbarnes@virtuousgeek.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: intel-iommu: CONFIG_DMAR*=y kills my box
Date: Tue, 6 May 2008 13:15:54 -0700 [thread overview]
Message-ID: <20080506131554.4adb3f9c.akpm@linux-foundation.org> (raw)
In-Reply-To: <4817A98D.8080007@googlemail.com>
On Wed, 30 Apr 2008 01:04:45 +0200
Gabriel C <nix.or.die@googlemail.com> wrote:
>
Guys, it's really painful having to scroll through thousand-line emails to
find a few lines of information. Please trim stuff.
>
> >
> > I do find it quite odd that a DMA code path specific to PCIE is somehow
> > in the loop for a parallel port device. Should this be possible?
>
> I have no idea =) ( PCI folks added to CC )
>
> >
> > I could easily be wrong so feel free to correct me but;
> > I think your bios is goofy / unprepared to support IOMMU / VT-d and
> > doing strange things with enumerated a parallel port on a PCIE bus with
> > VTD is turned on...
>
> I will contact ASUS peoples about the BIOS but it has for sure VT-d support and it is enabled.
So.. what happened here? It seems like a pretty fatal problem, and
personally I don't think that contacting vendors about BIOS upgrades is a
suitable general solution. It would be much better to find a kernel-based
fix or workaround?
next prev parent reply other threads:[~2008-05-06 20:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 14:21 Gabriel C
2008-04-26 17:27 ` Gabriel C
2008-04-29 0:29 ` mark gross
2008-04-29 1:20 ` Gabriel C
2008-04-29 22:53 ` mark gross
2008-04-29 23:04 ` Gabriel C
2008-05-06 20:15 ` Andrew Morton [this message]
2008-05-07 20:58 ` mark gross
2008-05-08 14:43 ` mark gross
2008-05-08 16:45 ` mark gross
2008-05-08 17:56 ` Gabriel C
2008-05-08 18:55 ` mark gross
2008-05-08 17:54 ` mark gross
2008-04-29 0:11 ` mark gross
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=20080506131554.4adb3f9c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashok.raj@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mgross@linux.intel.com \
--cc=nix.or.die@googlemail.com \
--cc=shaohua.li@intel.com \
/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
Powered by JetHome