- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Alpha ES40 rebooted with "Machine check processor ...
Operating System - Tru64 Unix
1753774
Members
6851
Online
108799
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-04-2005 12:06 AM
тАО07-04-2005 12:06 AM
Alpha ES40 rebooted with "Machine check processor fatal abort" error
Hi to ALL,
I have compaq alpha server ES40 with tru64 v5.1b o/s in a cluster mode,Firmware revision: 6.3-2
My server got rebooted with the below mentioned error.
Jul 1 22:26:04 atd1 vmunix: Machine Check Processor Fatal Abort
Jul 1 22:26:04 atd1 vmunix: Machine check code = 0x1000000a0
Jul 1 22:26:04 atd1 vmunix: Ibox Status = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Dcache Status = 0000000000000008
Jul 1 22:26:04 atd1 vmunix: Cbox Address = 0000000101dbcd40
Jul 1 22:26:04 atd1 vmunix: Fill Syndrome 1 = 00000000000000d3
Jul 1 22:26:04 atd1 vmunix: Fill Syndrome 0 = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Cbox Status = 000000000000000b
Jul 1 22:26:04 atd1 vmunix: EV6 captured status of Bcache mode = 000000000000000d
Jul 1 22:26:04 atd1 vmunix: EV6 Exception Address = 0000000122af84d0
Jul 1 22:26:04 atd1 vmunix: EV6 Interrupt Enablement and Current Processor mode = 0000007ee0000008
Jul 1 22:26:04 atd1 vmunix: EV6 Interrupt Summary Register = 0000000080000000
Jul 1 22:26:04 atd1 vmunix: EV6 TBmiss or Fault status = 0000000000000290
Jul 1 22:26:04 atd1 vmunix: EV6 PAL Base Address = 0000000000018000
Jul 1 22:26:04 atd1 vmunix: EV6 Ibox control = fffffe0006304396
Jul 1 22:26:04 atd1 vmunix: EV6 Ibox Process_context = 0000080000000004
Jul 1 22:26:04 atd1 vmunix: O/S Summary flag = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Cchip Base Address (phys) = 00000f01a0000000
Jul 1 22:26:04 atd1 vmunix: Cchip Device Raw Interrupt Request = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: DRIR Register Decode:
Jul 1 22:26:04 atd1 vmunix: PCI Device Interrupt Mask = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Cchip Miscellaneous Register = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Misc Register Decode:
Jul 1 22:26:04 atd1 vmunix: Cchip Revision: 00
Jul 1 22:26:04 atd1 vmunix: ID of CPU performing read: 00
Jul 1 22:26:04 atd1 vmunix: Pchip 0 Base Address (phys) = 00000f0180000000
Jul 1 22:26:04 atd1 vmunix: Pchip 0 Error Register = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Pchip Error Register Decode:
Jul 1 22:26:04 atd1 vmunix: PCI Xaction Start Address = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: PCI Command: Interrupt Acknowledge
Jul 1 22:26:04 atd1 vmunix: Pchip 1 Base Address (phys) = 00000f0380000000
Jul 1 22:26:04 atd1 vmunix: Pchip 1 Error Register = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Pchip Error Register Decode:
Jul 1 22:26:04 atd1 vmunix: PCI Xaction Start Address = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: PCI Command: Interrupt Acknowledge
Jul 1 22:26:04 atd1 vmunix: CPU 1 is prevented from being rebooted.
Jul 1 22:26:04 atd1 vmunix: The system must be reset or power cycled to clear this state.
Jul 1 22:26:04 atd1 vmunix: panic (cpu 1): Processor Machine Check
Jul 1 22:26:04 atd1 vmunix: syncing disks...
After browsing similar threads,the problem is most likely with CPU/RAM.
can anyone pinpoint what is the actual problem?
Wheather the above mentioned hardware need to be replaced???
Attaching herewith crash-data ,binary.errorlog.zip,
Waiting for prompt reply.
rgds
azim
I have compaq alpha server ES40 with tru64 v5.1b o/s in a cluster mode,Firmware revision: 6.3-2
My server got rebooted with the below mentioned error.
Jul 1 22:26:04 atd1 vmunix: Machine Check Processor Fatal Abort
Jul 1 22:26:04 atd1 vmunix: Machine check code = 0x1000000a0
Jul 1 22:26:04 atd1 vmunix: Ibox Status = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Dcache Status = 0000000000000008
Jul 1 22:26:04 atd1 vmunix: Cbox Address = 0000000101dbcd40
Jul 1 22:26:04 atd1 vmunix: Fill Syndrome 1 = 00000000000000d3
Jul 1 22:26:04 atd1 vmunix: Fill Syndrome 0 = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Cbox Status = 000000000000000b
Jul 1 22:26:04 atd1 vmunix: EV6 captured status of Bcache mode = 000000000000000d
Jul 1 22:26:04 atd1 vmunix: EV6 Exception Address = 0000000122af84d0
Jul 1 22:26:04 atd1 vmunix: EV6 Interrupt Enablement and Current Processor mode = 0000007ee0000008
Jul 1 22:26:04 atd1 vmunix: EV6 Interrupt Summary Register = 0000000080000000
Jul 1 22:26:04 atd1 vmunix: EV6 TBmiss or Fault status = 0000000000000290
Jul 1 22:26:04 atd1 vmunix: EV6 PAL Base Address = 0000000000018000
Jul 1 22:26:04 atd1 vmunix: EV6 Ibox control = fffffe0006304396
Jul 1 22:26:04 atd1 vmunix: EV6 Ibox Process_context = 0000080000000004
Jul 1 22:26:04 atd1 vmunix: O/S Summary flag = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Cchip Base Address (phys) = 00000f01a0000000
Jul 1 22:26:04 atd1 vmunix: Cchip Device Raw Interrupt Request = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: DRIR Register Decode:
Jul 1 22:26:04 atd1 vmunix: PCI Device Interrupt Mask = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Cchip Miscellaneous Register = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Misc Register Decode:
Jul 1 22:26:04 atd1 vmunix: Cchip Revision: 00
Jul 1 22:26:04 atd1 vmunix: ID of CPU performing read: 00
Jul 1 22:26:04 atd1 vmunix: Pchip 0 Base Address (phys) = 00000f0180000000
Jul 1 22:26:04 atd1 vmunix: Pchip 0 Error Register = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Pchip Error Register Decode:
Jul 1 22:26:04 atd1 vmunix: PCI Xaction Start Address = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: PCI Command: Interrupt Acknowledge
Jul 1 22:26:04 atd1 vmunix: Pchip 1 Base Address (phys) = 00000f0380000000
Jul 1 22:26:04 atd1 vmunix: Pchip 1 Error Register = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: Pchip Error Register Decode:
Jul 1 22:26:04 atd1 vmunix: PCI Xaction Start Address = 0000000000000000
Jul 1 22:26:04 atd1 vmunix: PCI Command: Interrupt Acknowledge
Jul 1 22:26:04 atd1 vmunix: CPU 1 is prevented from being rebooted.
Jul 1 22:26:04 atd1 vmunix: The system must be reset or power cycled to clear this state.
Jul 1 22:26:04 atd1 vmunix: panic (cpu 1): Processor Machine Check
Jul 1 22:26:04 atd1 vmunix: syncing disks...
After browsing similar threads,the problem is most likely with CPU/RAM.
can anyone pinpoint what is the actual problem?
Wheather the above mentioned hardware need to be replaced???
Attaching herewith crash-data ,binary.errorlog.zip,
Waiting for prompt reply.
rgds
azim
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2005 01:15 AM
тАО07-04-2005 01:15 AM
Re: Alpha ES40 rebooted with "Machine check processor fatal abort" error
You should check:
1-
Your firmware revision is tha latest.
You have tha latest patch kit installed.
2-
Check power supply/environment errors (>>> show power)
Replace memory
Swap/Replace cpu
3-
Oracle was the process running at the time of the crash, check oracle log files.
1-
Your firmware revision is tha latest.
You have tha latest patch kit installed.
2-
Check power supply/environment errors (>>> show power)
Replace memory
Swap/Replace cpu
3-
Oracle was the process running at the time of the crash, check oracle log files.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2005 02:55 AM
тАО07-04-2005 02:55 AM
Re: Alpha ES40 rebooted with "Machine check processor fatal abort" error
Azim,
this is clearly a case to open a call with HP.
greetings,
Michael
this is clearly a case to open a call with HP.
greetings,
Michael
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