Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Upon boot-up, and login, immediately this crash appears. Additional info: WARNING: at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge+0x5b/0x70() Hardware name: To be filled by O.E.M. Modules linked in: Pid: 1, comm: swapper/0 Not tainted 3.7.2-201.fc18.i686.PAE #1 Call Trace: [<c044d6a2>] warn_slowpath_common+0x72/0xa0 [<c06afa0b>] ? pci_find_upstream_pcie_bridge+0x5b/0x70 [<c06afa0b>] ? pci_find_upstream_pcie_bridge+0x5b/0x70 [<c044d6f2>] warn_slowpath_null+0x22/0x30 [<c06afa0b>] pci_find_upstream_pcie_bridge+0x5b/0x70 [<c0878037>] intel_iommu_add_device+0x37/0x1a0 [<c0966da1>] ? klist_next+0x21/0xe0 [<c08754c0>] ? bus_set_iommu+0x60/0x60 [<c08754ea>] add_iommu_group+0x2a/0x60 [<c07621e2>] bus_for_each_dev+0x42/0x80 [<c087549d>] bus_set_iommu+0x3d/0x60 [<c08754c0>] ? bus_set_iommu+0x60/0x60 [<c0c78f83>] intel_iommu_init+0x9bf/0xad1 [<c0c5317c>] ? free_initrd_mem+0x1b/0x1d [<c0c46ffa>] ? memblock_find_dma_reserve+0x5/0x5 [<c0c47009>] pci_iommu_init+0xf/0x34 [<c0403152>] do_one_initcall+0x112/0x160 [<c096704a>] kernel_init+0x13a/0x2b0 [<c0c3f48b>] ? do_early_param+0x7a/0x7a [<c098f737>] ret_from_kernel_thread+0x1b/0x28 [<c0966f10>] ? rest_init+0x60/0x60 Potential duplicate: bug 878273
You're right about the duplicate. Can you tell us something about the hardware this is happening on?
This should be gone with the -204 kernel in updates. Please reopen if it recreates with that.
It's still happening with kernel-3.8.3-201.fc18.x86_64.
It's still happening with kernel-3.8.6-203.fc18.x86_64.
It's still happening with kernel-3.8.8-202.fc18.x86_64.
It's still happening with kernel-3.8.9-200.fc18.x86_64.
It's still happening with kernel-3.8.11-200.fc18.x86_64.
It's still happening with kernel-3.9.2-200.fc18.x86_64.
It's still happening with kernel-3.9.4-200.fc18.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 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.
It's still happening with kernel-3.11.9-200.fc19.x86_64 [ 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 ]--- [ 0.330381] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [ 0.330748] Initialise system trusted keyring
*********** 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.
Shouldn't this bug be closed as a duplicate of bug #901807?
Shouldn't this bug be closed as a duplicate of bug #878273?
*** This bug has been marked as a duplicate of bug 878273 ***