IOMMU issue
Stephen Davies
sdavies at sdc.com.au
Tue Feb 18 02:05:43 UTC 2014
I have just used fedup to upgrade from FC17 to FC18.
When I reboot into fedup, the screen is unreadable in graphics mode so I
changed the grub configuration to use console.
Now booting to fedup gives:
dmar:IOMMU: failed to map dmar0
and hangs/crashes/freezes.
If I reboot to FC17, the system is perfectly usable but dmesg tells me:
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.3.4-5.fc17.x86_64
root=/dev/mapper/vg_mustang-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True
KEYTABLE=us rd.lvm.lv=vg_mustang/lv_swap rd.lvm.lv=vg_mustang/lv_root
rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: at drivers/iommu/dmar.c:492
warn_invalid_dmar+0x92/0xa0()
[ 0.000000] Hardware name: S3210SH
[ 0.000000] Your BIOS is broken; DMAR reported at address feb00000 returns
all ones!
[ 0.000000] BIOS vendor: Intel Corporation; Ver:
S3200X38.86B.00.00.0033.112120071101; Product Version:
[ 0.000000] Modules linked in:
[ 0.000000] Pid: 0, comm: swapper Not tainted 3.3.4-5.fc17.x86_64 #1
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff810568af>] warn_slowpath_common+0x7f/0xc0
[ 0.000000] [<ffffffff8105694f>] warn_slowpath_fmt_taint+0x3f/0x50
[ 0.000000] [<ffffffff8103d0c9>] ? native_flush_tlb_single+0x9/0x10
[ 0.000000] [<ffffffff81b0164b>] ? __early_set_fixmap+0x99/0xa0
[ 0.000000] [<ffffffff814bcc42>] warn_invalid_dmar+0x92/0xa0
[ 0.000000] [<ffffffff81b29c0c>] check_zero_address+0xc8/0xf7
[ 0.000000] [<ffffffff815f795f>] ? bad_to_user+0x7f9/0x7f9
[ 0.000000] [<ffffffff81b29c52>] detect_intel_iommu+0x17/0xb9
[ 0.000000] [<ffffffff81af4e7e>] pci_iommu_alloc+0x4a/0x73
[ 0.000000] [<ffffffff81b0140a>] mem_init+0x19/0xed
[ 0.000000] [<ffffffff815e09bc>] ? set_nmi_gate+0x48/0x4a
[ 0.000000] [<ffffffff81aeda20>] start_kernel+0x1da/0x3c5
[ 0.000000] [<ffffffff81aed346>] x86_64_start_reservations+0x131/0x135
[ 0.000000] [<ffffffff81aed44a>] x86_64_start_kernel+0x100/0x10f
[ 0.000000] ---[ end trace a7919e7f17c0a725 ]---
After a deal of Googling, I tried adding iommu=off to the grub configuration
boot args.
With that in place, neither FC17 nor fedup will boot so I have taken it out
again.
Any ideas as to what I can do to get fedup to boot?
Cheers and thanks,
Stephen Davies
--
=============================================================================
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia. Mobile:040 304 0583
Records & Collections Management.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140218/3d304a72/attachment.html>
More information about the users
mailing list