> The bad thing with a bus error is that it may be delayed for a very long
> time thus resulting in a useless program counter. What happens is that
> the CPU writes to some invalid address but the write access over the
> system bus is delayed because the writeback cache policy is being used.
> Later, maybe even much later, when the cacheline gets written back to
> memory for some reason the system board signals a bus error interrupt.
> At this point the program counter may already be completly useless.
You cannot get a delayed bus error on a cached write, unless
you do a "create dirty exclusive" cache operation to validate the line
before writing. You can get delayed bus errors on uncached writes,
as to device control registers. Since any K1SEG address is uncached,
it is not too hard to generate a bus error with a bad pointer value.