Technical data

7-2 IRIX Error Reporting
7.2.1 Interpreting Panic Messages
The following message usually indicates a hardware problem:
WARNING: Kernel Bus Error Exception ...
HARDWARE ERROR STATE:
...
PANIC: CPU n: Kernel Bus Error Exception ...
This kind of message also indicates a hardware problem:
WARNING: Bus Error Exception in User mode ...
HARDWARE ERROR STATE:
...
PANIC: CPU n: Bus Error Exception in User mode ...
There are some cases in which this message displays because of software bugs. This is
discussed in further detail below.
Note that it is not useful to report only the Bus Error Exception message when filing a bug
report. The HARDWARE ERROR STATE messages are the most useful messages.
The following message means that a chip detected a problem and sent an interrupt to a
CPU. This is probably a hardware problem.
Received interrupt at level 0x7a due to FCHIP ERROR
HARDWARE ERROR STATE: ...
The following kernel fault message indicates a software bug:
PANIC: CPU 1: KERNEL FAULT
PC: 0x8012681c ep:ffffc888
EXC code:128, ‘Software detected SEGV ‘ (or)
Read Address Error (or)
Write Address Error
Bad addr: 0x0, cause: 0x8<CE=0,EXC=RMISS>
This message indicates the kernel read or wrote an out-of-range, or misaligned address.
Despite the fact that the panic message lists a specific CPU, this message does not
necessarily indicate a problem with that CPU.
In general, even if a panic message is followed by a CPU number, it does not automatically
indicate a hardware problem (with the exception of the cases listed above).
The following message does not appear in production kernels. It should appear only in
special engineering builds in which assertations are turned on:
assertion failed cpu n: <some C code> file: xxx.c, line: nn
This message normally indicates a software bug.