Troubleshooting
Problem
Troubleshooting OS/2 trap errors for Servers and IntelliStation.
Resolving The Problem
Operating System errors and Stop Codes (called Blue Screens in Microsoft Windows, Abends in Novell NetWare, Kernel Panics in UNIX) are often the result of application and/or file corruption that can occur as a result of poor application programming or known bugs that exist in all software. Fixes to these issues are periodically released in software patches known as Service Packs, Fix Packs, or Hot Fixes. However, there are instances when errors and Stop Codes may indicate a hardware source or problem. The following lists detail the most common hardware-related error codes and actions to take when they occur.
Note: If IBM hardware has recently been added or changed or if hardware errors (during POST/Startup) are occurring with the OS errors, please refer to the appropriate IBM hardware section for troubleshooting.
Trap errors under IBM OS/2 Warp:
There are a maximum of 255 possible traps. Trap errors consist
of interrupts and exceptions. An interrupt is an event external to
the processor that can occur at random times during system
operation. An exception is a special condition which is detected by
the processor during the execution of instructions. Exceptions only
occur when the processor is executing instructions.
- Traps 0 through 16, with the exclusion of Trap 2, are special exceptions that are detected by the processor. If they occur, the processor takes the appropriate action according to the instructions in the interrupt handler routine of your operating system. The exception handler can vary widely according to the software vendor.
- Trap 2 is a non-maskable interrupt (NMI) error indicating a catastrophic system failure.
- Traps 17 through 31 are exceptions reserved by Intel.
- Traps 32 through 255 are maskable interrupts that are user defined.
A summary of the traps is shown below:
|
Trap Number:
|
TRAP Code (Hex):
|
Description:
|
Explanation:
|
|---|---|---|---|
|
0
|
0000
|
Divide By Zero Error
|
An application program attempted to divide a
number by zero. Contact software support.
|
|
1
|
0001
|
Debug Exception
|
Contact software support.
|
|
2
|
0002
|
NMI Interrupt
|
An NMI interrupt is generated by the system when
a catastrophic error occurs. See below for
further TRAP0002 troubleshooting information.
|
|
3
|
0003
|
Debug Breakpoint
|
This is a special instruction (INT 3) used in
"debugging" software, which was left in the code either
accidentally or by design. Contact software support.
|
|
4
|
0004
|
Overflow Detected
|
An overflow occurred while doing an arithmetic
operation. Contact software support.
|
|
5
|
0005
|
Bound Range Exceeded
|
A BOUND instruction exceeded the specified
limits. Contact software support.
|
|
6
|
0006
|
Invalid Opcode Instruction
|
The processor tried to execute an unreserved
invalid opcode. Contact software support.
|
|
7
|
0007
|
Coprocessor Not Available
|
If coprocessor diagnostics run error-free,
contact software support.
|
|
8
|
0008
|
Double Fault
|
The processor detected an exception while
processing an exception. It could be caused by either hardware or
software. If TRAP0002 is also being experienced, contact hardware
support.
|
|
9
|
0009
|
Coprocessor Segment Overrun
|
The middle portion of a coprocessor operand is
protected or not-present. Contact software support.
|
|
10
|
000A
|
Invalid Task State Segment
|
A task switch to an invalid task switch segment
was attempted. Contact software support.
|
|
11
|
000B
|
Segment Not Present
|
The segment being referenced is not present.
Contact software support.
|
|
12
|
000C
|
Stack Fault
|
Contact software support.
|
|
13
|
000D
|
General Protection
|
All protection violations which do not cause
another exception, cause a TRAP000D. Contact software
support.
|
|
14
|
000E
|
Page Fault
|
The page being referenced is not present in
memory or the procedure referencing the page does not have enough
privilege to access the page. Contact software support.
|
|
15
|
000F
|
Intel Reserved - Do Not Use
|
Contact Intel.
|
|
16
|
0010
|
Coprocessor Error
|
The processor detected an error from the
coprocessor. This could be caused by hardware or software.
|
|
17 through 31
|
0011-001F
|
Intel Reserved - Do Not Use
|
Contact Intel.
|
|
32 through 255
|
0020-00FF
|
Maskable Interrupts
|
User defined. Contact software support.
|
TRAP0002 - NMI
INTERRUPT
An NMI interrupt is generated by the system when a
catastrophic error occurs. This is typically the result of a
hardware problem (specifically memory or cache). However, there can
be four possible causes of this problem:
- 110 error - system board memory parity error
- 111 error - I/O channel check (adapter card error)
- 112 error - watchdog timeout (may be hardware or software)
- 113 error - DMA timeout (may be hardware or software)
Run extended diagnostics on the system. The Service Aid Diskette (SADA) may be useful to determine whether the problem was a 110, 111, 112, or 113 error. If a 112 or 113 error cannot be resolved by hardware troubleshooting, software support should be contacted. (Some operating systems do not support this Service Aid diskette.)
Note: Some systems have serial and parallel ports with DMA arbitration. If DMA arbitration errors are encountered during I/O operations to these ports, changing the arbitration to another level, or to "disable," may correct the problem.
For further problem determination of TRAP0002 errors on ISA or EISA bus systems, examine the ERRCD field of the TRAP screen. This field contains the values from hardware port 0x61.The following codes indicate the actions needed:
Note: The ERRCD field is available beginning with OS/2 Warp 3 FixPak 14, and OS/2 2.11 FixPak 103, and is included in OS/2 Warp 4 base level.
- 0000 - Software caused NMI 0001 - RAM error, check memory (parity error)
- 0002 - Adapter caused error (I/O channel check)
- 0003 - Check bus mastering adapters, update adapter drivers. Also disable bus mastering on failing adapters as a problem determination tool to figure out which adapter is causing the failure. Contact the adapter vendor for further assistance. (DMA timeout)
- 0004 - A device driver or DOS application disabled interrupts too long. Contact appropriate software vendor for updated software (Watchdog timeout).
- 0005 - Contact application or device driver hardware vendor (software generated NMI)
- 0006 - see error code 0003
- 0007 - see error code 0004
- 0008 - see error code 0002
- 0009 - see error code 0001
The following built inOS/2 error messages can be queried to see additional help for the error codes. At an OS/2 command prompt, type HELP followed by the ERRCD error code number to get more help. For example, type HELP 1945 then press Enter.
- 0000 1944
- 0001 1945
- 0002 1946
- 0003 1947
- 0004 1948
- 0005 3140
- 0006 3141
- 0007 3142
- 0008 3143
- 0009 3144
Additional information
Please select one of the the following options for further assistance:
Document Location
Worldwide
Applicable countries and regions
- Worldwide
Was this topic helpful?
Document Information
More support for:
Older System x->Netfinity 7000
Operating system(s):
OS/2
Document number:
846958
Modified date:
28 January 2019
UID
ibm1MIGR-40768