What caused the CPU panic?

[권진호]

My server(Digital UNIX V4.0E (Rev. 1091), AlphaServer 4100 5/466 4MB Physmem(MBytes): 2047)
rebooted unexpectedly and here is what was in the log...


_vm_swap_init: warning /sbin/swapdefault swap device not found
vm_swap_init: swap is set to lazy (over commitment) mode
Starting secondary cpu 1
fta0: Link Unavailable.
fta0: Link Available.
Environmental Monitoring Subsystem Configured.
fta0: Receive Overrun
fta0: Duplicate token found
fta0: MAC CRC Error: DA: ff-ff-ff-ff-ff-ff => SA: 00-00-f8-bc-cc-b9
panic (cpu 1): k_mape_op_bad: unsupported map entry operation
syncing disks... device string for dump = SCSI 1 2 0 0 0 0 0.
DUMP.prom: dev SCSI 1 2 0 0 0 0 0, block 1236565
device string for dump = SCSI 1 2 0 0 0 0 0.
DUMP.prom: dev SCSI 1 2 0 0 0 0 0, block 1236565


What does "panic (cpu 1): k_mape_op_bad: unsupported map entry operation" mean? It looks all foreign to me.

Thanks

[Hein van den Heuvel]

One would suspects that the network link error has something to do with the crash, but without timestamps it might be irrelevant.

Check the /var/adm/crash directory for the most recent crash-data.n file.
Read that for more clues.

Check man pages for crashdc

Mostly though you shoulf take this crash as a trigger to move to a more supported Tru64 version: 4.0F/G which is in Prior Version Support. This may well be a know, and fixed problem. (Bad reaction to an external problem)

Perhaps move the the latests and greatests?
See:
http://h30097.www3.hp.com/pdf/Tru64_Roadmap_Current.pdf


Good luck,
Hein.

/var/adm/crash