HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

attention light source

 
SOLVED
Go to solution
Mandosa
Regular Advisor

attention light source

i've an HP 5405 that has the attention light on. i've examined the error log using SL from gsp, but it doesn't appear to give me any usable information regarding the source of the problem. Here's the output

Log Entry # 0 :
SYSTEM NAME: xxxx-gsp
DATE: 12/29/2005 TIME: 19:36:23
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 74 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x1800002000FF6742 00000000 00000008 type 3 = Actual Data
0x5800082000FF6742 0000690B 1D132417 type 11 = Timestamp 12/29/2005 19:36:23

any ideas?
thx.
5 REPLIES 5
Steven E. Protter
Exalted Contributor

Re: attention light source

Shalom,

Welcome to the wonderful world of GSP messages.

Attention lights only are a prompt to read the messages as you did. There is no guarantee there will be any usable or actionable information in there.

Where I work, the attention light is allowed to flash. If I get a chance I clear them, but that just shows how anal I am.

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
Sameer_Nirmal
Honored Contributor
Solution

Re: attention light source

Hi,

Looking at the event log entry, it indicates a "machine check" has occured in the server. The 'machine check" could be either HPMC or LPMC. You need to check other entries besides this entry to know the cause of "machine check".
If it turns out to be HPMC , then most probably it is hardware trouble.

One has to know the circumstances of the trouble when started initially. It means
Is the server reboot automatically?
If it could boot thereafter , one can check the "/var/tomstones/ts99" file.
What you see in syslog, demsg, OLDsyslog, shutdownlog ?
Mandosa
Regular Advisor

Re: attention light source

system isn't automatically rebooted. Last reboot was Nov 10, this error timestamp is Dec 29.
syslog doesn't show any activity @ that time. and tombstones/ts99 looks ok. the last line of dmesg is: "LPMC type : D-Cache Parity Error". There's no time associated with it though. This is likely what triggered the attention light?
Sameer_Nirmal
Honored Contributor

Re: attention light source

Mark,

You are right.

As per the event log entry you posted, the "machine check " event could relates to a LPMC event. I think the event is probably related to the "D-Cache parity Error" which you see in dmesg causing the "attention" light up.

The parity error seems to be correctable and thus didn't give any trouble. The D-cache being referred is seems to be belongs to processor 1.
You will see the LPMC info in the "ts99" file for this error if you do either reboot the server or run "pdcinfo" command.
The problem could be a signal of "Big" trouble in near future and hence it is better to provide all these details to HP Support and get the expert advice and resolution.
Mandosa
Regular Advisor

Re: attention light source

pdinfo didn't show anything LPMC related. in fact it is identical to ts99 from November. i'm going to place a call with support services anyway.
thx.