Bug 168949 - Replace "low quality" error message when memory parity errors.
Replace "low quality" error message when memory parity errors.
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Larry Woodman
Brian Brock
IT_50366
Kernel
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-09-21 12:06 EDT by Linda Wang
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-21 15:45:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Linda Wang 2005-09-21 12:06:58 EDT
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 13:59:29 EDT
We tried to make this change a long time ago and it was shot down out on
rhkernel-list.  

Larry Woodman

Note You need to log in before you can comment on or make changes to this bug.