Bug 697094

Summary: kernel oops happens after every startup
Product: [Fedora] Fedora Reporter: Dhiraj Kumar Hazra <dhirajhazra>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sgruszka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-16 22:10:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg output none

Description Dhiraj Kumar Hazra 2011-04-15 20:00:36 UTC
Created attachment 492487 [details]
dmesg output

Description of problem:
kernel oops happens after every startup

Version-Release number of selected component (if applicable):

rpm -qa|grep kernel
kernel-headers-2.6.35.12-88.fc14.x86_64
kernel-2.6.35.6-45.fc14.x86_64
abrt-addon-kerneloops-1.1.17-1.fc14.x86_64
kernel-2.6.35.12-88.fc14.x86_64

How reproducible:
after boot everytime

Steps to Reproduce:
1.
2.
3.
  
Actual results:
======================================================================
WARNING: at drivers/pci/dmar.c:633 warn_invalid_dmar+0x7d/0x8d()
Hardware name: HP Pavilion dv4 Notebook PC
Your BIOS is broken; DMAR reported at address 0!
BIOS vendor: Insyde; Ver: F.65; Product Version: F.65
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.35.6-45.fc14.x86_64 #1
Call Trace:
 [<ffffffff8104d7c1>] warn_slowpath_common+0x85/0x9d
 [<ffffffff8102baca>] ? _paravirt_ident_64+0x9/0xe
 [<ffffffff8104d834>] warn_slowpath_fmt_taint+0x3f/0x41
 [<ffffffff81245693>] warn_invalid_dmar+0x7d/0x8d
 [<ffffffff81bcf2c9>] check_zero_address+0xb9/0xf9
 [<ffffffff81be20a0>] ? boot_command_line+0x0/0x800
 [<ffffffff81471193>] ? _etext+0x0/0x1
 [<ffffffff81bcf31b>] detect_intel_iommu+0x12/0x95
 [<ffffffff81ba8362>] pci_iommu_alloc+0x1c/0x28
 [<ffffffff81bb7243>] mem_init+0x19/0xec
 [<ffffffff81be20a0>] ? boot_command_line+0x0/0x800
 [<ffffffff81ba1a63>] start_kernel+0x225/0x416
 [<ffffffff81ba12c6>] x86_64_start_reservations+0xb1/0xb5
 [<ffffffff81ba13c2>] x86_64_start_kernel+0xf8/0x107
====================================================================

Expected results:


Additional info:

Comment 1 Stanislaw Gruszka 2011-04-16 22:10:46 UTC
This message correctly indicate that BIOS provide invalid data to kernel. Try to update BIOS. If that not help you may try to contact your hardware vendor.