cancel
Showing results for 
Search instead for 
Did you mean: 

MP Log

 
SOLVED
Go to solution
mark.M
Frequent Advisor

MP Log

i'm find MP Log, what is it??

Log Entry 225: 28 Feb 2007 06:02:40
Alert Level 5: Critical
Keyword: MEM_PDT_TABLE_FULL
Cannot add PDT entry-PDT full
Logged by: System Firmware 0
Data: Data field unused
0xA08000D800E01520 0000000000000000

Log Entry 223: 28 Feb 2007 05:47:40
Alert Level 5: Critical
Keyword: MEM_PDT_TABLE_FULL
Cannot add PDT entry-PDT full
Logged by: System Firmware 0
Data: Data field unused
0xA08000D800E014F0 0000000000000000


Log Entry 222: 28 Feb 2007 05:47:40
Alert Level 5: Critical
Keyword: SYSTEM_FIRMWARE_ERROR
System firmware error
Logged by: Redundant w/ an E0 code;
Sensor: System Firmware Progress
Data2: PRV State: 0x3F
0xC145E5177C0214E0 FF3F4070000F0300

Log Entry 221: 28 Feb 2007 05:32:40
Alert Level 5: Critical
Keyword: MEM_PDT_TABLE_FULL
Cannot add PDT entry-PDT full
Logged by: System Firmware 0
Data: Data field unused
0xA08000D800E014C0 0000000000000000


Log Entry 220: 28 Feb 2007 05:32:40
Alert Level 5: Critical
Keyword: SYSTEM_FIRMWARE_ERROR
System firmware error
Logged by: Redundant w/ an E0 code;
Sensor: System Firmware Progress
Data2: PRV State: 0x3F
0xC145E513F80214B0 FF3F4070000F0300


# Location|Alert| Encoded Field | Data Field | Keyword / Timestamp
-------------------------------------------------------------------------------
225 SFW 0 *5 0xA08000D800E01520 0000000000000000 MEM_PDT_TABLE_FULL
28 Feb 2007 06:02:40
224 SFW *5 0xC145E51B00021510 FF3F4070000F0300 SYSTEM_FIRMWARE_ERROR
28 Feb 2007 06:02:40
223 SFW 0 *5 0xA08000D800E014F0 0000000000000000 MEM_PDT_TABLE_FULL
28 Feb 2007 05:47:40
222 SFW *5 0xC145E5177C0214E0 FF3F4070000F0300 SYSTEM_FIRMWARE_ERROR
28 Feb 2007 05:47:40
221 SFW 0 *5 0xA08000D800E014C0 0000000000000000 MEM_PDT_TABLE_FULL
28 Feb 2007 05:32:40
220 SFW *5 0xC145E513F80214B0 FF3F4070000F0300 SYSTEM_FIRMWARE_ERROR
28 Feb 2007 05:32:40
219 SFW 0 *5 0xA08000D800E01490 0000000000000000 MEM_PDT_TABLE_FULL
27 Feb 2007 21:17:34
218 SFW *5 0xC145E49FEE021480 FF3F4070000F0300 SYSTEM_FIRMWARE_ERROR
27 Feb 2007 21:17:34
217 SFW 0 *5 0xA08000D800E01460 0000000000000000 MEM_PDT_TABLE_FULL
27 Feb 2007 21:02:34
4 REPLIES 4
Matti_Kurkela
Honored Contributor
Solution

Re: MP Log

PDT is Page Deallocation Table.

If my understanding is correct, when a memory address produces repeated errors, the system uses PDT to disable the faulty bit of memory.

This happens at the hardware/firmware level, so the maximum size of the PDT is fixed.

PDT_TABLE_FULL errors mean that you have some memory that has so many failing locations the PDT cannot handle them all. If the fault gets worse, the system can no longer protect you from using known-bad bits of memory.

Recommendation: locate the faulty DIMM and replace it/have it replaced by HP.

The STM diagnostics (cstm/mstm/xstm) will usually give more human-readable information about the location of the failing DIMM.
MK
Steven E. Protter
Exalted Contributor

Re: MP Log

Shalom,

You should be able to identify the specific memory chip thats gone bad with cstm. You already have enough information to do an HP Hardware call unless you've used Non-HP memory.

The replacement will require downtime.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
MHudec
Frequent Advisor

Re: MP Log

All was lovely said. Just some more information: once in STM (I prefer cstm):

1. run logtool (type ru, select 2 for logtool)
2. type vda (shows you deallocation information)
-OR-
2. type vd (shows you entire memory log).
Andrew Rutter
Honored Contributor

Re: MP Log

mark,

you can also clear the pdt table aswell, this will free up room for more or duplicates errors on the dimms until you can have them replaced

this requires a reboot to PDC level

reboot the server and stop it from booting.

select service from main menu at BCH

Ma > ser

Ser > pdtclear

this will then reset the system afterwards and reboot again. From here it can boot up normally.


Andy