linux-kernel - Re: IOMMU and DMA mode of pata

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: <4D1A881C.3080109@garzik.org>
Date:	Tue, 28 Dec 2010 20:00:12 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Steffen Moser <lists@...ffen-moser.de>
CC:	linux-kernel@...r.kernel.org,
	Linux IDE mailing list <linux-ide@...r.kernel.org>,
	Joerg Roedel <joerg.roedel@....com>
Subject: Re: IOMMU and DMA mode of pata_jmicron

(CC'd linux-ide, Joerg)

On 12/28/2010 06:43 PM, Steffen Moser wrote:
> I've encountered a problem with my AMD 890FX based system
> and linux-2.6.35.10 (x86_64 platform).
>
> After activating the option "IOMMU" in the mainboard's BIOS
> setup, the onboard P-ATA controller "JMicron Technology Corp.
> JMB361 AHCI/IDE (rev 02)" puts itself back in the PIO mode.
> When loading the module, the kernel reports:
>
>    pata_jmicron 0000:06:00.1: BMDMA: failed to set dma mask, \
>                               falling back to PIO
[...]
> As soon as I deactivate IOMMU in BIOS setup, the P-ATA channel
> runs in the DMA mode again. The S-ATA controllers don't seem
> to be affected.
>
> My question is: Is this a known behavior? Are there any
> things I have to consider when activating IOMMU (which seems
> to be AMD-Vi) on an 890FX based system? Is it a problem of
> the chipset and/or the controller or is it related to a
> problem in the libata area?
>
> Some information about the affected system:
>
>  - Mainboard:    ASUS M4A89TD Pro/USB3
>  - BIOS version: 1101 (most recent version)
>  - Chipset:      AMD 890FX
>  - Processor:    AMD Phenom 1090T
>  - Memory:       4 x 4 GB (Kingston KVR1333D3E9S/4G)
>  - Distribution: openSUSE 11.3
>  - Kernel:       2.6.35.10 (from "kernel.org"), x86_64
>

This condition occurs when the PCI API cannot set the PCI device's DMA 
mask to the 32-bit value
	#define ATA_DMA_MASK            0xffffffffULL

That is an unusual failure for such a modern system, which certainly can 
handle 32-bit masks like that, one would think.

	Jeff



--
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/