rp5470 error

[James Raffeld]

after a planned power cycle of a rp5470 the following error occurs and boot and is displayed on the vfp:

Log Entry # 0 :
SYSTEM NAME: l3000gsp
DATE: 11/05/2003 TIME: 17:27:25
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 9 = serial SOURCE ID: 0
PROBLEM DETAIL: 3 = functional failure

CALLER ACTIVITY: 1 = test STATUS: 0
CALLER SUBACTIVITY: 4C = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x00000063890014C0 00000000 00000000 type 0 = Data Field Unused
0x58000863890014C0 0000670A 05111B19 type 11 = Timestamp 11/05/2003 17:27:25


Whats broke and how do i get more info?

[Joshua Scott]

**Quote**

This is regarding kernel parameter:
Default value of the kernel parameter (ncallout) is too small. DocId: KBRC00007212 Updated: 6/14/01 2:55:00 AM

PROBLEM
Problem Text :

The default value of kernel tunable parameter "ncallout" is
too small and may cause system panic ("callout table overflow")
if many multi-threaded applications are running on HP-UX 11.00.

It is defined with NPROC in
/usr/conf/master.d/core-hpux file as,

ncallout NCALLOUT (16+NPROC)RESOLUTION
The workaround of this phenomenon is to modify the
/usr/conf/master.d/core-hpux file by hand as follows
and recreate new kernel.

from
ncallout NCALLOUT (16+NPROC)
to
ncallout NCALLOUT (16+NKTHREAD)
(or larger).


This has been fixed on HP-UX 11i.

Also, you probably have another issue (Document id: pamLC200111121):
A7 - The chassis code below appears because the Rev B
GSP Card (A6696B) is not fully supported on the
revisions of PDC (L2000 (PDC 40.48) and L3000
(PDC 40.43)) installed on the system. You must
have PDC 41.36 for L3000 and PDC 41.38 for
L1000/L2000.

-------------------------------------------------------------------
***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: octopus
DATE: 08/30/2001 TIME: 10:44:07
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 9 = serial SOURCE ID: 0
PROBLEM DETAIL: 3 = functional failure

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH OFF OFF ON ON
LED State: Running non-OS code. (i.e. Boot or Diagnostics)

0x00000063890014C0 00000000 00000000- type 0 = Data Field Unused
0x58000863890014C0 00006507 1E0A2C07- type 11 = Timestamp
08/30/2001 10:44:07
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:

**End Quote**

See this thread:
http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x946e0ea029a2d711abdc0090277a778c%2C00.html&admit=716493758+1068055152035+28353475

[James Raffeld]

rebuilt kernal and still get error. not sure where to go from here.

[Joshua Scott]

Try here:

http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x778c227a6ab4d711900a0090279cd0f9%2C00.html&admit=716493758+1068059333475+28353475

are you able to get the the BCH menu (interupt the boot when prompted)? type
path
to check the set console path. then, boot HP-UX and do an
ioscan -fkC tty
This will show the paths of the Serial ports on your system.

Post the results back here.

[Joshua Scott · Accepted solution]

OK,

If you have a revision A Core I/O (with the beige 3-way splitter cable) then your console path should be 0/0/4/0. If you have the black 3-way cable, then you need console path 0/0/4/1

The error itself means there's a problem with the serial port on the Core I/O.

See this thread.
http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x2675c1c4ceddd61190050090279cd0f9%2C00.html&admit=716493758+1068059984823+28353475

[Joshua Scott]

Also,

do a control-B and login to the GSP. do "help" and it will display the GSP firmware revision. Post this also. An update to your firmware may fix it.

[James Raffeld]

Console port was wrong. All better now! Thanks!