HPMC Error Log Information

[Christian Aguilar Varga]

Hi all, This is my problem:
I have an E35 HP-9000 server, with HP-UX 9.04 installed.

The system was OK, before 9:00 am (now is 16:00) today. But suddenly after that hour the message in the attached file was displayed on the screen.

Then I reboot the system, It seemed that everithing was going to be ok, but when the login is shown, the system report a message about the CPU registers , besides the messages
in the attached file is shown again.

What can I do?

Any suggestion would be really appreciated.

Thanks

[Helen French]

There may be other intelligent answers, but here is just my thoughts:

HPMC error 7XXX is normally relates to system memory (RAM). The file shows some error on the module which is in slot 3A. You need to check this memory and if there is a problem, then replace it. The best option would be to call a H/W support. You can check the module with stm (or sysdiag), offline diagnostics etc.

If you are confident, then open the system and clean this solt and the module. Btw, 9.X is very old OS, consider updating your system to 10.X or 11.X (32 bit OS)

[PIYUSH D. PATEL]

Hi,

This error indicates something related to the memory 7xxx.

Call HP engg and let him observe the system.

Piyush

[Patrick Wessel]

Christian,
The memory SIMM in Slot 3A didn't respond to a request by the CPU (address 0x3A607800)
You may check with sysdiag if the diagnostics system logged memory errors for this SIMM or replace it.

[Bill Hassell]

Your E35 has a critical memory error and it is causing the system to crash and reboot (that's what HPMC means: High Priority Machine Check). Most likely it is a pair of memory modules but it may also be a processor failure...no way to diagnose that with HP-UX, you'll need hardware service with box of spare parts.

[Uli Manschke]

Sometimes its just a problem of contact - if you dare to do it yourself remove the mem modules and put them back in.
Or: maybe you can swap memory modules to other locations - it definitely is a HW problem.
Slot 3a causes the problem - try moving the memory from there to a higher slot number (if there is such ...??); it may be the failing module loads parts of the kernel during boot?
Regards
uli