Re: PHCO_31609 (PA-RISC)
- From: Vishwas Pai <noman@xxxxxxxxxxxxxx>
- Date: Mon, 26 Mar 2007 12:10:39 GMT
ArkanoiD wrote:
+--------------------------------------------+
| Processor activity |
+--------------------------------------------+
Processor 0 started it by HPMC'ing. Here is the stack trace:
stack trace for event 0
crash event was an HPMC
can not find unwind or stub descriptor for
pc==0x0`01c9e2b4
+--------------------------------------------+
That link is HP internal. CPU or some hardware is
causing the system to log a machine check. This
could be a H/W fault (most probable) or a software
issue (least probability).
==========
A Data I/O Fetch Timeout occurred while CPU 0 was
requesting information from a device at the path 10/0/14/2 (built-in
PCI device).
Memory/IO Controller Error Analysis Information:
The Memory/IO Controller only observed the Broadcast Error. It did
not log
any additional information about the HPMC.
==========
The above log shows that there is some dead card/
slot/I/O backplane etc. What card exists on 10/0/14/2 ?
Are using it ? If not - try shutdown-remove-reboot.
If that does not solve the problem, you should contact
HP-support and ask them to have look at the crash.
They may also do a HPMC analysis using the tombstone
files.
--vishwas.
.
- Follow-Ups:
- Re: PHCO_31609 (PA-RISC)
- From: ArkanoiD
- Re: PHCO_31609 (PA-RISC)
- From: ArkanoiD
- Re: PHCO_31609 (PA-RISC)
- References:
- PHCO_31609 (PA-RISC)
- From: ArkanoiD
- Re: PHCO_31609 (PA-RISC)
- From: Vishwas Pai
- Re: PHCO_31609 (PA-RISC)
- From: ArkanoiD
- PHCO_31609 (PA-RISC)
- Prev by Date: Re: How to kill your VxVM boot ;-)
- Next by Date: Re: PHCO_31609 (PA-RISC)
- Previous by thread: Re: PHCO_31609 (PA-RISC)
- Next by thread: Re: PHCO_31609 (PA-RISC)
- Index(es):