- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: V2600 hung
HPE 9000 and HPE e3000 Servers
1753974
Members
7117
Online
108811
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
тАО06-27-2005 06:50 AM
тАО06-27-2005 06:50 AM
V2600 hung
After running cpu_hang I get the following info.
================================================================================
spac_interrogator is running on NODE n0 SPAC p1r
r_error_cause0 = 0x0
r_error_cause1 = 0x784000000
r_error_cause_num = 0x0
r_error_config0_reg = 0x7fffff55fdfffff7
r_error_config1_reg = 0x3ff57dffea
r_error_info_reg = 0x18004184
----------------------------------------------------------------------------
Hard Error Group bit = 0x0 The SPAC's hard error pin WAS NOT driven
by another chip.
error_info phase = 0x2
error_info S = 0x0
----------------------------------------------------------------------------
error_cause0 register indicates 0 errors.
----------------------------------------------------------------------------
error_cause1 register indicates 5 error(s):
bit severity error name
--- -------- ----------
0 hard Runway 0 Address Cycle Parity Error
1 hard Runway 0 Data Cycle Parity Error
2 hard Runway 0 Control Parity Error
3 hard Runway 0 Valid Error
8 hard Runway 0 Bad TTYPE Error
*** Running extractor rw_acycle_perror n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Address Cycle Parity Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Address Cycle Parity Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[0] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected a parity error on the runway data bus during an
address cycle, i.e. addr_valid=1, data_valid=0.
=========================================================================
*** Running extractor rw_dcycle_perror n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Data Cycle Parity Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Data Cycle Parity Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[1] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected a parity error on the runway data bus during a
data cycle, i.e. addr_valid=0, data_valid=1.
=========================================================================
*** Running extractor r_rw_cntl_perror n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Control Parity Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Control Parity Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[2] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected a parity error on the runway control lines,
i.e. mid and tid.
=========================================================================
*** Running extractor r_rw_valid_error n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Valid Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Valid Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[3] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c r_rw0_a_val_a (cpu a addr_valid) r_rw0_d_val_a (cpu a data_valid)
-------------------------------------------------------------------------
Error Description:
The SPAC detected that both addr_valid and data_valid were asserted
on the same runway cycle.
=========================================================================
*** Running extractor rw_bad_ttype_error n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Bad Ttype Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Bad Ttype Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[8] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected an invalid runway ttype or a coherent read using
a tid greater than 0x9.
=========================================================================
*** questioning suspect: spac[4]
***
spac_error_cause0[4] = | 20 0|
*** questioning suspect: spac[5]
***
spac_error_cause0[5] = | 20 0|
############################## End ##################################
I am not sure if I have a cpu, memory, or bus error. What is a bad Ttype error? Can anyone decifer this?
================================================================================
spac_interrogator is running on NODE n0 SPAC p1r
r_error_cause0 = 0x0
r_error_cause1 = 0x784000000
r_error_cause_num = 0x0
r_error_config0_reg = 0x7fffff55fdfffff7
r_error_config1_reg = 0x3ff57dffea
r_error_info_reg = 0x18004184
----------------------------------------------------------------------------
Hard Error Group bit = 0x0 The SPAC's hard error pin WAS NOT driven
by another chip.
error_info phase = 0x2
error_info S = 0x0
----------------------------------------------------------------------------
error_cause0 register indicates 0 errors.
----------------------------------------------------------------------------
error_cause1 register indicates 5 error(s):
bit severity error name
--- -------- ----------
0 hard Runway 0 Address Cycle Parity Error
1 hard Runway 0 Data Cycle Parity Error
2 hard Runway 0 Control Parity Error
3 hard Runway 0 Valid Error
8 hard Runway 0 Bad TTYPE Error
*** Running extractor rw_acycle_perror n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Address Cycle Parity Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Address Cycle Parity Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[0] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected a parity error on the runway data bus during an
address cycle, i.e. addr_valid=1, data_valid=0.
=========================================================================
*** Running extractor rw_dcycle_perror n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Data Cycle Parity Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Data Cycle Parity Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[1] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected a parity error on the runway data bus during a
data cycle, i.e. addr_valid=0, data_valid=1.
=========================================================================
*** Running extractor r_rw_cntl_perror n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Control Parity Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Control Parity Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[2] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected a parity error on the runway control lines,
i.e. mid and tid.
=========================================================================
*** Running extractor r_rw_valid_error n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Valid Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Valid Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[3] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c r_rw0_a_val_a (cpu a addr_valid) r_rw0_d_val_a (cpu a data_valid)
-------------------------------------------------------------------------
Error Description:
The SPAC detected that both addr_valid and data_valid were asserted
on the same runway cycle.
=========================================================================
*** Running extractor rw_bad_ttype_error n0:1:internal:p1r 0 0x0 0x784000000 16#0 16#18004184:
Event Code = 0x854e0008
=========================================================================
Runway Bad Ttype Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Bad Ttype Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[8] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected an invalid runway ttype or a coherent read using
a tid greater than 0x9.
=========================================================================
*** questioning suspect: spac[4]
***
spac_error_cause0[4] = | 20 0|
*** questioning suspect: spac[5]
***
spac_error_cause0[5] = | 20 0|
############################## End ##################################
I am not sure if I have a cpu, memory, or bus error. What is a bad Ttype error? Can anyone decifer this?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2005 07:24 AM
тАО06-27-2005 07:24 AM
Re: V2600 hung
Looks like I pasted the wrong date. Here is the current log. It looks like a bad backplane maybe. Anyone know what an invalid runway Ttype means?
+++>
error:0x854e0008
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
=========================================================================
Runway Control Parity Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Control Parity Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[2] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected a parity error on the runway control lines,
i.e. mid and tid.
=========================================================================
****
+++>
info:0x456a2000
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
****
+++>
error:0x854e0000
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
Node Device Part Number Board Serial Number EDC Scan Artwork Rev
---------------------------------------------------------------------------
0 scub A5074-60003 2026178 3916 00 c
0 mib A5074-60002 2020061 3901 00 a
0 pb0r A5825-60001 A56302015302 4003 00 c
0 pb1r A5825-60001 A56302015296 4003 00 c
0 pb1l A5825-60001 A56302001905 4003 00 c
0 pb2l A5825-60001 A56302015301 4003 00 c
0 pb2r A5825-60001 A56302009841 4003 00 c
0 pb3l A5825-60001 A56302009833 4003 00 c
0 pb4l A5825-60001 A56301998291 4003 00 c
0 pb4r A5825-60001 A56302015287 4003 00 c
0 pb5r A5825-60001 A56302009868 4003 00 c
0 pb5l A5825-60001 A56301998339 4003 00 c
0 pb6r A5826-60001 A56302057113 4003 00 c
0 pb7l A5825-60001 A56302015256 4003 00 c
0 mb0l A5517-60001 A56301500436 3914 00 a
0 mb1l A5078-60003 A56E02805226 3941 01 a
0 mb2r A5078-60003 A56E02732689 3941 01 a
0 mb3r A5078-60003 A56E02805205 3941 01 a
0 mb4l A5078-60003 A56E02802215 3941 01 a
0 mb5l A5078-60003 A56E02745477 3941 01 a
0 mb6r A5078-60003 A56E02805258 3941 01 a
0 mb7r A5078-60003 A56E02802287 3941 01 a
0 iolf A5080-60001 1410059 3950 00 a
0 iolr A5080-60001 1410167 3950 00 a
0 iorr A5080-60001 1410180 3950 00 a
0 iorf A5080-60001 1410269 3950 00 a
****
+++>
error:0x854e0001
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
Node IP address Clocks LEDS @C U SHPT Supply1 Supply2 Supply3 Supply4
------------------- ------ --------- ---- ------ ------- ------- ------- -------
0 15.99.111.116 Normal A 0x68 22 1 0000 Nominal Nominal Nominal Nominal
****
+++>
info:0x456a2000
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
================================================================================
spac_interrogator is running on NODE n0 SPAC p1r
r_error_cause0 = 0x0
r_error_cause1 = 0x784000000
r_error_cause_num = 0x0
r_error_config0_reg = 0x7fffff55fdfffff7
r_error_config1_reg = 0x3ff57dffea
r_error_info_reg = 0x18004184
----------------------------------------------------------------------------
Hard Error Group bit = 0x0 The SPAC's hard error pin WAS NOT driven
by another chip.
error_info phase = 0x2
error_info S = 0x0
----------------------------------------------------------------------------
error_cause0 register indicates 0 errors.
----------------------------------------------------------------------------
error_cause1 register indicates 5 error(s):
bit severity error name
--- -------- ----------
0 hard Runway 0 Address Cycle Parity Error
1 hard Runway 0 Data Cycle Parity Error
2 hard Runway 0 Control Parity Error
3 hard Runway 0 Valid Error
8 hard Runway 0 Bad TTYPE Error
****
+++>
error:0x854e0008
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
=========================================================================
Runway Valid Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Valid Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[3] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c r_rw0_a_val_a (cpu a addr_valid) r_rw0_d_val_a (cpu a data_valid)
-------------------------------------------------------------------------
Error Description:
The SPAC detected that both addr_valid and data_valid were asserted
on the same runway cycle.
=========================================================================
****
+++>
info:0x456a2000
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
****
+++>
error:0x854e0000
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
Node Device Part Number Board Serial Number EDC Scan Artwork Rev
---------------------------------------------------------------------------
0 scub A5074-60003 2026178 3916 00 c
0 mib A5074-60002 2020061 3901 00 a
0 pb0r A5825-60001 A56302015302 4003 00 c
0 pb1r A5825-60001 A56302015296 4003 00 c
0 pb1l A5825-60001 A56302001905 4003 00 c
0 pb2l A5825-60001 A56302015301 4003 00 c
0 pb2r A5825-60001 A56302009841 4003 00 c
0 pb3l A5825-60001 A56302009833 4003 00 c
0 pb4l A5825-60001 A56301998291 4003 00 c
0 pb4r A5825-60001 A56302015287 4003 00 c
0 pb5r A5825-60001 A56302009868 4003 00 c
0 pb5l A5825-60001 A56301998339 4003 00 c
0 pb6r A5826-60001 A56302057113 4003 00 c
0 pb7l A5825-60001 A56302015256 4003 00 c
0 mb0l A5517-60001 A56301500436 3914 00 a
0 mb1l A5078-60003 A56E02805226 3941 01 a
0 mb2r A5078-60003 A56E02732689 3941 01 a
0 mb3r A5078-60003 A56E02805205 3941 01 a
0 mb4l A5078-60003 A56E02802215 3941 01 a
0 mb5l A5078-60003 A56E02745477 3941 01 a
0 mb6r A5078-60003 A56E02805258 3941 01 a
0 mb7r A5078-60003 A56E02802287 3941 01 a
0 iolf A5080-60001 1410059 3950 00 a
0 iolr A5080-60001 1410167 3950 00 a
0 iorr A5080-60001 1410180 3950 00 a
0 iorf A5080-60001 1410269 3950 00 a
****
+++>
error:0x854e0001
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
Node IP address Clocks LEDS @C U SHPT Supply1 Supply2 Supply3 Supply4
------------------- ------ --------- ---- ------ ------- ------- ------- -------
0 15.99.111.116 Normal A 0x68 22 1 0000 Nominal Nominal Nominal Nominal
****
+++>
info:0x456a2000
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
================================================================================
spac_interrogator is running on NODE n0 SPAC p1r
r_error_cause0 = 0x0
r_error_cause1 = 0x784000000
r_error_cause_num = 0x0
r_error_config0_reg = 0x7fffff55fdfffff7
r_error_config1_reg = 0x3ff57dffea
r_error_info_reg = 0x18004184
----------------------------------------------------------------------------
Hard Error Group bit = 0x0 The SPAC's hard error pin WAS NOT driven
by another chip.
error_info phase = 0x2
error_info S = 0x0
----------------------------------------------------------------------------
error_cause0 register indicates 0 errors.
----------------------------------------------------------------------------
error_cause1 register indicates 5 error(s):
bit severity error name
--- -------- ----------
0 hard Runway 0 Address Cycle Parity Error
1 hard Runway 0 Data Cycle Parity Error
2 hard Runway 0 Control Parity Error
3 hard Runway 0 Valid Error
8 hard Runway 0 Bad TTYPE Error
****
+++>
error:0x854e0008
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
=========================================================================
Runway Bad Ttype Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Bad Ttype Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[8] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected an invalid runway ttype or a coherent read using
a tid greater than 0x9.
=========================================================================
****
+++>
info:0x456a2000
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
=========================================================================
Runway Control Parity Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Control Parity Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[2] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected a parity error on the runway control lines,
i.e. mid and tid.
=========================================================================
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
Node Device Part Number Board Serial Number EDC Scan Artwork Rev
---------------------------------------------------------------------------
0 scub A5074-60003 2026178 3916 00 c
0 mib A5074-60002 2020061 3901 00 a
0 pb0r A5825-60001 A56302015302 4003 00 c
0 pb1r A5825-60001 A56302015296 4003 00 c
0 pb1l A5825-60001 A56302001905 4003 00 c
0 pb2l A5825-60001 A56302015301 4003 00 c
0 pb2r A5825-60001 A56302009841 4003 00 c
0 pb3l A5825-60001 A56302009833 4003 00 c
0 pb4l A5825-60001 A56301998291 4003 00 c
0 pb4r A5825-60001 A56302015287 4003 00 c
0 pb5r A5825-60001 A56302009868 4003 00 c
0 pb5l A5825-60001 A56301998339 4003 00 c
0 pb6r A5826-60001 A56302057113 4003 00 c
0 pb7l A5825-60001 A56302015256 4003 00 c
0 mb0l A5517-60001 A56301500436 3914 00 a
0 mb1l A5078-60003 A56E02805226 3941 01 a
0 mb2r A5078-60003 A56E02732689 3941 01 a
0 mb3r A5078-60003 A56E02805205 3941 01 a
0 mb4l A5078-60003 A56E02802215 3941 01 a
0 mb5l A5078-60003 A56E02745477 3941 01 a
0 mb6r A5078-60003 A56E02805258 3941 01 a
0 mb7r A5078-60003 A56E02802287 3941 01 a
0 iolf A5080-60001 1410059 3950 00 a
0 iolr A5080-60001 1410167 3950 00 a
0 iorr A5080-60001 1410180 3950 00 a
0 iorf A5080-60001 1410269 3950 00 a
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
Node IP address Clocks LEDS @C U SHPT Supply1 Supply2 Supply3 Supply4
------------------- ------ --------- ---- ------ ------- ------- ------- -------
0 15.99.111.116 Normal A 0x68 22 1 0000 Nominal Nominal Nominal Nominal
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
================================================================================
spac_interrogator is running on NODE n0 SPAC p1r
r_error_cause0 = 0x0
r_error_cause1 = 0x784000000
r_error_cause_num = 0x0
r_error_config0_reg = 0x7fffff55fdfffff7
r_error_config1_reg = 0x3ff57dffea
r_error_info_reg = 0x18004184
----------------------------------------------------------------------------
Hard Error Group bit = 0x0 The SPAC's hard error pin WAS NOT driven
by another chip.
error_info phase = 0x2
error_info S = 0x0
----------------------------------------------------------------------------
error_cause0 register indicates 0 errors.
----------------------------------------------------------------------------
error_cause1 register indicates 5 error(s):
bit severity error name
--- -------- ----------
0 hard Runway 0 Address Cycle Parity Error
1 hard Runway 0 Data Cycle Parity Error
2 hard Runway 0 Control Parity Error
3 hard Runway 0 Valid Error
8 hard Runway 0 Bad TTYPE Error
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
=========================================================================
Runway Valid Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Valid Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[3] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c r_rw0_a_val_a (cpu a addr_valid) r_rw0_d_val_a (cpu a data_valid)
-------------------------------------------------------------------------
Error Description:
The SPAC detected that both addr_valid and data_valid were asserted
on the same runway cycle.
=========================================================================
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
Node Device Part Number Board Serial Number EDC Scan Artwork Rev
---------------------------------------------------------------------------
0 scub A5074-60003 2026178 3916 00 c
0 mib A5074-60002 2020061 3901 00 a
0 pb0r A5825-60001 A56302015302 4003 00 c
0 pb1r A5825-60001 A56302015296 4003 00 c
0 pb1l A5825-60001 A56302001905 4003 00 c
0 pb2l A5825-60001 A56302015301 4003 00 c
0 pb2r A5825-60001 A56302009841 4003 00 c
0 pb3l A5825-60001 A56302009833 4003 00 c
0 pb4l A5825-60001 A56301998291 4003 00 c
0 pb4r A5825-60001 A56302015287 4003 00 c
0 pb5r A5825-60001 A56302009868 4003 00 c
0 pb5l A5825-60001 A56301998339 4003 00 c
0 pb6r A5826-60001 A56302057113 4003 00 c
0 pb7l A5825-60001 A56302015256 4003 00 c
0 mb0l A5517-60001 A56301500436 3914 00 a
0 mb1l A5078-60003 A56E02805226 3941 01 a
0 mb2r A5078-60003 A56E02732689 3941 01 a
0 mb3r A5078-60003 A56E02805205 3941 01 a
0 mb4l A5078-60003 A56E02802215 3941 01 a
0 mb5l A5078-60003 A56E02745477 3941 01 a
0 mb6r A5078-60003 A56E02805258 3941 01 a
0 mb7r A5078-60003 A56E02802287 3941 01 a
0 iolf A5080-60001 1410059 3950 00 a
0 iolr A5080-60001 1410167 3950 00 a
0 iorr A5080-60001 1410180 3950 00 a
0 iorf A5080-60001 1410269 3950 00 a
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
Node IP address Clocks LEDS @C U SHPT Supply1 Supply2 Supply3 Supply4
------------------- ------ --------- ---- ------ ------- ------- ------- -------
0 15.99.111.116 Normal A 0x68 22 1 0000 Nominal Nominal Nominal Nominal
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
================================================================================
spac_interrogator is running on NODE n0 SPAC p1r
r_error_cause0 = 0x0
r_error_cause1 = 0x784000000
r_error_cause_num = 0x0
r_error_config0_reg = 0x7fffff55fdfffff7
r_error_config1_reg = 0x3ff57dffea
r_error_info_reg = 0x18004184
----------------------------------------------------------------------------
Hard Error Group bit = 0x0 The SPAC's hard error pin WAS NOT driven
by another chip.
error_info phase = 0x2
error_info S = 0x0
----------------------------------------------------------------------------
error_cause0 register indicates 0 errors.
----------------------------------------------------------------------------
error_cause1 register indicates 5 error(s):
bit severity error name
--- -------- ----------
0 hard Runway 0 Address Cycle Parity Error
1 hard Runway 0 Data Cycle Parity Error
2 hard Runway 0 Control Parity Error
3 hard Runway 0 Valid Error
8 hard Runway 0 Bad TTYPE Error
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
=========================================================================
Runway Bad Ttype Error.
-------------------------------------------------------------------------
NODE 0 SPAC P1R detected a Runway 0 Bad Ttype Error.
-------------------------------------------------------------------------
Register name Ring value Description
-------------------------------------------------------------------------
r_error_cause1_reg[8] = 1 an error was detected
at RUNWAY 0
r_err_info_reg[16:23] = c no valid data present
-------------------------------------------------------------------------
Error Description:
The SPAC detected an invalid runway ttype or a coherent read using
a tid greater than 0x9.
=========================================================================
****
+++>
/spp/bin//log_event:3.1.0.0:../log_event.c:197
complex: USR411233F (mea) node: 0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2005 12:11 AM
тАО06-28-2005 12:11 AM
Re: V2600 hung
I can't. I never ran that command. But I have a V2600. I have had problems with memory getting deallocated in the past.
If I had something like this, I would just send it to HP support.
But before I even looked at that gook, I would check out the console log messages on the test station. That's where I got enough info to know what's going on on MY box.
If I had something like this, I would just send it to HP support.
But before I even looked at that gook, I would check out the console log messages on the test station. That's where I got enough info to know what's going on on MY box.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 11:02 AM
тАО10-26-2005 11:02 AM
Re: V2600 hung
Chris,
Any resolution on this? We're having V2500 problems and my hard_hist shows very similar things and HP so far has not definitively defined the problem.
Thanks.
Any resolution on this? We're having V2500 problems and my hard_hist shows very similar things and HP so far has not definitively defined the problem.
Thanks.
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