Description of problem: I tried to enable VT-d on my computer by booting with intel_iommu=on. Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: BOOT_IMAGE=/vmlinuz-3.6.6-1.fc17.x86_64 root=/dev/mapper/hermesVG-Fedora--rootVol ro rd.md=0 rd.dm=0 SYSFONT=True KEYTABLE=us nodmraid rd.luks=0 nompath rd.lvm.lv=hermesVG/Fedora-rootVol LANG=en_US.UTF-8 ipv6.disable=1 video=VGA-1:d intel_iommu=on kernel: 3.6.6-1.fc17.x86_64 backtrace: :WARNING: at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge+0x5e/0x70() :Hardware name: :Modules linked in: :Pid: 1, comm: swapper/0 Not tainted 3.6.6-1.fc17.x86_64 #1 :Call Trace: : [<ffffffff8105b8ef>] warn_slowpath_common+0x7f/0xc0 : [<ffffffff8105b94a>] warn_slowpath_null+0x1a/0x20 : [<ffffffff8130385e>] pci_find_upstream_pcie_bridge+0x5e/0x70 : [<ffffffff814edadb>] intel_iommu_add_device+0x4b/0x1f0 : [<ffffffff814e6200>] ? bus_set_iommu+0x60/0x60 : [<ffffffff814e6233>] add_iommu_group+0x33/0x60 : [<ffffffff813bfff5>] bus_for_each_dev+0x55/0x90 : [<ffffffff814e61eb>] bus_set_iommu+0x4b/0x60 : [<ffffffff81d3aa7b>] intel_iommu_init+0xa71/0xb99 : [<ffffffff81044889>] ? free_init_pages+0x129/0x1c0 : [<ffffffff81cfcb83>] ? md_run_setup+0x9c/0x9c : [<ffffffff81cfd3b5>] ? maybe_link.part.2+0x111/0x111 : [<ffffffff81d03073>] ? memblock_find_dma_reserve+0x13d/0x13d : [<ffffffff81d03086>] pci_iommu_init+0x13/0x3e : [<ffffffff8100212a>] do_one_initcall+0x12a/0x180 : [<ffffffff81cfbd97>] kernel_init+0x150/0x1d4 : [<ffffffff81cfb614>] ? do_early_param+0x8c/0x8c : [<ffffffff816269c4>] kernel_thread_helper+0x4/0x10 : [<ffffffff81cfbc47>] ? start_kernel+0x3d4/0x3d4 : [<ffffffff816269c0>] ? gs_change+0x13/0x13
It seems that ABRT didn't say anything about the hardware. The CPU is Intel Core i7-3770 with HT enabled and the motherboad is Intel DZ77BH-55K bulk.
It also happened with kernel-3.6.8-2.fc17.x86_64.
I've just had the same error. I enabled vt-d in UEFI then booted fedora 18 beta with grub 2.0 with intel_iommu=1. I have all updates from updates-testing as of 1/6/13. I also have a core i7-3770 with HT enabled. Motherboard is Asrock z77 Pro4. I am booting fedora in uefi mode without secure boot.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
It's still happening with kernel-3.9.6-200.fc18.x86_64: kernel: Unpacking initramfs... kernel: Freeing initrd memory: 20156k freed kernel: DMAR: No ATSR found kernel: IOMMU 0 0xfed90000: using Queued invalidation kernel: IOMMU 1 0xfed91000: using Queued invalidation kernel: IOMMU: Setting RMRR: kernel: IOMMU: Setting identity map for device 0000:00:02.0 [0xcb800000 - 0xcf9fffff] kernel: IOMMU: Setting identity map for device 0000:00:1d.0 [0xca20b000 - 0xca217fff] kernel: IOMMU: Setting identity map for device 0000:00:1a.0 [0xca20b000 - 0xca217fff] kernel: IOMMU: Setting identity map for device 0000:00:14.0 [0xca20b000 - 0xca217fff] kernel: IOMMU: Prepare 0-16MiB unity mapping for LPC kernel: IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff] kernel: PCI-DMA: Intel(R) Virtualization Technology for Directed I/O kernel: ------------[ cut here ]------------ kernel: WARNING: at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge+0x58/0x80() kernel: Hardware name: kernel: Modules linked in: kernel: Pid: 1, comm: swapper/0 Not tainted 3.9.6-200.fc18.x86_64 #1 kernel: Call Trace: kernel: [<ffffffff8105ef85>] warn_slowpath_common+0x75/0xa0 kernel: [<ffffffff8105efca>] warn_slowpath_null+0x1a/0x20 kernel: [<ffffffff813319b8>] pci_find_upstream_pcie_bridge+0x58/0x80 kernel: [<ffffffff8152e63b>] intel_iommu_add_device+0x4b/0x1f0 kernel: [<ffffffff81525ec0>] ? bus_set_iommu+0x60/0x60 kernel: [<ffffffff81525ef3>] add_iommu_group+0x33/0x60 kernel: [<ffffffff813f7a8d>] bus_for_each_dev+0x5d/0xa0 kernel: [<ffffffff81525eab>] bus_set_iommu+0x4b/0x60 kernel: [<ffffffff81d45af8>] intel_iommu_init+0xa72/0xb9a kernel: [<ffffffff81d0bba2>] ? memblock_find_dma_reserve+0x13d/0x13d kernel: [<ffffffff81d0bbb5>] pci_iommu_init+0x13/0x3e kernel: [<ffffffff8100215a>] do_one_initcall+0x12a/0x180 kernel: [<ffffffff81d04033>] kernel_init_freeable+0x150/0x1df kernel: [<ffffffff81d03885>] ? do_early_param+0x8c/0x8c kernel: [<ffffffff81646970>] ? rest_init+0x80/0x80 kernel: [<ffffffff8164697e>] kernel_init+0xe/0xf0 kernel: [<ffffffff8166a52c>] ret_from_fork+0x7c/0xb0 kernel: [<ffffffff81646970>] ? rest_init+0x80/0x80 kernel: ---[ end trace c4604bbb75f3833d ]---
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.
[ 0.224774] Unpacking initramfs... [ 0.321021] Freeing initrd memory: 8248K (ffff880036fd4000 - ffff8800377e2000) [ 0.321170] DMAR: No ATSR found [ 0.321276] IOMMU 0 0xfed90000: using Queued invalidation [ 0.321364] IOMMU 1 0xfed91000: using Queued invalidation [ 0.321453] IOMMU: Setting RMRR: [ 0.321545] IOMMU: Setting identity map for device 0000:00:02.0 [0xcb800000 - 0xcf9fffff] [ 0.321979] IOMMU: Setting identity map for device 0000:00:1d.0 [0xca209000 - 0xca215fff] [ 0.322125] IOMMU: Setting identity map for device 0000:00:1a.0 [0xca209000 - 0xca215fff] [ 0.322269] IOMMU: Setting identity map for device 0000:00:14.0 [0xca209000 - 0xca215fff] [ 0.322407] IOMMU: Prepare 0-16MiB unity mapping for LPC [ 0.322498] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff] [ 0.322955] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O [ 0.323094] ------------[ cut here ]------------ [ 0.323185] WARNING: CPU: 0 PID: 1 at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge+0x77/0x90() [ 0.323319] Modules linked in: [ 0.323443] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.9-200.fc19.x86_64 #1 [ 0.323573] Hardware name: /DZ77BH-55K, BIOS BHZ7710H.86A.0100.2013.0517.0942 05/17/2013 [ 0.323712] 0000000000000009 ffff8808030d1ce0 ffffffff8164764b 0000000000000000 [ 0.323998] ffff8808030d1d18 ffffffff8106715d ffff880802fde098 ffff880802fde000 [ 0.324284] ffff880802fde098 ffffffff81cbb0a0 ffff88080e405660 ffff8808030d1d28 [ 0.324571] Call Trace: [ 0.324658] [<ffffffff8164764b>] dump_stack+0x45/0x56 [ 0.324746] [<ffffffff8106715d>] warn_slowpath_common+0x7d/0xa0 [ 0.324833] [<ffffffff8106723a>] warn_slowpath_null+0x1a/0x20 [ 0.324920] [<ffffffff8132b557>] pci_find_upstream_pcie_bridge+0x77/0x90 [ 0.325009] [<ffffffff8152638d>] intel_iommu_add_device+0x4d/0x220 [ 0.325099] [<ffffffff8151d680>] ? bus_set_iommu+0x50/0x50 [ 0.325187] [<ffffffff8151d6aa>] add_iommu_group+0x2a/0x50 [ 0.325277] [<ffffffff813efff3>] bus_for_each_dev+0x63/0xa0 [ 0.325366] [<ffffffff8151d678>] bus_set_iommu+0x48/0x50 [ 0.325456] [<ffffffff81d5f4f0>] intel_iommu_init+0xa55/0xb4d [ 0.325546] [<ffffffff8104f5e5>] ? free_init_pages+0x75/0xa0 [ 0.325637] [<ffffffff81d10694>] ? maybe_link.part.2+0x110/0x110 [ 0.325732] [<ffffffff81d17da9>] ? memblock_find_dma_reserve+0x124/0x124 [ 0.325821] [<ffffffff81d17dbb>] pci_iommu_init+0x12/0x3c [ 0.325911] [<ffffffff810020fa>] do_one_initcall+0xfa/0x1b0 [ 0.326001] [<ffffffff81086795>] ? parse_args+0x225/0x400 [ 0.326090] [<ffffffff81d0f078>] kernel_init_freeable+0x177/0x1ff [ 0.326179] [<ffffffff81d0e898>] ? do_early_param+0x88/0x88 [ 0.326270] [<ffffffff8163d940>] ? rest_init+0x80/0x80 [ 0.326359] [<ffffffff8163d94e>] kernel_init+0xe/0x190 [ 0.326448] [<ffffffff816567ac>] ret_from_fork+0x7c/0xb0 [ 0.326537] [<ffffffff8163d940>] ? rest_init+0x80/0x80 [ 0.326628] ---[ end trace ae3280ebc4cdeff1 ]---
That was from kernel-3.11.9-200.fc19.x86_64.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
After upgrading to 3.12.6, can you try the patches here: http://www.spinics.net/lists/linux-pci/msg22136.html And report your findings there: https://bugzilla.kernel.org/show_bug.cgi?id=44881
*** Bug 1025978 has been marked as a duplicate of this bug. ***
It's still happening with kernel-3.12.6-300.fc20.x86_64 and IMMU on: kernel: Command line: initrd=\865b8ff295c29b42a3eef3ecebbeea5a\3.12.6-300.fc20.x86_64\initrd root=UUID=ca0414e3-a3f3-4a12-9bf2-47a528bea489 ro vconsole.font=latarcyrheb-sun16 rhgb quiet rd.driver.blacklist=nvidia,nouveau nouveau.modeset=0 video=VGA-1:d nmi_watchdog=0 intel_iommu=on kernel: Freeing initrd memory: 10816K (ffff88007f570000 - ffff880080000000) kernel: DMAR: No ATSR found kernel: IOMMU 0 0xfed90000: using Queued invalidation kernel: IOMMU 1 0xfed91000: using Queued invalidation kernel: IOMMU: Setting RMRR: kernel: IOMMU: Setting identity map for device 0000:00:02.0 [0xcb800000 - 0xcf9fffff] kernel: IOMMU: Setting identity map for device 0000:00:1d.0 [0xca209000 - 0xca215fff] kernel: IOMMU: Setting identity map for device 0000:00:1a.0 [0xca209000 - 0xca215fff] kernel: IOMMU: Setting identity map for device 0000:00:14.0 [0xca209000 - 0xca215fff] kernel: IOMMU: Prepare 0-16MiB unity mapping for LPC kernel: IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff] kernel: PCI-DMA: Intel(R) Virtualization Technology for Directed I/O kernel: ------------[ cut here ]------------ kernel: WARNING: CPU: 0 PID: 1 at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge+0x77/0x90() kernel: Modules linked in: kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.6-300.fc20.x86_64 #1 kernel: Hardware name: /DZ77BH-55K, BIOS BHZ7710H.86A.0100.2013.0517.0942 05/17/2013 kernel: 0000000000000009 ffff8808034f9ce0 ffffffff816630c1 0000000000000000 kernel: ffff8808034f9d18 ffffffff810691dd ffff8808032dd098 ffff8808032dd000 kernel: ffff8808032dd098 ffffffff81cc2680 ffff88080e805960 ffff8808034f9d28 kernel: Call Trace: kernel: [<ffffffff816630c1>] dump_stack+0x45/0x56 kernel: [<ffffffff810691dd>] warn_slowpath_common+0x7d/0xa0 kernel: [<ffffffff810692ba>] warn_slowpath_null+0x1a/0x20 kernel: [<ffffffff8133cc17>] pci_find_upstream_pcie_bridge+0x77/0x90 kernel: [<ffffffff8153ff3d>] intel_iommu_add_device+0x4d/0x220 kernel: [<ffffffff815370e0>] ? bus_set_iommu+0x50/0x50 kernel: [<ffffffff8153710a>] add_iommu_group+0x2a/0x50 kernel: [<ffffffff813fde13>] bus_for_each_dev+0x63/0xa0 kernel: [<ffffffff815370d8>] bus_set_iommu+0x48/0x50 kernel: [<ffffffff81d6d0ce>] intel_iommu_init+0xa56/0xb4e kernel: [<ffffffff81051655>] ? free_init_pages+0x75/0xa0 kernel: [<ffffffff81d1e6fd>] ? maybe_link.part.2+0x10e/0x10e kernel: [<ffffffff81d25e76>] ? memblock_find_dma_reserve+0x124/0x124 kernel: [<ffffffff81d25e88>] pci_iommu_init+0x12/0x3c kernel: [<ffffffff810020f2>] do_one_initcall+0xf2/0x1a0 kernel: [<ffffffff81089225>] ? parse_args+0x225/0x3f0 kernel: [<ffffffff81d1d07a>] kernel_init_freeable+0x178/0x200 kernel: [<ffffffff81d1c89a>] ? do_early_param+0x88/0x88 kernel: [<ffffffff81659400>] ? rest_init+0x80/0x80 kernel: [<ffffffff8165940e>] kernel_init+0xe/0x190 kernel: [<ffffffff8167207c>] ret_from_fork+0x7c/0xb0 kernel: [<ffffffff81659400>] ? rest_init+0x80/0x80 kernel: ---[ end trace 77c4ad2e21278927 ]--- kernel: alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) kernel: Initialise system trusted keyring (In reply to Michele Baldessari from comment #11) > After upgrading to 3.12.6, can you try the patches here: > http://www.spinics.net/lists/linux-pci/msg22136.html Compiling software, especially the kernel isn't exactly my thing. I'll try to follow the instructions from https://fedoraproject.org/wiki/Building_a_custom_kernel .
If I boot without intel_iommu=on there's no sign of that warning (at least for the first 26 minutes).
*** Bug 901807 has been marked as a duplicate of this bug. ***
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.