summaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/aperture_64.c
diff options
context:
space:
mode:
authorAdam Jackson <ajax@redhat.com>2008-09-29 14:52:03 -0400
committerIngo Molnar <mingo@elte.hu>2008-09-30 10:25:28 +0200
commit9b1568458a3ef006361710dc12848aec891883b5 (patch)
treee0bcd0b1fadb4fb04e8336cef4fb1839924b39cb /arch/x86/kernel/aperture_64.c
parent12544697f12e0ecdcf971075415c7678fae502af (diff)
downloadop-kernel-dev-9b1568458a3ef006361710dc12848aec891883b5.zip
op-kernel-dev-9b1568458a3ef006361710dc12848aec891883b5.tar.gz
x86, debug printouts: IOMMU setup failures should not be KERN_ERR
The number of BIOSes that have an option to enable the IOMMU, or fix anything about its configuration, is vanishingly small. There's no good reason to punish quiet boot for this. Signed-off-by: Adam Jackson <ajax@redhat.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/x86/kernel/aperture_64.c')
-rw-r--r--arch/x86/kernel/aperture_64.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/arch/x86/kernel/aperture_64.c b/arch/x86/kernel/aperture_64.c
index 44e2182..9a32b37 100644
--- a/arch/x86/kernel/aperture_64.c
+++ b/arch/x86/kernel/aperture_64.c
@@ -455,11 +455,11 @@ out:
force_iommu ||
valid_agp ||
fallback_aper_force) {
- printk(KERN_ERR
+ printk(KERN_INFO
"Your BIOS doesn't leave a aperture memory hole\n");
- printk(KERN_ERR
+ printk(KERN_INFO
"Please enable the IOMMU option in the BIOS setup\n");
- printk(KERN_ERR
+ printk(KERN_INFO
"This costs you %d MB of RAM\n",
32 << fallback_aper_order);
OpenPOWER on IntegriCloud