Bug 168949

Summary:	Replace "low quality" error message when memory parity errors.
Product:	Red Hat Enterprise Linux 4	Reporter:	Linda Wang <lwang>
Component:	kernel	Assignee:	Larry Woodman <lwoodman>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	jbaron
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	IT_50366
Whiteboard:	Kernel
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-09-21 19:45:21 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 Linda Wang 2005-09-21 16:06:58 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4

Description of problem:
Current message is:
  printk("Uhhuh. NMI received. Dazed and confused, but trying to continue\n");
  printk("You probably have a hardware problem with your RAM chips\n");

AOL would prefer it be more descriptive and more professional, like:
  printk("NMI received. Memory parity error detected. Attempting to continue.\n");
  printk("You probably have a hardware problem with your RAM chips\n");

The message is inside a function called mem_parity_error in
arch/{i386,x86_64}/kernel/traps.c



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

How reproducible:
Always

Steps to Reproduce:
1.boot the kernel
2.load a test driver module that loops forever
3.it will trigger NMI
  

Actual Results:  Current message is:
  printk("Uhhuh. NMI received. Dazed and confused, but trying to continue\n");
  printk("You probably have a hardware problem with your RAM chips\n");

Expected Results:  Something different

Additional info:

RHEL3U7 version of this bug is in bug 135455

Comment 1 Larry Woodman 2005-09-21 17:59:29 UTC

We tried to make this change a long time ago and it was shot down out on
rhkernel-list.  

Larry Woodman