From: Steffen Moser <lists@steffen-moser.de>
To: linux-kernel@vger.kernel.org
Subject: IOMMU and DMA mode of pata_jmicron
Date: Wed, 29 Dec 2010 00:43:36 +0100 [thread overview]
Message-ID: <4D1A7628.3050704@steffen-moser.de> (raw)
Hi all,
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
This results, as expected, in a much too low data throughput
between the system and the optical drives connected to the
P-ATA controller.
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
Earlier versions of 2.6.35.x are affected, too. I haven't
tested other kernel versions besides 2.6.35.x, yet.
If you need further information (log files, information from
"/proc", lspci, and so on), please let me know.
Thank you very much in advance for any hint!
Best regards,
Steffen
next reply other threads:[~2010-12-28 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 23:43 Steffen Moser [this message]
2010-12-29 1:00 ` IOMMU and DMA mode of pata_jmicron Jeff Garzik
2011-01-03 11:29 ` Roedel, Joerg
2011-01-03 20:15 ` Steffen Moser
2011-01-04 10:23 ` Roedel, Joerg
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=4D1A7628.3050704@steffen-moser.de \
--to=lists@steffen-moser.de \
--cc=linux-kernel@vger.kernel.org \
/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