Bug 496396 - intel_iommu warning: DMAR reported at address zero
intel_iommu warning: DMAR reported at address zero
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
10
All Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-18 12:51 EDT by Harald Reindl
Modified: 2009-04-21 08:12 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-04-21 08:12:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Harald Reindl 2009-04-18 12:51:23 EDT
Since upgrade to testing-kernel 2.6.29.1-30.fc10.x86_64 i get the following stack-trace every boot on my notebook

2.6.29-10 and 2.6.29.1-15 which i used before had no oops

___________

------------[ cut here ]------------
WARNING: at drivers/pci/dmar.c:182 dmar_table_init+0x12f/0x29a() (Not tainted)
Hardware name: HP Compaq 6830s
Your BIOS is broken; DMAR reported at address zero!
BIOS vendor: Hewlett-Packard; Ver: 68PZD Ver. F.09; Product Version: F.09
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.29.1-30.fc10.x86_64 #1
Call Trace:
 [<ffffffff810496d9>] warn_slowpath+0xb9/0xfe
 [<ffffffff8104a1f6>] ? vprintk+0x309/0x33e
 [<ffffffff81150dee>] ? security_inode_alloc+0x1c/0x1e
 [<ffffffff813716cd>] ? _spin_lock+0x9/0xc
 [<ffffffff810fa20b>] ? inotify_d_instantiate+0x44/0x49
 [<ffffffff8136f1da>] ? printk+0x3c/0x42
 [<ffffffff815ebeb4>] dmar_table_init+0x12f/0x29a
 [<ffffffff815cfb94>] ? pci_iommu_init+0x0/0x21
 [<ffffffff815ec4ac>] intel_iommu_init+0x16/0x840
 [<ffffffff8100e7f1>] ? xen_debugfs_create_u32_array+0x57/0x63
 [<ffffffff815cfb94>] ? pci_iommu_init+0x0/0x21
 [<ffffffff815c5140>] ? early_idt_handler+0x0/0x71
 [<ffffffff815cfba2>] pci_iommu_init+0xe/0x21
 [<ffffffff8100a056>] do_one_initcall+0x56/0x13d
 [<ffffffff8108e586>] ? register_irq_proc+0xb0/0xcc
 [<ffffffff81110000>] ? vfs_set_dqinfo+0xb4/0x111
 [<ffffffff815c574e>] kernel_init+0x1d0/0x228
 [<ffffffff8101264a>] child_rip+0xa/0x20
 [<ffffffff81011f67>] ? restore_args+0x0/0x30
 [<ffffffff815c557e>] ? kernel_init+0x0/0x228
 [<ffffffff81012640>] ? child_rip+0x0/0x20
---[ end trace 4eaa2a86a8e2da22 ]---
Comment 1 Chuck Ebbert 2009-04-21 08:10:43 EDT
This is not an oops it's just a warning. Your BIOS really is broken and there's nothing we can do about it. You can get rid of the warning by adding "intel_iommu=off" to the boot options.

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