HPE 9000 and HPE e3000 Servers
1748179 Members
4120 Online
108758 Solutions
New Discussion юеВ

Re: System Panic

 
SCSI Error
Regular Advisor

System Panic

Hi Everyone.

Please help me analyze the ts99.log file attached.
The system did panic several times.

Thank you
6 REPLIES 6
Taifur
Respected Contributor

Re: System Panic

Hi,

From provided log, there is memory related error. Check /var/adm/syslog/syslog.log


Rgds//
Taifur
Patrick Wallek
Honored Contributor

Re: System Panic

>>Check /var/adm/syslog/syslog.log

That should actually be /var/adm/syslog/OLDsyslog.log to see what happened prior to the crash.

You should also check /etc/shutdownlog.

There should be a crash dump, or several if the system paniced several times, in /var/adm/crash. The most recent (newest) will have a .0 extension. If you have a support contract you should get this dump analyzed by HP.
SCSI Error
Regular Advisor

Re: System Panic

Thanks,

I found some EMS alerts. Is this something related?

Summary:
Adapter at hardware path 0/2/0/0 : Received an interrupt indicating that a
primitive was transmitted


Description of Error:


lbolt value: 4197

The Fibre Channel Driver received an interrupt indicating
that a primitive was transmitted
Frame Manager Status Register = 0xa002c480

Basheer_2
Trusted Contributor

Re: System Panic

do

lastb root
lastb reboot
Jozef_Novak
Respected Contributor

Re: System Panic

Hello,

The EMS event you received is Fibre Channel related and should be informational only. It tells you that a FC protocol primitive was transmitted, likely due to fabric / arbitrated loop initialization.

You can check memory error log via STM.

J.
Senthil-kumar
Occasional Advisor

Re: System Panic

The analysis of ts99 files reveal that the issue is with the system board. Get it replaced.