Bug 861757 - [abrt]: WARNING: at drivers/iommu/dmar.c:493 warn_invalid_dmar+0x98/0xb0()
Summary: [abrt]: WARNING: at drivers/iommu/dmar.c:493 warn_invalid_dmar+0x98/0xb0()
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fb6e44e5870947466a1860f3654...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-30 14:16 UTC by karthikeyan
Modified: 2012-10-01 11:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-01 11:51:54 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description karthikeyan 2012-09-30 14:16:31 UTC 
Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
cmdline:        BOOT_IMAGE=/boot/vmlinuz-3.5.4-1.fc17.i686.PAE root=UUID=dae3061b-36a8-4fc9-95eb-5562a94a46d4 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
kernel:         3.5.4-1.fc17.i686.PAE

backtrace:
:WARNING: at drivers/iommu/dmar.c:493 warn_invalid_dmar+0x98/0xb0()
:Hardware name: HP Pavilion dv4 Notebook PC
:Your BIOS is broken; DMAR reported at address 0!
:BIOS vendor: Insyde; Ver: F.67; Product Version: F.67
:Modules linked in:
:Pid: 0, comm: swapper Not tainted 3.5.4-1.fc17.i686.PAE #1
:Call Trace:
: [<c0447a82>] warn_slowpath_common+0x72/0xa0
: [<c0851fb8>] ? warn_invalid_dmar+0x98/0xb0
: [<c0851fb8>] ? warn_invalid_dmar+0x98/0xb0
: [<c0447b12>] warn_slowpath_fmt_taint+0x32/0x40
: [<c0851fb8>] warn_invalid_dmar+0x98/0xb0
: [<c0c3f100>] check_zero_address+0x59/0x11f
: [<c06e6013>] ? acpi_get_table_with_size+0x5f/0xb9
: [<c0c3f1d8>] detect_intel_iommu+0x12/0x7c
: [<c0c0f52c>] pci_iommu_alloc+0x3a/0x5e
: [<c0c1b618>] mem_init+0xe/0x28c
: [<c0c25855>] ? ___alloc_bootmem_node_nopanic+0x50/0xa1
: [<c0958d7e>] ? printk+0x4d/0x4f
: [<c0c26e10>] ? page_cgroup_init_flatmem+0x6d/0x98
: [<c0c0785d>] start_kernel+0x1b6/0x363
: [<c0c074dc>] ? repair_env_string+0x51/0x51
: [<c0c072f8>] i386_start_kernel+0x9b/0xa2
Comment 1 Josh Boyer 2012-10-01 11:51:54 UTC 
As the bug says, your BIOS is broken.  There isn't much we can do here.
Note You need to log in before you can comment on or make changes to this bug.