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@chowder at Aug 25 11:55:03 ...
kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.

Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: You have some hardware problem, likely on the PCI bus.

Message from syslogd@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

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

At 04:14 PM 8/25/2008, you wrote:

Subject: question on a kernal "uhhuh" message
To: fedora-list@redhat.com
Message-ID: <48B31A7A.6040309@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@chowder at Aug 25 11:55:03 ...
kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.

Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: You have some hardware problem, likely on the PCI bus.

Message from syslogd@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.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Dan Koehler wrote:

At 04:14 PM 8/25/2008, you wrote:

Subject: question on a kernal "uhhuh" message
To: fedora-list@redhat.com
Message-ID: <48B31A7A.6040309@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@chowder at Aug 25 11:55:03 ...
kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.

Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: You have some hardware problem, likely on the PCI bus.

Message from syslogd@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?



Dan:

Only during the yum update. To the best of my memory, I haven't seen a
dazed and confused on this machine since I got it with FC5 back in
mid-2006 ... but I could never get it connected to the net so this is
the first time I have run yum on it.


Thanks,
Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Mon, Aug 25, 2008 at 10:47 PM, Paul Newell <pnewell@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@chowder at Aug 25 11:55:03 ...
> kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.
>
> Message from syslogd@chowder at Aug 25 11:55:03 ...
> kernel: You have some hardware problem, likely on the PCI bus.
>
> Message from syslogd@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 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.

>
> 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
>
> --
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>



--
Alain Spineux
aspineux gmail com
May the sources be with you

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Alain Spineux wrote:

On Mon, Aug 25, 2008 at 10:47 PM, Paul Newell <pnewell@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@chowder at Aug 25 11:55:03 ...
kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.

Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: You have some hardware problem, likely on the PCI bus.

Message from syslogd@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 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.


For what it is worth, I don't see any errors in the while process of
powering up the machine, but maybe the boot process isn't doing all the
tests you are suggesting.


Thanks,
Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Paul Newell wrote:

Alain Spineux wrote:

On Mon, Aug 25, 2008 at 10:47 PM, Paul Newell <pnewell@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@chowder at Aug 25 11:55:03 ...
kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.

Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: You have some hardware problem, likely on the PCI bus.

Message from syslogd@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 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.



For what it is worth, I don't see any errors in the while process of
powering up the machine, but maybe the boot process isn't doing all the
tests you are suggesting.


Thanks,
Paul




--
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer rps2@nerd.com -
- Hosting Consulting, Inc. -
- -
- "Very funny, Scotty. Now beam down my clothes." -
----------------------------------------------------------------------

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Rick Stevens wrote:

Paul Newell wrote:

Alain Spineux wrote:
On Mon, Aug 25, 2008 at 10:47 PM, Paul Newell <pnewell@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@chowder at Aug 25 11:55:03 ...
kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.

Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: You have some hardware problem, likely on the PCI bus.

Message from syslogd@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
===
Memtest86 v2.01 | Pass 0%
Xeon DP (0.13) 2394 MHz | Test 3% #
L1 Cache: 8K 19626 Mb/s | Test #1 [Address test, own address]
L2 Cache: 512K 16742 Mb/s | Testing: 128K - 2047M 2047M
Memory: 2047M 1039 Mb/s | Pattern:
Chaipset: Intel i860 (ECC: Detect / Correct)

WallTime Cached RsvdMem MemMap Cache ECC Test Pass Errors ECC Errs
--------- ------ ------- -------- ----- --- ---- ---- ------ --------
0:00:02 2047M 676K e820-Std on on Std 0 1 0
----------------------------------------------------------------------
Unexpected Interrupt -- Halting
Stack
Type: Gen-Prot eax: 00000000 0001db4c 0a100000 0001db7c 0001dc2c
DC: 00002504 ebx: 0a100000 0001db50 00000000 0001db80 0001dc20
CS: 00000010 ecx: 800000c8 0001db54 0000000d 0001db84 00000001
Eflag: 00010002 edx: 0a100000 0001db58 00000000 0001db88 0001cad4
Code: 00000000 edi: 09dee660 0001db5c 00002504 0001db8c 0001dc20
esi: 7fefef00 0001db60 00000010 0001db90 00000002
ebp: 00000000 0001db64 00010002 0001db94 0001dc20
esp: 0001db4c 0001db68 00000002 0001db98 0000339d
0001db6c 00000000 0001db9c 00000000
CS:EIP: cf 8d 76 00 00 9f 00 10 25 0001db70 00003882 0001dba0 00000000
0001db74 00000010 0001dba4 00000000
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Paul Newell wrote regarding memtest86 results:
> 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".

One of my Frankenstein boxes, made from left over computer parts, had
faulty RAM. The system would often run fine, there'd be occasional
faults. I didn't know it had faulty memory at the time, it didn't have
Linux on it, and had never been subjected to the memtest86 program. It
was much later on that it got tested, and it failed the test every time.
As an experiment, I left it running as a webserver. It continued to
work most of the time, but would occasionally die. It must have just
been luck that the faulty part of the memory wasn't being used, or was
being used by something that didn't notice the fault.

Moral of the story: A computer that apparently works fine can still
have faults, you've just not seen them yet, or not associated some
apparent software faults with actual hardware faults.

--
[tim@localhost ~]$ uname -r
2.6.25.14-108.fc9.i686

Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Tim wrote:

Paul Newell wrote regarding memtest86 results:


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".



One of my Frankenstein boxes, made from left over computer parts, had
faulty RAM. The system would often run fine, there'd be occasional
faults. I didn't know it had faulty memory at the time, it didn't have
Linux on it, and had never been subjected to the memtest86 program. It
was much later on that it got tested, and it failed the test every time.
As an experiment, I left it running as a webserver. It continued to
work most of the time, but would occasionally die. It must have just
been luck that the faulty part of the memory wasn't being used, or was
being used by something that didn't notice the fault.

Moral of the story: A computer that apparently works fine can still
have faults, you've just not seen them yet, or not associated some
apparent software faults with actual hardware faults.


Appreciate the comment, thanks. I can live with a fault if I know
whether it is going to bite me or not later on. I've sent the memtest68
output to manufacturer to see if I can get more info (understanding that
their assumed stance will be "must replace" ... I'm just hoping to get a
"what is it?").


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Boot off the CD/DVD. At the "boot:" prompt, enter "memtest86" and off
you go.


Is there a "memtestppc", as well?

Listing bootable images showed a "check". When I gave that a run, it
went for a while, to something more than 70% and then wandered off
into the ether -- black screen, as if it openfirmware had put it to
sleep, but it wouldn't wake up.


The Fedora 9 powerPC netinstall doesn't seem to have any alternative
images at all.


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines