HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: ES40 crash
Operating System - Tru64 Unix
1827697
Members
3048
Online
109967
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
Forums
Discussions
Discussions
Discussions
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
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
10-25-2007 01:01 AM
10-25-2007 01:01 AM
ES40 crash
I have a ES40 ,It crashed and rebooted on Oct 17 . But I don't know what is the real cause that ES40 crashed. the log as below ,hope someone could tell me the where the cause is.
Sep 28 13:27:43 smf3 vmunix: chk_bf_quota: group quota underflow for group 7 on fileset /
Oct 16 18:44:08 smf3 vmunix: prom_getenv:Invalid ev type:0
Oct 17 08:45:28 smf3 vmunix: Machine Check SYSTEM Fatal Abort
Oct 17 08:45:28 smf3 vmunix: Machine Check Processor Fatal Abort
Oct 17 08:45:28 smf3 vmunix: Machine check code = 0x100000202
Oct 17 08:45:28 smf3 vmunix: Ibox Status = 0000000000000000
Oct 17 08:45:28 smf3 vmunix: Dcache Status = 0000000000000000
Oct 17 08:45:28 smf3 vmunix: Cbox Address = 0000000000000000
Oct 17 08:45:28 smf3 vmunix: Fill Syndrome 1 = 0000000000000000
Oct 17 08:45:28 smf3 vmunix: Fill Syndrome 0 = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: Cbox Status = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: EV6 captured status of Bcache mode = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: EV6 Exception Address = fffffc00002bf204
Oct 17 08:45:29 smf3 vmunix: EV6 Interrupt Enablement and Current Processor mode = 0000007ee0000000
Oct 17 08:45:29 smf3 vmunix: EV6 Interrupt Summary Register = 0000000200000000
Oct 17 08:45:29 smf3 vmunix: EV6 TBmiss or Fault status = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: EV6 PAL Base Address = 0000000000018000
Oct 17 08:45:29 smf3 vmunix: EV6 Ibox control = fffffffc1a304096
Oct 17 08:45:29 smf3 vmunix: EV6 Ibox Process_context = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: O/S Summary flag = 0000000000000004
Oct 17 08:45:29 smf3 vmunix: Cchip Base Address (phys) = 00000801a0000000
Oct 17 08:45:30 smf3 vmunix: Cchip Device Raw Interrupt Request = 8000000000000000
Oct 17 08:45:30 smf3 vmunix: DRIR Register Decode:
Oct 17 08:45:30 smf3 vmunix: Bit 63: Internal Cchip Error
Oct 17 08:45:30 smf3 vmunix: PCI Device Interrupt Mask = 0000000000000000
Oct 17 08:45:30 smf3 vmunix: Cchip Miscellaneous Register = 0000000830000000
Oct 17 08:45:30 smf3 vmunix: Misc Register Decode:
Oct 17 08:45:30 smf3 vmunix: Bit 28: NXM
Oct 17 08:45:30 smf3 vmunix: Bit 29: NXM Source (Bit<29>)
Oct 17 08:45:30 smf3 vmunix: Bit 35: CChip Rev (Bit<35>)
Oct 17 08:45:30 smf3 vmunix: Cchip Revision: 08
Oct 17 08:45:30 smf3 vmunix: ID of CPU performing read: 00
Oct 17 08:45:31 smf3 vmunix: Source of NXM access: CPU 1
Oct 17 08:45:31 smf3 vmunix: Pchip 0 Base Address (phys) = 0000080180000000
Oct 17 08:45:31 smf3 vmunix: Pchip 0 Error Register = 0000000000000000
Oct 17 08:45:31 smf3 vmunix: Pchip Error Register Decode:
Oct 17 08:45:31 smf3 vmunix: PCI Xaction Start Address = 0000000000000000
Oct 17 08:45:31 smf3 vmunix: PCI Command: Interrupt Acknowledge
Oct 17 08:45:31 smf3 vmunix: Pchip 1 Base Address (phys) = 0000080380000000
Oct 17 08:45:31 smf3 vmunix: Pchip 1 Error Register = 0000000000000000
Oct 17 08:45:31 smf3 vmunix: Pchip Error Register Decode:
Oct 17 08:45:31 smf3 vmunix: PCI Xaction Start Address = 0000000000000000
Oct 17 08:45:32 smf3 vmunix: PCI Command: Interrupt Acknowledge
Oct 17 08:45:32 smf3 vmunix: panic (cpu 0): System Uncorrectable Machine Check
Oct 17 08:45:32 smf3 vmunix: syncing disks...
Oct 17 08:45:32 smf3 vmunix: LSM attempting to dump to SCSI device unit number rz0
Oct 17 08:45:32 smf3 vmunix:
Oct 17 08:45:32 smf3 vmunix: device string for dump = SCSI 1 4 0 0 0 0 0.
Oct 17 08:45:32 smf3 vmunix: DUMP.prom: dev SCSI 1 4 0 0 0 0 0, block 2097152
Oct 17 08:45:32 smf3 vmunix: device string for dump = SCSI 1 4 0 0 0 0 0.
Oct 17 08:45:32 smf3 vmunix: DUMP.prom: dev SCSI 1 4 0 0 0 0 0, block 2097152
Oct 17 08:45:32 smf3 vmunix: Alpha boot: available memory from 0x4e1a000 to 0xffff4000
Oct 17 08:45:32 smf3 vmunix: Digital UNIX V4.0F (Rev. 1229); Fri Jul 2 03:29:59 CST 2004
Oct 17 08:45:33 smf3 vmunix: physical memory = 4096.00 megabytes.
Oct 17 08:45:33 smf3 vmunix: available memory = 4017.19 megabytes.
Oct 17 08:45:33 smf3 vmunix: using 5239 buffers containing 40.92 megabytes of memory
Oct 17 08:45:33 smf3 vmunix: Master cpu at slot 0.
Oct 17 08:45:33 smf3 vmunix: Firmware revision: 6.6-19
Oct 17 08:45:33 smf3 vmunix: PALcode: Digital UNIX version 1.92-105
Oct 17 08:45:33 smf3 vmunix: AlphaServer ES40
Thanks
Ramber
Sep 28 13:27:43 smf3 vmunix: chk_bf_quota: group quota underflow for group 7 on fileset /
Oct 16 18:44:08 smf3 vmunix: prom_getenv:Invalid ev type:0
Oct 17 08:45:28 smf3 vmunix: Machine Check SYSTEM Fatal Abort
Oct 17 08:45:28 smf3 vmunix: Machine Check Processor Fatal Abort
Oct 17 08:45:28 smf3 vmunix: Machine check code = 0x100000202
Oct 17 08:45:28 smf3 vmunix: Ibox Status = 0000000000000000
Oct 17 08:45:28 smf3 vmunix: Dcache Status = 0000000000000000
Oct 17 08:45:28 smf3 vmunix: Cbox Address = 0000000000000000
Oct 17 08:45:28 smf3 vmunix: Fill Syndrome 1 = 0000000000000000
Oct 17 08:45:28 smf3 vmunix: Fill Syndrome 0 = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: Cbox Status = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: EV6 captured status of Bcache mode = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: EV6 Exception Address = fffffc00002bf204
Oct 17 08:45:29 smf3 vmunix: EV6 Interrupt Enablement and Current Processor mode = 0000007ee0000000
Oct 17 08:45:29 smf3 vmunix: EV6 Interrupt Summary Register = 0000000200000000
Oct 17 08:45:29 smf3 vmunix: EV6 TBmiss or Fault status = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: EV6 PAL Base Address = 0000000000018000
Oct 17 08:45:29 smf3 vmunix: EV6 Ibox control = fffffffc1a304096
Oct 17 08:45:29 smf3 vmunix: EV6 Ibox Process_context = 0000000000000000
Oct 17 08:45:29 smf3 vmunix: O/S Summary flag = 0000000000000004
Oct 17 08:45:29 smf3 vmunix: Cchip Base Address (phys) = 00000801a0000000
Oct 17 08:45:30 smf3 vmunix: Cchip Device Raw Interrupt Request = 8000000000000000
Oct 17 08:45:30 smf3 vmunix: DRIR Register Decode:
Oct 17 08:45:30 smf3 vmunix: Bit 63: Internal Cchip Error
Oct 17 08:45:30 smf3 vmunix: PCI Device Interrupt Mask = 0000000000000000
Oct 17 08:45:30 smf3 vmunix: Cchip Miscellaneous Register = 0000000830000000
Oct 17 08:45:30 smf3 vmunix: Misc Register Decode:
Oct 17 08:45:30 smf3 vmunix: Bit 28: NXM
Oct 17 08:45:30 smf3 vmunix: Bit 29: NXM Source (Bit<29>)
Oct 17 08:45:30 smf3 vmunix: Bit 35: CChip Rev (Bit<35>)
Oct 17 08:45:30 smf3 vmunix: Cchip Revision: 08
Oct 17 08:45:30 smf3 vmunix: ID of CPU performing read: 00
Oct 17 08:45:31 smf3 vmunix: Source of NXM access: CPU 1
Oct 17 08:45:31 smf3 vmunix: Pchip 0 Base Address (phys) = 0000080180000000
Oct 17 08:45:31 smf3 vmunix: Pchip 0 Error Register = 0000000000000000
Oct 17 08:45:31 smf3 vmunix: Pchip Error Register Decode:
Oct 17 08:45:31 smf3 vmunix: PCI Xaction Start Address = 0000000000000000
Oct 17 08:45:31 smf3 vmunix: PCI Command: Interrupt Acknowledge
Oct 17 08:45:31 smf3 vmunix: Pchip 1 Base Address (phys) = 0000080380000000
Oct 17 08:45:31 smf3 vmunix: Pchip 1 Error Register = 0000000000000000
Oct 17 08:45:31 smf3 vmunix: Pchip Error Register Decode:
Oct 17 08:45:31 smf3 vmunix: PCI Xaction Start Address = 0000000000000000
Oct 17 08:45:32 smf3 vmunix: PCI Command: Interrupt Acknowledge
Oct 17 08:45:32 smf3 vmunix: panic (cpu 0): System Uncorrectable Machine Check
Oct 17 08:45:32 smf3 vmunix: syncing disks...
Oct 17 08:45:32 smf3 vmunix: LSM attempting to dump to SCSI device unit number rz0
Oct 17 08:45:32 smf3 vmunix:
Oct 17 08:45:32 smf3 vmunix: device string for dump = SCSI 1 4 0 0 0 0 0.
Oct 17 08:45:32 smf3 vmunix: DUMP.prom: dev SCSI 1 4 0 0 0 0 0, block 2097152
Oct 17 08:45:32 smf3 vmunix: device string for dump = SCSI 1 4 0 0 0 0 0.
Oct 17 08:45:32 smf3 vmunix: DUMP.prom: dev SCSI 1 4 0 0 0 0 0, block 2097152
Oct 17 08:45:32 smf3 vmunix: Alpha boot: available memory from 0x4e1a000 to 0xffff4000
Oct 17 08:45:32 smf3 vmunix: Digital UNIX V4.0F (Rev. 1229); Fri Jul 2 03:29:59 CST 2004
Oct 17 08:45:33 smf3 vmunix: physical memory = 4096.00 megabytes.
Oct 17 08:45:33 smf3 vmunix: available memory = 4017.19 megabytes.
Oct 17 08:45:33 smf3 vmunix: using 5239 buffers containing 40.92 megabytes of memory
Oct 17 08:45:33 smf3 vmunix: Master cpu at slot 0.
Oct 17 08:45:33 smf3 vmunix: Firmware revision: 6.6-19
Oct 17 08:45:33 smf3 vmunix: PALcode: Digital UNIX version 1.92-105
Oct 17 08:45:33 smf3 vmunix: AlphaServer ES40
Thanks
Ramber
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2007 02:14 AM
10-25-2007 02:14 AM
Re: ES40 crash
Not easy, but you can get a lot more valuable information with WEBES and CCAT:
http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1162755
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1115051
http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1162755
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1115051
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
10-25-2007 01:41 PM
10-25-2007 01:41 PM
Re: ES40 crash
Hey,
if open a h/w case they would analyze binary.errlog file and will tell you exact reason and would do sm replacememt if needed.
As Ivan said frm those two links you can download the tools and analyze urself also.
BR,
Kapil
if open a h/w case they would analyze binary.errlog file and will tell you exact reason and would do sm replacememt if needed.
As Ivan said frm those two links you can download the tools and analyze urself also.
BR,
Kapil
I am in this small bowl, I wane see the real world......
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP