Need Assistance deciphering INI code

[jaxuser]

Have VERY old system with OLD Meridian Mail that has INI multiple times recently.
I got lost in my attempt to decipher the INI code so thought I would request help from the GURUs.

INI000 8000 16 42 14 00BC FF8B 0003 3280 0088

Thank you in advance for any assistance. System is up and running now but want to see why it did this.

 

[rflores69]

>err ini000
>

INI0000 fc hh mm ss pg pc fp fa (x y) hex
An initialization has taken place. The additional fields associated
with this message are described below.

fc = fault code identifying the cause of the initialization. See "FAULT
CODES" on page 555.
hh = the hour of initialization
mm = the minute of initialization
ss = the second of initialization
pg = the program page at the time of trap ( in hexadecimal)
pc = the program xounter (in hexadecimal)
fp = the fault page (in hexadecimal)
fa = the fault address (when the fault page is on page 3). See "Page 3
fault addresses: on page 559.
x = the active CPU, if it is known. If it is not known, a question mark
(?) is output. This field only occurs for dual CPU systems.
y = the active Clock Controller (for multi-group systems)
hex = the contents of the maintenance display (see HEX for
interpretation)
The INI1000 message is followed by DSET000 message.

FAULT CODES

0000 Normal initialize after SYSLOAD. This
code may also appear if a fault occurs
in memory 0. In this case, the
maintenance display should be 10 with
no SYSLOAD message before the
initialize. An INI004 message may
follow.

0001 Manual initialize by attendant. If this
code appears but no attendant has
operated the manual initialize key,
check whether any attendant console
is equipped with an initialize key. If not,
probable software or data error: check
data for each console. If some con-
soles have an initialize key, possible
fault in:

1. Attendant console. Use LD 31 to
check each console having an INI
key.
2. Signaling path to an attendant con-
sole. Use TEST command of LD 45
to check signaling.

0002 Manual initialize from the Miscellane-
ous (MISC) or Interface (IF) pack. If
this code appears but the button on
the MISC pack was not pressed,
probable fault on MISC pack associ-
ated with the active CPU. The
manual initialize button will also re-
enable, if possible, all disabled items.

0003 PE signaling fault. INI003 message will
follow to identify the Peripheral Signal-
ing card at fault.

004 Real-time clock (RTC) has failed (in a
system having two CPUs). Probable
fault in pack providing clock (i.e.
Peripheral Signaling pack or Control,
Interface and Memory pack) or Miscel-
laneous pack associated with active
CPU.

0005 A CPU changeover has taken place
due to a failure of the then-active CPU.
The faulty CPU should be identified by
a subsequent INI005 message. A fault
may exist on:
1. Miscellaneous pack
2. QPC424 CPU pack or daughter
board ROM (especially if mainten-
ance display shows 02)
3. Function (FN), Interface (IF) or
Control and Timing pack
4. CIM pack (especially for mainten-
ance display codes 088 and 08D)
5. CMA pack

0006 Overload detected from a particular
loop. Loop will be disabled. OVD
diagnostic message should follow. If an
OVD message identifying a faulty PE
pack appeared before the initialize,
remove that pack before reenabling
the loop.

0007 Overload detected from a peripheral
signaling pack. Offending Peripheral
Signaling pack will be disabled. OVD
diagnostic message should follow.

0008 Invalid operation code (opcode). Inform
operating company.

0009 Invalid interrupt. Inform operating
company.

000A Attempt to write store using nil pointer.
Software error.

000B Main stack underflow. Software error.

000C Broken queue. Software error.

000D Response timeout in data store 0.
System should reload. Replace data
store 0.

000E Trying to idle Call Register with active
auxiliary Call Registers still linked to it.
Inform operating company.

000F Service change. Data store exceeded.
Should be preceded by a warning
message, "Equip more data store".

0010 Conversions complete.

0011 Triggered by software verification
program (used by operating company
only). If an investigation by the oper-
ating company is not currently active,
then inform the operating company.

0012 Caused by Common Equipment
Diagnostic (CED) trying to rebuild un-
protected data store.

0013 All extenders disabled.

0014 Firmware fault. nCPU clock unmasked.
Same as for 0011.

0015 Firmware fault. RTC interrupt on level 7
unmasked. Same as for 0011.

0017 More than 5 NT8D04 Network or
Network/DTR packs need software
download recovery during the auto-
recovery or midnight audit.
Where: xxxx = cause of the initialization

0018 More than 5 NT8D01 Peripheral
Controllers need software download
recovery during the auto-recovery or
midnight audit.

0019 From Firmware: The system has
initialized after recovery from battery
backup. (Note: that the system clock
has slipped during the time that the
system was under battery power.)

001C There have been more than 10 occur-
ences of auto-recoveries to avert
INI000 000C problems since the last
system initialization. INI000 001C was
triggered to perform system cleanup
following midnight routines.

Action: Report the problem to your support
engineer for further analysis.

001D An invalid pointer is found during
queue processing.

Action: Report the problem to your support
engineer for further analysis.

0100 Trap data blocks are not valid. No
action.

0200 SYSLOAD was caused by response
timeout of data store.

0400 Power-on reset. Power-up, manual
reload.

0800 Software trap. No action.

1000 Memory Parity error. Determine fault
page ( field 7 of INI000 message).
Suspect a faulty:
1. CMA pack
2. MISC pack
3. Memory pack

2000 Watchdog timer runlet. This is some-
times a software fault, but may also
indicate hardware faults as follows:
1. If an INI002 or INI003 message
follows, the device(s) specified may
be faulty.
2. If the maintenance display = 04,
the following packs are suspect,
(in addition to those listed in the
Maintenance Display Code
interpretations):
a Ce extender packs
b Miscellaneous
c Serial Data Interface (SDI)
d Tape Interface
e Tone and Digit Switch (TDS)
3. If the maintenance display = 05, the
following packs are suspect, (in
addition to those listed in the
Maintenance Display Code
interpretations):
a Peripheral Signaling
b CE extender.

4. Affected CPU may be faulty.
5. CIM may be faulty (if equipped).
6. Also occurs if a TDS card is in
slot 5 of an SL-1 ST and configured
as loop 0. This is not a valid
configuration.

3000 Same as code 1000.

4000 Write protection violation. An attempt
was made to overwrite a protected
memory location. Possible software
fault. This code may also appear if the
affected CPU is faulty, especially the
MISC pack.

5000 Same as code 1000.

6000 Same as code 2000.

7000 Same as code 1000.

8000 Response timeout. A memory or other
device failed to respond to a read-write
request.

If an INI002, INI003 or INI004
message follows the indicated
device(s) may be faulty. If several
devices on the same shelf are indi-
cated, the CE extender connecting the
shelf to the CPU may be faulty.

If none of the above messages appear,
this code probably indicates a software
fault, or:
1. CPU fault, especially Miscellan-
eous pack and, if equipped, Inter-
face (IF) pack of affected CPU.
2. Peripheral Signaling pack on
same bus as affected CPU.
3. CIM (if equipped).
4. Faulty ROM on CPU (QPC424 or
QPC425).

9000 Same as code 1000.

A000 Same as code 8000.

B000 Same as code 1000.

C000 Same as code 8000.

D000 Same as code 1000.

E000 Same as code 8000.

F000 Same as code 1000.

Page 3 fault addresses
This table is used to interpret the fault
address for page 3 faults (external devices).
To obtain the address of the faulty circuit pack, the 4-digit
hexadecimal codes must be
converted to 4-digit binary numbers (see HEX).

Outputs not covered in this table cannot be decoded to an address.
However they may indicate a Bus Fault.

0800 to 0807 CPU/Extender

1806 CMA pack

3000 to 3F7F Serial Data Inter (SDI).
Bits 4 to 7 provide card
addressing.

3FC8 Tape Interface pack

8000 to A7FF Network pack

For single Network packs:
Bits 7 to 13 for non-enhanced
network loops
Bits 11 to 13 for group.
Bits 2 to 6 determine timeslots
used.

For dual Network packs:
Bits 6 to 10 for loop
Bits 11 to 13 for group.
Bits 1 to 5 determine timeslots
used.

C000 to D3FF Peripheral Signaling (PS) pack
Bits 13 to 15 give PS address.
Bits 9 to 12 give loop
address.

E000 to E8FF Intergroup Switch. Address Bit 5 deter-
mines the odd or even switch
(i.e., 0 or 1). Address Bits 9
through 11 determine the card
affected.

F000 to FFFF Intergroup Switch. If bit 5=0, then
card 0 is affected. If bit 5=1,
then card 1 is affected.

Severity: Critical

 

[Firebird Scrambler]

A quick look at the error shows it to be more confusing!.

INI000 8000 16 42 14 00BC FF8B 0003 3280 0088
INI0000 fc hh mm ss pg pc fp fa (x y) hex

Translates to

INI0000 = 0000 Normal initialize after SYSLOAD
fc = 8000 Response timeout. A memory or other device failed to respond to a read-write request.
hh mm ss = 16 42 14 The time that the event happened
pg = 00BC The program page at the time of trap (in hexadecimal) 188 in decimal.
pc = FF8B The program xounter (in hexadecimal) 65419 in decimal.
fp = 0003 The fault page (in hexadecimal) 3 in decimal.
fa = 3280 The fault address 12928 in decimal.
(x) hex = 00 which means it's on CPU 0
hex = 88 which means it's the active Clock Controller (for multi-group systems)

It might be worthwhile looking at any errors in "pdt" around this time period. Just having the one error might not be enough.


Firebird Scrambler
Nortel Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Advance knowledge on BCM support

http://www.linkedin.com/in/davidbromley

 

[jaxuser]

Thank you, I will check pdt once back on site; had to make the long drive to another critical ticket. This one stable at the moment.