question on a kernal "uhhuh" message

[Paul Newell]

Rick Stevens wrote:
> Paul Newell wrote:
>> Alain Spineux wrote:
>>> On Mon, Aug 25, 2008 at 10:47 PM, Paul Newell <pnewell at cs.cmu.edu> 
>>> wrote:
>>>> While running a long "yum update", I got the following message in 
>>>> the middle:
>>>>
>>>>   (367/406): cscope-15.6-2.fc9.i386.rpm                    | 141
>>>>   kB     00:01       (368/406): gstreamer-p  86% |  20% |==        
>>>> |  57
>>>> kB/s | 192
>>>>   kB     00:12 ETA
>>>>   Message from syslogd at chowder at Aug 25 11:55:03 ...
>>>>    kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.
>>>>
>>>>   Message from syslogd at chowder at Aug 25 11:55:03 ...
>>>>    kernel: You have some hardware problem, likely on the PCI bus.
>>>>
>>>>   Message from syslogd at chowder at Aug 25 11:55:03 ...
>>>>    kernel: Dazed and confused, but trying to continue
>>>>   (368/406): gstreamer-plugins-base-0.10.19-2.fc9.i386.rpm | 929
>>>>   kB     00:12       (369/406): exempi-2.0.1-1.fc9.i386.rpm
>>>>   | 297
>>>>   kB     00:03
>>>>
>>> Any RedHat compatible distribution, has a memory test included in the
>>> first install CD.
>>> Just boot on it, an type memtest or mem86 or memtes86 or something
>>> like that to start the test.
>>> Be carrefull, some VGA adapter share the begining of the memory and
>>> this part of the memory must be
>>> skipped to avoid false error.
>>>  
>> Alain:
>>
>> I installed off a DVD, which should be the same, so my one question 
>> before I try this is "at what point to I get it to not do an 
>> install/update but to give me a terminal (or single-user window) so I 
>> can execute this command. Actually, being new to this, I don't even 
>> know if this is something I get a terminal / single-user window for 
>> as I don't know how early I am jumping in.
> Boot off the CD/DVD.  At the "boot:" prompt, enter "memtest86" and off
> you go.
>
Thanks for the clarification on Alain's suggestion. I ran the test and 
it immediately failed. To make sure I was doing things right, I tried in 
on another machine (which worked) and am trying it on a third machine 
(which I will check in on tomorrow morning)..

Though I am not seeing any problems running on the machine that reported 
the error during yum update, I am figuring "I gotta hardware problem". I 
am attaching a file of my transciption of the error with the hopes of 
getting some confirmation / education / advice / sympathy / etc.

Thanks for the help in teaching me where the testing stuff is on Fedora,
Paul
===
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: F9_memtest86_failure.txt
Url: http://lists.fedoraproject.org/pipermail/users/attachments/20080825/a5f3220c/attachment-0001.txt