Bug 901824 - Possible bug on intel VT-d
Summary: Possible bug on intel VT-d
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-19 14:43 UTC by Antonio Augusto Santos
Modified: 2013-01-21 14:40 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-21 14:40:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output of lspci -vv (8.79 KB, text/x-log)
2013-01-19 14:43 UTC, Antonio Augusto Santos
no flags Details
The output of dmesg after last boot (100.92 KB, text/x-log)
2013-01-19 14:46 UTC, Antonio Augusto Santos
no flags Details
Dmidecode output (21.71 KB, text/x-log)
2013-01-19 14:46 UTC, Antonio Augusto Santos
no flags Details

Description Antonio Augusto Santos 2013-01-19 14:43:02 UTC
Created attachment 683068 [details]
Output of lspci -vv

Description of problem:
I'm getting the followin "Warning" on every boot:
[    0.721854] ------------[ cut here ]------------
[    0.721859] WARNING: at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge+0x58/0x80()
[    0.721860] Hardware name: To be filled by O.E.M.
[    0.721861] Modules linked in:
[    0.721863] Pid: 1, comm: swapper/0 Not tainted 3.7.2-201.fc18.x86_64 #1
[    0.721864] Call Trace:
[    0.721868]  [<ffffffff8105e67f>] warn_slowpath_common+0x7f/0xc0
[    0.721870]  [<ffffffff8105e6da>] warn_slowpath_null+0x1a/0x20
[    0.721872]  [<ffffffff813152b8>] pci_find_upstream_pcie_bridge+0x58/0x80
[    0.721875]  [<ffffffff81502d9b>] intel_iommu_add_device+0x4b/0x1f0
[    0.721877]  [<ffffffff814fa950>] ? bus_set_iommu+0x60/0x60
[    0.721878]  [<ffffffff814fa983>] add_iommu_group+0x33/0x60
[    0.721881]  [<ffffffff813d0f55>] bus_for_each_dev+0x55/0x90
[    0.721882]  [<ffffffff814fa93b>] bus_set_iommu+0x4b/0x60
[    0.721884]  [<ffffffff81d3bbdd>] intel_iommu_init+0xa73/0xb9b
[    0.721887]  [<ffffffff81046959>] ? free_init_pages+0x129/0x1c0
[    0.721890]  [<ffffffff81cfc9d4>] ? md_run_setup+0x9c/0x9c
[    0.721891]  [<ffffffff81cfd206>] ? maybe_link.part.2+0x111/0x111
[    0.721893]  [<ffffffff81d032d1>] ? memblock_find_dma_reserve+0x13d/0x13d
[    0.721895]  [<ffffffff81d032e4>] pci_iommu_init+0x13/0x3e
[    0.721897]  [<ffffffff8100216a>] do_one_initcall+0x12a/0x180
[    0.721900]  [<ffffffff81611a6c>] kernel_init+0x1fc/0x380
[    0.721901]  [<ffffffff81cfb614>] ? do_early_param+0x8c/0x8c
[    0.721903]  [<ffffffff81611870>] ? rest_init+0x80/0x80
[    0.721906]  [<ffffffff8163da2c>] ret_from_fork+0x7c/0xb0
[    0.721908]  [<ffffffff81611870>] ? rest_init+0x80/0x80
[    0.721912] ---[ end trace 0a657a1071a1f899 ]---


Version-Release number of selected component (if applicable):
kernel-3.7.2-201.fc18.x86_64

How reproducible:
Always. Every boot I get this message. Wasn't present on 3.7.1 *(looked on /var/log/mesages)

Steps to Reproduce:
1. Instal kernel 3.7.2-201
2. Boot the machine
3.
  
Actual results:
No problems detected on the system, but I'm not using VT-d at the momment, just VT-x.

Expected results:
No warnings on boot

Additional info:
I'm running a Intel i7-3770 (non k) on a Gigabyte z77m-d3h, with 16Gb of ram.

Comment 1 Antonio Augusto Santos 2013-01-19 14:46:28 UTC
Created attachment 683069 [details]
The output of dmesg after last boot

Comment 2 Antonio Augusto Santos 2013-01-19 14:46:57 UTC
Created attachment 683070 [details]
Dmidecode output

Comment 3 Antonio Augusto Santos 2013-01-19 17:59:29 UTC
I'm not getting the warning anymore on 3.7.2-204.
Probably related to this (from the changelog):

* Tue Jan 15 09:00:00 2013 Justin M. Forbes <jforbes> 3.7.2-203
- Turn off Intel IOMMU by default
- Stable queue from 3.7.3 with many relevant fixes

* Fri Jan 11 09:00:00 2013 Justin M. Forbes <jforbes> 3.7.1-1
- Linux v3.7.2
- Enable Intel IOMMU by default

So i guess that was indeed just a warning.


Note You need to log in before you can comment on or make changes to this bug.