wilbur.chan wrote:
The usual reason would be a failure to correctly initialize an interrupt controller, or the Status.IM mask field. The kernel complains precisely *because* IRQ 23 wasn't registered, but an interrupt was nevertheless delivered that was decoded as being that IRQ.Kernal didn't resgister IRQ 23 when booting. Hmm....the only '23' number I can find in kernel is in traps.c. Why a 23 IRQ was triggered?
Regards, Kevin K.