- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: SRM meesage
Operating System - Tru64 Unix
1753463
Members
4489
Online
108794
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2009 10:23 PM
тАО09-27-2009 10:23 PM
Hello,
Our customer has an ES40 Alpha server Model 2 running Tru64 Unix 5.1 with one CPU 667 MhZ.
We noticed that after powering up the server and before getting SRM prompt P00>> , the following message is dispalyed on console :
unexpexted system evrnt through vector 680 on CPU 0
os_flags 00000000000
cchip_dirx 0004000000000
tig_smir 00000000000008
tig_cpuir 00000000000001
|
|
reserved_1 0000000000000
NB : I changed the CPU and the problem still not fixed.
Our customer has an ES40 Alpha server Model 2 running Tru64 Unix 5.1 with one CPU 667 MhZ.
We noticed that after powering up the server and before getting SRM prompt P00>> , the following message is dispalyed on console :
unexpexted system evrnt through vector 680 on CPU 0
os_flags 00000000000
cchip_dirx 0004000000000
tig_smir 00000000000008
tig_cpuir 00000000000001
|
|
reserved_1 0000000000000
NB : I changed the CPU and the problem still not fixed.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2009 01:54 AM
тАО09-28-2009 01:54 AM
Re: SRM meesage
Hello Roro!
You are having an environmental error, which causes a "logout frame" (those numbers you posted) to be printed on SRM. Each line corresponds to part (offset) within this frame but there seem to be some fields missing. Could you please post the fields (lines) between tig_cpuir and reserved_1 too?
Kind regards,
Kobylka
You are having an environmental error, which causes a "logout frame" (those numbers you posted) to be printed on SRM. Each line corresponds to part (offset) within this frame but there seem to be some fields missing. Could you please post the fields (lines) between tig_cpuir and reserved_1 too?
Kind regards,
Kobylka
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2009 02:35 AM
тАО09-28-2009 02:35 AM
Re: SRM meesage
Hi Kobylka,
Thank you for your concern.
please find below the missing fields:
tig_cpuir 0000000000001
tig_psir 0000000000003
ln78_isr 0000000000000
door_open 0000000000000
temp_warning 0000000000000
fan_ctrl_fault 0004000000000
power_down_code 0000000000000
reserved_1 0000000000000
Regards
Roger
Thank you for your concern.
please find below the missing fields:
tig_cpuir 0000000000001
tig_psir 0000000000003
ln78_isr 0000000000000
door_open 0000000000000
temp_warning 0000000000000
fan_ctrl_fault 0004000000000
power_down_code 0000000000000
reserved_1 0000000000000
Regards
Roger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2009 04:01 AM
тАО09-28-2009 04:01 AM
Solution
Hello Roro!
I've been checking your values and am a bit confused by the value in
fan_ctrl_fault 0004000000000
For sure, the problem is related to either:
- System fan (any of fans 1 - 6 not responding to RMC)
- CPU fan (fans 5 - 6 , speed issues)
- PCI fan (fans 1 - 4, speed issues)
Maybe some fan is not working correctly or your ES40 is simply overheating. For a description of the fans in the system refer to "ES40 Service Guide - 1.12 Fans"
Confusion arises when trying to decode the bitmask because valid bits for field "fan_ctrl_fault" range between 0 - 11 (12 bits in total, counting from right to left) and your fan_ctrl_fault bitmask has bit 38 set (!!!).
I would strongly suggest to use Compaq Analyzer to interpret this error fault.
Boot into the OS (Tru64 or OVMS) and start CA. It will display error events for localhost by default and give you way more information on the actual failure.
Kind regards,
Kobylka
I've been checking your values and am a bit confused by the value in
fan_ctrl_fault 0004000000000
For sure, the problem is related to either:
- System fan (any of fans 1 - 6 not responding to RMC)
- CPU fan (fans 5 - 6 , speed issues)
- PCI fan (fans 1 - 4, speed issues)
Maybe some fan is not working correctly or your ES40 is simply overheating. For a description of the fans in the system refer to "ES40 Service Guide - 1.12 Fans"
Confusion arises when trying to decode the bitmask because valid bits for field "fan_ctrl_fault" range between 0 - 11 (12 bits in total, counting from right to left) and your fan_ctrl_fault bitmask has bit 38 set (!!!).
I would strongly suggest to use Compaq Analyzer to interpret this error fault.
Boot into the OS (Tru64 or OVMS) and start CA. It will display error events for localhost by default and give you way more information on the actual failure.
Kind regards,
Kobylka
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP