- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- L2000 crashes and system error code
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО03-27-2006 12:10 PM
тАО03-27-2006 12:10 PM
DATE: 03/24/2006 TIME: 17:10:33
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 32 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x1800002011006322 CB818000 00000000 type 3 = Actual Data
0x5800082011006322 00006A02 18110A21 type 11 = Timestamp 03/24/2006 17:10:33
Type CR for next entry, - CR for previous entry, Q CR to quit.
cr
DATE: 03/24/2006 TIME: 17:10:36
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 7 = memory
SOURCE DETAIL: 4 = SIMM or DIMM SOURCE ID: FF
PROBLEM DETAIL: 3 = double bit error
CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: B8 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 02
0x2000202374FF6B83 0000FF00 006BFF74 type 4 = Physical Location
0x5800282374FF6B83 00006A02 18110A24 type 11 = Timestamp 03/24/2006 17:10:36
Type CR for next entry, - CR for previous entry, Q CR to quit.
cr
DATE: 03/24/2006 TIME: 17:10:36
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: 46 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 02
0x0000202000FF6462 00000000 00000000 type 0 = Data Field Unused
0x5800282000FF6462 00006A02 18110A24 type 11 = Timestamp 03/24/2006 17:10:36
Type CR for next entry, - CR for previous entry, Q CR to quit.
cr
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2006 12:15 PM
тАО03-27-2006 12:15 PM
Re: L2000 crashes and system error code
It's time to place a hardware call to HP and have them take a look at your logs so they can pinpoint the DIMM/SIMM and fix the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2006 12:21 PM
тАО03-27-2006 12:21 PM
Re: L2000 crashes and system error code
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2006 02:03 PM
тАО03-27-2006 02:03 PM
SolutionAs per the event log entry, the memory module showing "double bit error" is at slot no 6B. The system shows machine check has occured which constitute a HPMC. Looking at the sequence of the 3 entries, the HPMC is seems to be occured by the memory module.
However you might want to see all other entries logged to know if something else is also being reported. You can collect those logs from MP alongwith /var/tombstones/ts99 & ts98 files and send it to HP for analysis.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2006 02:31 PM
тАО03-27-2006 02:31 PM
Re: L2000 crashes and system error code
Check your ts99 file(/var/tombstone/ts99)
Double bit error must replace memory.
Regards..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2006 09:02 PM
тАО03-27-2006 09:02 PM
Re: L2000 crashes and system error code
if your system crashed ervery night with this error messages at GSP-Log than this indicates an memoryissue. The system crashed every night at the same time? High workload at this time (backup)?
You can check the memory with cstm.
# cstm
# scl type mem
# info
# il
-> you can see
- the configuration
- errorlist (single bit / double bit)
- PDT entries (note: if PDT is used up to 100% the system didnt restart at next crash)
-> for deeper check you must call HP to get the password and see the whole logtool
If one or more adresses from memory are with high errorcount or more adresses from one DIMM this should be rplaced.
HP also can check the files at /var/tombstones/.
If there are double bit errors the DIMM must be replaced, if single bit errors at one adress or DIMM it seems like defective adress and system (ECC) cant dealocate this adress in cause of use from process. Powercycle helps in this case.
Regards
Mirko
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2006 02:24 AM
тАО03-29-2006 02:24 AM