- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Problem with rx5670, Crash
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
тАО06-01-2010 10:23 PM
тАО06-01-2010 10:23 PM
Problem with rx5670, Crash
Jun 1 05:03:41 hp-uxserver01 vmunix: Boot device's HP-UX HW path is: 0/0/2/0.2.0
Jun 1 05:03:41 hp-uxserver01 vmunix:
Jun 1 05:03:41 hp-uxserver01 vmunix: System Console is on the Built-In Serial Interface
Jun 1 05:03:41 hp-uxserver01 vmunix: igelan0: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 0/1/1/0/4/0
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:REVISION:0002
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:SEVERITY:1
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:Processor Error Device Info decode begins.
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:VALIDATION_BITS = 0x000000000110102f
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:PSP = 0xa8000000fff21330
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:The error was isolated but not contained.
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]: cache check. info:N/A
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]: req:N/A res:N/A
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]: tgt:N/A ip:N/A
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]: bus check. info:0x0080000000000060
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]: cache check. info:N/A
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]: uarch check. info:0x0080000000003001
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:PSI_STATIC_STRUCT.VALID_FIELD_BITS=0x000000000000003f
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:Processor Error Device Info decode ends.
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]: req:N/A res:N/A
Jun 1 05:03:44 hp-uxserver01 above message repeats 3 times
Jun 1 05:03:41 hp-uxserver01 vmunix:
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]: tgt:N/A ip:N/A
Jun 1 05:03:44 hp-uxserver01 above message repeats 3 times
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:PCI I/O Component Error
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:Hardware Path = 0/3/1/0
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]:handler = OS_MCA, sub_type = Generic
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]:00 00 00 00 00 00 20 02 e0 00 00 00 00 22 c7 00
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]:00 03 00 03 01 00 a0 00 e0 00 00 01 1d c0 d2 68
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]:00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 08
Jun 1 05:03:41 hp-uxserver01 vmunix:
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:PCI Mercury Bus Error
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:Bus ID = 0x60
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:Error Type = 0x1
Jun 1 05:03:41 hp-uxserver01 vmunix:
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:Error Status val = 0xe1600
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:Error Status type = ERR_PARITY Bus parity error (must also set the A, C, or D Bits).
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]:handler = OS_MCA, sub_type = Generic
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]:00 00 00 00 00 00 20 04 e0 00 00 00 00 22 c6 c0
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]:00 60 00 01 01 00 a0 00 00 00 00 00 00 60 08 00
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA/CMC[0]:00 00 00 00 fe d2 60 00 00 00 00 40 76 83 a6 b0
Jun 1 05:03:41 hp-uxserver01 vmunix:
Jun 1 05:03:41 hp-uxserver01 vmunix: Logical volume 64, 0x3 configured as ROOT
Jun 1 05:03:41 hp-uxserver01 vmunix: Logical volume 64, 0x2 configured as SWAP
Jun 1 05:03:41 hp-uxserver01 vmunix: Logical volume 64, 0x2 configured as DUMP
Jun 1 05:03:41 hp-uxserver01 vmunix: Swap device table: (start & size given in 512-byte blocks)
Jun 1 05:03:41 hp-uxserver01 vmunix: entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Jun 1 05:03:41 hp-uxserver01 vmunix: Dump device table: (start & size given in 1-Kbyte blocks)
Jun 1 05:03:41 hp-uxserver01 vmunix: entry 0000000000000000 - major is 31, minor is 0x2000; start = 826228, size = 4194300
Jun 1 05:03:41 hp-uxserver01 vmunix: Starting the STREAMS daemons-phase 1
Jun 1 05:03:41 hp-uxserver01 vmunix: Create STCP device files
Jun 1 05:03:41 hp-uxserver01 vmunix: Starting the STREAMS daemons-phase 2
Jun 1 05:03:41 hp-uxserver01 vmunix: $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
Jun 1 05:03:41 hp-uxserver01 vmunix: Memory Information:
Jun 1 05:03:41 hp-uxserver01 vmunix: physical page size = 4096 bytes, logical page size = 4096 bytes
Jun 1 05:03:41 hp-uxserver01 vmunix: Physical: 8381808 Kbytes, lockable: 6125152 Kbytes, available: 7180052 Kbytes
Jun 1 05:03:41 hp-uxserver01 vmunix:
Jun 1 05:03:41 hp-uxserver01 vmunix: NOTICE: vxvm:vxdmp: added disk array OTHER_DISKS, datype = OTHER_DISKS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2010 10:39 PM
тАО06-01-2010 10:39 PM
Re: Problem with rx5670, Crash
Reboot after panic: MCA, IIP:0xe00000000073a760 IFA:0x6000000000406320
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2010 10:44 PM
тАО06-01-2010 10:44 PM
Re: Problem with rx5670, Crash
check
/var/adm/crash
/var/tombstones
collect information from MP ( event log ) =>
filter majority => 3
check /etc/shutdownlog
check /var/adm/syslog/OLDsyslog.log (syslog.log)
....
of course if you have valid HP contract, contact your ASM, and open a HW call, the will analyze the crashdump and toombstones if are presented.
reference could be also this page :
http://www.hpux.ws/?p=83
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2010 10:51 PM
тАО06-01-2010 10:51 PM
Re: Problem with rx5670, Crash
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:REVISION:0002
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:SEVERITY:1
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:Processor Error Device Info decode begins.
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:VALIDATION_BITS = 0x000000000110102f
Jun 1 05:03:41 hp-uxserver01 vmunix: MCA[0]:PSP = 0xa8000000fff21330
it seems some issue on server LAN/SCSI I/O PCI board on path 0/1/1/0/4/0
Remove this card & try for reboot.
GUdlcuk
Prasanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2010 10:52 PM
тАО06-01-2010 10:52 PM
Re: Problem with rx5670, Crash
/var/tomstones are present
shutdownlog at previous message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2010 10:57 PM
тАО06-01-2010 10:57 PM
Re: Problem with rx5670, Crash
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2010 11:02 PM
тАО06-01-2010 11:02 PM
Re: Problem with rx5670, Crash
i will werite it again, if you have valid HP contract, would open a HW call, and the HP will analyze your crash dump + mcafile.00x
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2010 11:07 PM
тАО06-01-2010 11:07 PM