Bug 485361

Summary:	INFO test always fail with a tainted kernel value of 16 in RHEL4.7 x86_64
Product:	[Retired] Red Hat Hardware Certification Program	Reporter:	abel0301 <abel.cm.lee>
Component:	Test Suite (tests)	Assignee:	Greg Nichols <gnichols>
Status:	CLOSED NOTABUG	QA Contact:	Lawrence Lim <llim>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.2	CC:	rlandry, tools-bugs, ykun
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:	2009-02-17 02:21:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description abel0301 2009-02-13 01:56:56 UTC

Description of problem:
Installation of RHEL4.7 X86_64 with full software package installed. This causes a tainted kernel with a /proc/sys/kernel/tainted value of 16. The error causes a INFO test job always fail for hardware certification. but PASSED on RHEL4.7 X86 with full software package installed.

The issue is similar to Bug 481690

Version-Release number of selected component (if applicable):
HTS version 5.2 release 20
RHEL4.7 x86_64 kernel-largesmp-2.6.9-78.EL

How reproducible:
Every time.


Steps to Reproduce:
1. Install RHEL4.7 x86_64 with full software package installed
2. Check contents of /proc/sys/kernel/tainted
3. Value is 16 (non-zero)
4. Run 'hts certify --test info' or any other test that includes INFO, INFO will
fail.

  
Actual results:
INFO fail with Tainted kernel.

Expected results:
Non-tainted kernel with INFO pass.

Additional info:
INFO test PASSED on RHEL4.7 X86 with full software package installed without tainted kernel

Comment 1 abel0301 2009-02-13 08:00:14 UTC

Verified and Passed INFO testing on RHEL4.6 x86_64 (full software package installed) without tainted kernel

Comment 2 Rob Landry 2009-02-13 15:35:54 UTC

A value of 16 most likely means your box suffered from an unknown MCE which means you'll need to check the system board logs to find out.  The typical cause is bad RAM but it isn't exclusive to this.

Comment 3 abel0301 2009-02-17 02:21:27 UTC

This strange problem fixed with our stable firmware and thanks to Rob for your great information.