From: Daniel Haid <d.haid@gogi.tv>
To: <linux-kernel@vger.kernel.org>
Subject: Question about iommu on x86_64 and radeon driver.
Date: Sun, 22 May 2011 22:56:27 +0100 [thread overview]
Message-ID: <6ac3f6faad655602b767aa14b355e982@admin.gogi.tv> (raw)
Hello,
I have an x86_64 system with a VIA chipset and 4GB of RAM. The
mainboard
is an ASUS M2V where the bios-setup has an option called "Map around
memory hole" and I have an "ATI Technologies Inc RV710 [Radeon HD
4350]"
graphics card according to lspci.
Now one of the following things happen to my system:
1) With the bios-option enabled and no kernel parameters I get the
following error:
[drm:r600_ring_test] *ERROR* radeon: ring test failed
(scratch(0x8504)=0xCAFEDEAD)
radeon 0000:02:00.0: disabling GPU acceleration
and then I can not use any 3d-acceleration. I also get the message
Looks like a VIA chipset. Disabling IOMMU. Override with iommu=allowed
2) With the bios-option enabled and "mem=3072M" I can not use only 3GB
of RAM,
but the radeon card works.
3) With the bios-option enabled and "iommu=allowed" I get 4GB of RAM
and
the radeon card works. But I wonder whether this can have any bad
effects?
4) Without the bios-option (and without any kernel parameters) I do not
get the "Looks like a VIA chipset. Disabling IOMMU. Override with
iommu=allowed"
message, but strangely linux shows only about 3GB of RAM.
I did not try other combinations. Now my questions are
A) Is this a bug in the radeon driver? Or maybe not, since
Documentation/x86/x86_64/boot-options.txt
seems to imply that for >3GB an iommu is required?
B) Is it safe to use iommu=allowed in my case ? If not, what problems
will I encounter and what
options should I use instead? Will I be stuck with 3GB of RAM?
Please cc me if you answer, since I am not subscribed.
Thank you.
next reply other threads:[~2011-05-22 22:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 21:56 Daniel Haid [this message]
2011-05-23 22:05 ` Konrad Rzeszutek Wilk
2011-05-23 23:45 ` Daniel Haid
2011-05-24 15:50 ` Konrad Rzeszutek Wilk
2011-05-24 21:33 ` Daniel Haid
2011-05-25 12:58 ` Konrad Rzeszutek Wilk
2011-05-25 14:28 ` Daniel Haid
2011-05-24 22:48 ` Andi Kleen
2011-05-25 10:00 ` Daniel Haid
2011-05-25 12:57 ` Konrad Rzeszutek Wilk
2011-05-25 14:51 ` Daniel Haid
2011-05-25 20:21 ` Daniel Haid
2011-05-25 23:05 ` Andi Kleen
2011-05-27 15:48 ` Daniel Haid
2011-05-27 15:55 ` Konrad Rzeszutek Wilk
2011-05-27 22:20 ` Daniel Haid
2011-05-31 13:45 ` Konrad Rzeszutek Wilk
2011-05-31 15:34 ` Daniel Haid
2011-05-31 16:02 ` Konrad Rzeszutek Wilk
[not found] ` <0a8cb4bcad7fcf091a6bbe158323bba0@admin.gogi.tv>
2011-05-31 16:20 ` Daniel Haid
[not found] ` <20110531190412.GA21245@dumpdata.com>
2011-05-31 19:57 ` Daniel Haid
2011-06-01 13:24 ` Konrad Rzeszutek Wilk
2011-06-01 16:10 ` Daniel Haid
2011-06-01 21:51 ` Andi Kleen
2011-06-01 21:58 ` Daniel Haid
2011-06-01 22:22 ` Andi Kleen
2011-06-03 17:31 ` [PATCH] tentative fix for radeon on systems >4GB without hardware iommu Daniel Haid
2011-06-03 20:44 ` Alex Deucher
2011-06-03 23:13 ` Konrad Rzeszutek Wilk
2011-06-06 17:45 ` Daniel Haid
2011-06-06 17:41 ` Daniel Haid
2011-06-06 19:08 ` Alex Deucher
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=6ac3f6faad655602b767aa14b355e982@admin.gogi.tv \
--to=d.haid@gogi.tv \
--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
all inboxes | Powered by JetHome®