System freeze

[Roro_2]

Hello,

Our customer had an rp7410 server running HPUX 11i v1.
the server hanged twice since 10 days.
please find below some details and some attached files.

thanks and regards

Roger

# /opt/resmon/bin/resdata -R 540606466 -r /system/events/chassis/chassis_log -n 540606465 -a

ARCHIVED MONITOR DATA:

Event Time..........: Thu Dec 31 08:19:56 2009
Severity............: MAJORWARNING
Monitor.............: dm_chassis
Event #.............: 1311
System..............: hpnode2

Summary:
A DIMM was deallocated because the PDT was full.

Description of Error:

Chassis Code Keyword MEM_DIMM_ERR_DEALLOCATED.

A DIMM was successfully deallocated from system for the case where the PDT
was full. The system is still configured correctly and will function
properly but performance my be reduced.
Probable Cause / Recommended Action:

Cause:
Deallocation for a full PDT table

Action:
Replace the DIMM(s) that were deallocated

Additional Event Data:
System IP Address...: 172.16.7.51
Event Id............: 0x4b3cc11c00000004
Monitor Version.....: A.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_chassis.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/rp7410
EMS Version.....................: A.03.20
STM Version.....................: A.31.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm#1311

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v


Chassis Log Timestamp : 10/12/1945 01:13:13
Chassis Code Encoded Field : 0x2000464076001066
Alert Level : 4 (Unexpected configuration change detected.)
Source FRU : 7 (memory)
Source FRU Detail : 6 (physical memory)
Source ID : 0 (platform dependent)
Event Detail : 0 (no problem detail )
Caller Activity : 1 (test)
Caller Subactivity : 6 (implementation dependent)
Activity Status : 6 (implementation dependent)
Reporting Entity Type : 0 (system firmware)
Reporting Entity ID : 4
Data Type : 4 (physical location)
Message ID : 6
FRU Physical Location: 0x00ffff01ff0aff74
FRU Source = 7 (memory)
Source Detail = 4 (SIMM or DIMM)
Cabinet Location = 0
Cell Location = 1
DIMMS Rank = 10
umber o@

[Michal Kapalka (mikap) · Accepted solution]

hi,

did you check the EVENT ID :1311

Event 1311

Severity: MAJORWARNING
Event Summary: A DIMM was deallocated because the PDT was full.
Event Class: System
Problem Description:
Chassis Code Keyword MEM_DIMM_ERR_DEALLOCATED.

A DIMM was successfully deallocated from system for the case where the PDT was full. The system is still configured correctly and will function properly but performance my be reduced.

Probable Cause / Recommended Action:

Cause:
Deallocation for a full PDT table
Action:
Replace the DIMM(s) that were deallocated
Event Details:
Chassis Code Encoded Field : 0x2000084076001066
Alert Level : 4 (Unexpected configuration change detected.)
Source FRU : 7 (memory)
Source FRU Detail : 6 (physical memory)
Source ID : 0 (platform dependent)
Event Detail : 0 (no problem detail )
Caller Activity : 1 (test)
Caller Subactivity : 6 (implementation dependent)
Activity Status : 6 (implementation dependent)
Reporting Entity Type : 0 (system firmware)
Reporting Entity ID : 0 Cabinet 0 Cell 0 CPU 0
Data Type : 4 (physical location)
Message ID : 0 (not associated with other log entries)
FRU Physical Location: 0x0000000000000141
FRU Source = 4 (power entity)
Source Detail = 1 (AC mains)
Cabinet Location = 0
Card Cage Location = 0
Backplane Location = 0
Cell Location = 0
Level 5 (Impl. Dep.)= 0
Slot Number = 0

you could monitor the PDT via cstm, for example and if this error will be permamnet you should consider to replace the memory

mikap

[Nafez ALNajjar]

Marhaba,
PDT (Page Deallocation Table) is related to DIMM (Memory) error as if the system find ""double"" bit errors on any dimm at boot it will mark the accessed page as deallocated in the pdt and never access it.
Note:single bit errors are bypassed as it can be resolved with the CRC.
now the case is that there could be some bugs with your DIMMS so try to contact HP and replace them .
now you have an option to clear the pdt from the EFI by entering
SHELL>pdt clear,
but this will not solve the issue as it will be filled again.

Good luck

Nafez ALNajjar

[Vishu]

Hi Roro,

PDT is page deallocation table. It seems you have your PDT full bcoz of lots of single bit errors because of your DIMM memory. So, check that faulty DIMM with cstm and replce that memory. And dont forget the clear the PDT from the PDC menu.

Thanks

[Michael Steele_2]

Cause:
Deallocation for a full PDT table

Action:
Replace the DIMM(s) that were deallocated

HI

EMS always tells you the action that the manufacturer wants you to take. In this case, the manufacturer wants you to replace the DIMM.

[Roro_2]

Hello,

Thanks a lot for your support.
1- I have replaced 4 x DIMMS (4 x 512MB) in rank 0 but the problem (MEM deallocated) was not fixed.
NB : after powerig off the server and replacing the MEM , i could no more power on the cell and the cabinet.
After too many retries ( one hour) , i could power on the cell/cabinet.
Please advise.
2- how to clear the PDT from PDC.

Regards

Roger

[Ron Irving]

Hi Roro!!

Did you replace the memory yourself? It's always best practice to have HP, or a qualified maintenance provider do that for you.

Ok...make sure all of the memory is seated in properly, and remember your static discipline. Be sure that the memory is replaced EXACTLY in the order of slots as the old memory.

When the system boots up, enter PDC, (hit any key in 10 seconds to interrupt the boot process.)

When at the MAin menu, type SER to get to the service menu. Once there, type pdt clear to clear the deallocation table. The system will reboot. Let it spin up, and you should be good to go.

Be VERY careful pulling the cell, and putting it back in. Lots of sensitive stuff back there.

HTH

ron

[cnb]

Check/clear the PDT in the BCH menu. Command usage is in this manual:

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01868394/c01868394.pdf


Rgds,

[Roro_2]

Hi,

We have another problem with the second non system internal disk ( top right location ).
It is not detected by PDC ( search ) and by HPUX ( ioscan ).

Please advise.

Thanks

Roger

[Michal Kapalka (mikap)]

hi,

you should fix one problem and them go to the second, so at first fix the problem with the memory, boot from primary path and check if the system is up and running correctly,
them check the disk.

mikap