linux-kernel - Re: intel-iommu: CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080506131554.4adb3f9c.akpm@linux-foundation.org>
Date:	Tue, 6 May 2008 13:15:54 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Gabriel C <nix.or.die@...glemail.com>
Cc:	mgross@...ux.intel.com, linux-kernel@...r.kernel.org,
	ashok.raj@...el.com, shaohua.li@...el.com,
	anil.s.keshavamurthy@...el.com, jbarnes@...tuousgeek.org,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: intel-iommu: CONFIG_DMAR*=y kills my box

On Wed, 30 Apr 2008 01:04:45 +0200
Gabriel C <nix.or.die@...glemail.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?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/