2009/10/22 David Daney <ddaney@xxxxxxxxxxxxxxxxxx>: > IRQ != c0_cause.ExcCode > > You should look up your kernel's IRQ to interrupt source mapping to see > what is connected to IRQ 23. > > David Daney > 2009/10/22 Sergei Shtylyov <sshtylyov@xxxxxxxxxxxxx>: > IRQ # is not a trap #, so the rest of your speculations don't apply. > "unexpected IRQ" probably means that an IRQ occurs for which no handler has > been installed... > > WBR, Sergei > 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?
