question on a kernal "uhhuh" message

[Dan Koehler]

At 04:14 PM 8/25/2008, you wrote:
>Subject: question on a kernal "uhhuh" message
>To: fedora-list at redhat.com
>Message-ID: <48B31A7A.6040309 at cs.cmu.edu>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>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
>
>I am assuming that the second occurrence of "(368/406):
>gstreamer-plugins-base-0.10.19.2.fc9.i386.rpm" indicates that it did
>finish that rpm given that the rpm_debug_check and Transaction Test
>seemed to have passed.
>
>So, I am figuring this is my computer burping somewhere. Even though it
>is trying to point me at my PCI bus, I do not know what test / diags I
>should be running to find out if there really is a hardware problem and,
>if so, where and then how to deal with it.
>
>Any suggestions appreciated ... if I can provide any more info, please
>let me know what would be helpful.
>
>This is related to my prior email "update error on F9 -- round two" if
>more context is needed.
>
>Thanks,
>Paul

The last time I got one of these "dazed and confused" messages was 
when I was running a Fedora distribution on a motherboard with 
multiple PCI domains.  Do you get a "dazed and confused" message 
during your boot process, or did it only show up during the yum update? 


-- 
SCANNED for viruses and
dangerous content by MailScanner.
Believed to be clean.