Bug 1382612

Summary:	.../dmesg subtest should ignore "WARNING: at drivers/pci/dmar.c:597 warn_invalid_dmar+0x7a/0x90()"
Product:	[Retired] Beaker	Reporter:	Jan Hutař <jhutar>
Component:	tests	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	22	CC:	jikortus, mjia
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-21 14:14:58 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:

Description Jan Hutař 2016-10-07 08:06:24 UTC

Description of problem:
.../dmesg subtest should ignore "WARNING: at drivers/pci/dmar.c:597 warn_invalid_dmar+0x7a/0x90()"


Version-Release number of selected component (if applicable):
Current internal Beaker 23.2
On a server where this happened was kernel-2.6.32-642.el6.x86_64


How reproducible:
always


Steps to Reproduce:
1. Install OS and boot system


Actual results:
First test after installation fails


Expected results:
User should not be alerted about this


Additional info:

Checking dmesg for specific failures!
------------[ cut here ]------------
WARNING: at drivers/pci/dmar.c:597 warn_invalid_dmar+0x7a/0x90() (Not tainted)
Hardware name: HP Z200 Workstation
[Firmware Warn]: Your BIOS is broken; DMAR reported at address fed93000 returns all ones!
BIOS vendor: Hewlett-Packard; Ver: 786H3 v01.21; Product Version:  
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.32-642.el6.x86_64 #1
Call Trace:
 [<ffffffff8107c911>] ? warn_slowpath_common+0x91/0xe0
 [<ffffffff8107c9bf>] ? warn_slowpath_fmt_taint+0x3f/0x50
 [<ffffffff81046c2d>] ? native_set_pte_at+0xd/0x40
 [<ffffffff81046569>] ? native_flush_tlb_single+0x9/0x10
 [<ffffffff812d42aa>] ? warn_invalid_dmar+0x7a/0x90
 [<ffffffff81c6d369>] ? check_zero_address+0xda/0x110
 [<ffffffff8131c1b3>] ? acpi_get_table_with_size+0x5a/0xb4
 [<ffffffff81553d15>] ? _etext+0x0/0x3
 [<ffffffff81c6d3b1>] ? detect_intel_iommu+0x12/0x95
 [<ffffffff81c43b7d>] ? pci_iommu_alloc+0x67/0x76
 [<ffffffff81c588ce>] ? mem_init+0x19/0xec
 [<ffffffff81c3af1f>] ? start_kernel+0x221/0x431
 [<ffffffff81c3a33a>] ? x86_64_start_reservations+0x125/0x129
 [<ffffffff81c3a453>] ? x86_64_start_kernel+0x115/0x124
---[ end trace a7919e7f17c0a725 ]---
------------[ cut here ]------------
WARNING: at drivers/pci/dmar.c:597 warn_invalid_dmar+0x7a/0x90() (Tainted: G          I-- ------------   )
Hardware name: HP Z200 Workstation
[Firmware Warn]: Your BIOS is broken; DMAR reported at address fed93000 returns all ones!
BIOS vendor: Hewlett-Packard; Ver: 786H3 v01.21; Product Version:  
Modules linked in:
Pid: 1, comm: swapper Tainted: G          I-- ------------    2.6.32-642.el6.x86_64 #1
Call Trace:
 [<ffffffff8107c911>] ? warn_slowpath_common+0x91/0xe0
 [<ffffffff8107c9bf>] ? warn_slowpath_fmt_taint+0x3f/0x50
 [<ffffffff810527b8>] ? __ioremap_caller+0x2a8/0x390
 [<ffffffff812d42aa>] ? warn_invalid_dmar+0x7a/0x90
 [<ffffffff812d456f>] ? alloc_iommu+0x2af/0x310
 [<ffffffff81c6d5cd>] ? dmar_table_init+0x199/0x345
 [<ffffffff81c4dc22>] ? enable_IR_x2apic+0x10/0x1bd
 [<ffffffff81c4e52d>] ? default_setup_apic_routing+0x16/0x7b
 [<ffffffff81c4bc92>] ? native_smp_prepare_cpus+0x370/0x397
 [<ffffffff81c3a8e7>] ? kernel_init+0x10b/0x2f7
 [<ffffffff8100969d>] ? __switch_to+0x7d/0x340
 [<ffffffff8100c28a>] ? child_rip+0xa/0x20
 [<ffffffff81c3a7dc>] ? kernel_init+0x0/0x2f7
 [<ffffffff8100c280>] ? child_rip+0x0/0x20
---[ end trace a7919e7f17c0a726 ]---

End of log.

Comment 2 Jan Hutař 2016-10-07 08:08:03 UTC

Forgot to notice that this was rejected by kernel development:

Bug 737764 - WARNING: at drivers/pci/dmar.c:594 warn_invalid_dmar+0x7a/0x90()

Comment 4 Dan Callaghan 2016-10-10 03:17:24 UTC

I guess we want to filter this only on specific hardware models where we know it's broken and nobody is going to fix it... seems to be at least:

HP Z200 Workstation
HP xw4600 Workstation

Any others?

(Incidentally, I wonder did anyone ever tell HP that Linux thinks their firmware is broken? Presumably newer models don't show this same warning...?)

Comment 5 Jiri Kortus 2018-04-18 13:01:05 UTC

Hello Jan, Dan,

are there any updates regarding this bug? I occasionally spot the kernel warning making our Beaker jobs fail, so probably it would be helpful if this could be worked around in Beaker, as long as it is really just a warning and the firmware bug doesn't in fact break anything (and I suppose we can't count on the real issue, i. e. the bug in firmware, being fixed).

Thanks,
Jirka

Comment 6 Roman Joost 2018-04-19 05:01:50 UTC

Dear Jiri,

Beaker was put into maintenance for a year and has just been resurrected with a team of two. There are unfortunately no updates on this bug, since we're currently dealing only with urgent bugs (e.g. RHEL8). I understand that this can be annoying, but if it's not a total blocker at the moment it'll have to wait.