Technical data

7-4 IRIX Error Reporting
HARDWARE ERROR STATE Caused by Software
The following message can be caused by software that mistakenly generates a non-existent
address:
A Chip ADDR_HERE not asserted
A non-existent address on the EBus results in a display with the A Chip Error Register bit
ADDR_HERE not asserted message. For example:
pb 8: <4>WARNING: CPU 3 Bus Error Exception in User mode...
pb 9: HARDWARE ERROR STATE:
pb 10: + IP19 in slot 7
pb 11: + A Chip Error Register: 0x8000
pb 12: + 15:CPU 3 ADDR_HERE not asserted
pb 13: + CC in IP19 Slot 7, cpu 3
pb 14: + CC ERTOIP Register: 0x100
pb 15: + 8:Address Error on MyRequest on EBUS
pb 16: + IP19 in slot 9
pb 17: + A Chip Error Register: 0x8000
pb 18: + 15:CPU 3 ADDR_HERE not asserted
pb 20: <0>PANIC: CPU 3: Bus Error Exception in User mode...
Although this can be a hardware error, such as a board failing to decode its address, usually
this is a software problem.
IA ADDR_HERE not asserted
Software can cause an IA ADDR_HERE not asserted message by programming a device
to do DMA to a non-existent address. An example message might be:
HARDWARE ERROR STATE:
+ IO4 board in slot 3
+ IA EBUS Error Register: 0x24
+ 2: ADDR_ERROR Detected
+ 5: ADDR_HERE not asserted or My ADDR_ERROR Received
+ IA Error EBus Address: 0xfffffff800
+ 47..40: EBus Outgoing Command: 0x1
+ 48: Originating IOA number = 5
+ 54: DMA Read
+ 55: Address Map Match
+ Fchip in IO4 slot 3 adapter 5, FCI master: FCG
-
7.3 Warning Messages
The warning message syntax is: WARNING: CPU n xxx, where “n” is the processor number
and “xxx” is the string indicating the general area of the fault. Warnings often result from
the kernel nearly running out of some resource, indicating that a kernel software
configuration change is needed.