Bug 969966

Summary:	Your BIOS is broken; DMAR reported at address fed90000 returns all ones!
Product:	[Fedora] Fedora	Reporter:	Mattia Vio <theus84>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	18	CC:	dennis, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
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:	2013-07-01 18:25:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mattia Vio 2013-06-03 08:08:19 UTC

Description of problem:
after the yum update/upgrade of today the system is unstable.
Trying to open some page on the browser makes the system logout.
Using fedora at work this problem is killing my day.
I past a copy of the dmseg error below.



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


How reproducible:
always


Steps to Reproduce:
1. opening some page on the web browser

Actual results:
the system logout and send me to the login page


Expected results:
the browser should shows the page instead of crashing the system


Additional info:
 dmesg | grep -e DMAR -e IOMMU
[    0.000000] ACPI: DMAR 00000000bf7900f0 00090 (v01    AMI  OEMDMAR 00000001 MSFT 00000097)
[    0.000000] Your BIOS is broken; DMAR reported at address fed90000 returns all ones!
[    0.018478] dmar: IOMMU: failed to map dmar0
[    0.018481] dmar: parse DMAR table failure.

Comment 1 Bill Nottingham 2013-06-03 17:15:31 UTC

Moving to kernel for the crash. Do you have a full dmesg? The issue may be entirely unreleated to the DMAR warning.

Comment 2 Josh Boyer 2013-07-01 18:25:35 UTC

No reply to Bill's question.  The DMAR message is a BIOS issue we can't fix.