- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: rp5470 GSP infomation
HPE 9000 and HPE e3000 Servers
1752318
Members
6332
Online
108786
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
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
тАО07-01-2010 11:21 PM
тАО07-01-2010 11:21 PM
rp5470 GSP infomation
All Dear Experts.
rp5470 Atten light on,and sel GSP log:
Log Entry # 0 :
SYSTEM NAME: ygapp1
DATE: 07/01/2010 TIME: 23:28:09
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: 01
0x1800102000FF6742 00000000 00000040 type 3 = Actual Data
0x5800182000FF6742 00006E06 01171C09 type 11 = Timestamp 07/01/2010 23:28:09
Type CR for next entry, Q CR to quit.
Log Entry # 1 :
SYSTEM NAME: ygapp1
DATE: 07/01/2010 TIME: 23:28:09
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: 72 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01
0x0000102000FF6722 00000000 00000001 type 0 = Data Field Unused
0x5800182000FF6722 00006E06 01171C09 type 11 = Timestamp 07/01/2010 23:28:09
Type CR for next entry, - CR for previous entry, Q CR to quit.
there is no system error log in hp-UX.
so what is the information refer?
rp5470 Atten light on,and sel GSP log:
Log Entry # 0 :
SYSTEM NAME: ygapp1
DATE: 07/01/2010 TIME: 23:28:09
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: 01
0x1800102000FF6742 00000000 00000040 type 3 = Actual Data
0x5800182000FF6742 00006E06 01171C09 type 11 = Timestamp 07/01/2010 23:28:09
Type CR for next entry, Q CR to quit.
Log Entry # 1 :
SYSTEM NAME: ygapp1
DATE: 07/01/2010 TIME: 23:28:09
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: 72 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01
0x0000102000FF6722 00000000 00000001 type 0 = Data Field Unused
0x5800182000FF6722 00006E06 01171C09 type 11 = Timestamp 07/01/2010 23:28:09
Type CR for next entry, - CR for previous entry, Q CR to quit.
there is no system error log in hp-UX.
so what is the information refer?
You may be disappointed if you fail,but you are doomed if you don't try.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2010 05:17 AM
тАО07-02-2010 05:17 AM
Re: rp5470 GSP infomation
> CALLER ACTIVITY: 6 = machine check STATUS: 2
This says the problem was a "machine check". If the system did not reboot as a result, it was a Low-Priority Machine Check (LPMC).
LPMCs are parity errors in a processor or memory, which the ECC circuitry could successfully correct automatically, so that your data is not corrupted. An uncorrectable error would cause a HPMC, which would cause the system to crash and reboot.
Use the STM diagnostics (cstm/mstm/xstm). Run the Information tool on memory and CPUs; you'll probably find something in the "Memory Error Log Information" part of the CPU information and/or that the Page Deallocation Table's "PDT Entries Used" value is non-zero.
If the system detects that a RAM memory page produces errors, it will use the PDT to mark it as unusable. A small number of used PDT entries is relatively normal in an old server (within the limits of "expected wear & tear); but if the number of used PDT entries is large and/or keeps increasing, there might be a reason for concern.
If you have a support agreement, you might want to send the STM output to your hardware support contact for evaluation.
MK
This says the problem was a "machine check". If the system did not reboot as a result, it was a Low-Priority Machine Check (LPMC).
LPMCs are parity errors in a processor or memory, which the ECC circuitry could successfully correct automatically, so that your data is not corrupted. An uncorrectable error would cause a HPMC, which would cause the system to crash and reboot.
Use the STM diagnostics (cstm/mstm/xstm). Run the Information tool on memory and CPUs; you'll probably find something in the "Memory Error Log Information" part of the CPU information and/or that the Page Deallocation Table's "PDT Entries Used" value is non-zero.
If the system detects that a RAM memory page produces errors, it will use the PDT to mark it as unusable. A small number of used PDT entries is relatively normal in an old server (within the limits of "expected wear & tear); but if the number of used PDT entries is large and/or keeps increasing, there might be a reason for concern.
If you have a support agreement, you might want to send the STM output to your hardware support contact for evaluation.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2010 04:51 PM
тАО07-04-2010 04:51 PM
Re: rp5470 GSP infomation
o i see,thank you,MK.
You may be disappointed if you fail,but you are doomed if you don't try.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2010 02:20 PM
тАО07-07-2010 02:20 PM
Re: rp5470 GSP infomation
Hi,
MCA indicates that the issue is due to a HW fault with the box, you should have a latest ts99 file under /var/tombstones. Attach the same here...
Best Regards,
Prashanth
MCA indicates that the issue is due to a HW fault with the box, you should have a latest ts99 file under /var/tombstones. Attach the same here...
Best Regards,
Prashanth
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