Appendix
660
9836 3521 01
10.5 Fatal Software Errors
If a fatal software error occurs in the TC software an error code is generated by the real time operating
system (called OSE) and it is shown on the display of the TC, e.g.
OSE Error 0x103
Most of the fatal software errors indicate some kind of bug in the TC software. Normally you can just
restart the TC and it will work fine again, at least for a while. If you get a fatal software error you should
always try to get the TC Crash log from the TC, to help debugging.
The errors 0x01, 0x02, 0x03, 0x11, 0x20, 0x21 and 0x24 indicate insufficient memory. This might be
cause by running too many, memory consuming, devices on the failing TC. Try to move one or more of
the devices from the failing TC to another TC in the system. Especially devices used for reporting of Trace
and Cycle data may consume much memory.
This list show possible OSE error codes.
Code
Description
0x01
Too large stack buffer requested.
0x02
Out of space in user stack pool.
0x03
Too many processes were created.
0x11
Too large signal buffer requested.
0x12
Out of space in kernel pool.
0x1d
An attempt to kill a static semaphore was made.
0x1e
An attempt to kill a semaphore that is still in use was made.
0x1f
An illegal semaphore pointer was presented to the kernel.
0x20
Out of space in user signal pool.
0x21
Pool extension failed.
0x22
The create_pool system call was used on a block that contains processes.
0x23
The create_pool system call was presented a signal size table or a stack size table that contains
an unreasonable number in the first location.
0x24
Too many signals were attached.
0x25
Vector already in use.
0x26
Illegal system call from an interrupt process.
0x27
Illegal intersegment send to an interrupt or timer-interrupt process.
0x28
Illegal wakeup priority for an interrupt process.
0x29
An error was encountered while an error handler was executing.
0x2a
An error was encountered while an error handler was executing.
0x2b
A semaphore with a negative initial value was found or created.
0x2c
A semaphore in use was implicitly killed, but processes are still waiting for it.
Summary of Contents for PowerMACS 4000
Page 2: ......
Page 46: ...System Architecture 46 9836 3521 01...
Page 267: ...Tightening 9836 3521 01 267...
Page 400: ...Tightening 400 9836 3521 01...
Page 486: ...Peripheral Devices 486 9836 3521 01...
Page 622: ...Peripheral Devices 622 9836 3521 01...
Page 664: ...References 664 9836 3521 01...
Page 668: ...9836 3521 01 2010 11 Edition 10 3 0 www atlascopco com...