| To: | "wilbur.chan" <wilbur512@gmail.com> |
|---|---|
| Subject: | Re: Got trap No.23 when booting mips32 ? |
| From: | "Kevin D. Kissell" <kevink@paralogos.com> |
| Date: | Wed, 21 Oct 2009 17:50:38 -0700 |
| Cc: | Sergei Shtylyov <sshtylyov@ru.mvista.com>, ddaney@caviumnetworks.com, linux-mips@linux-mips.org |
| In-reply-to: | <e997b7420910211704w67517b3bud6f4757a35945ba@mail.gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <e997b7420910210740l4a8fefai27c81152a6c288ef@mail.gmail.com> <4ADF32D1.6030801@ru.mvista.com> <e997b7420910211704w67517b3bud6f4757a35945ba@mail.gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Thunderbird 2.0.0.23 (X11/20090817) |
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.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Got trap No.23 when booting mips32 ?, wilbur.chan |
|---|---|
| Next by Date: | Re: [PATCH -v4 9/9] tracing: add function graph tracer support for MIPS, Wu Zhangjin |
| Previous by Thread: | Re: Got trap No.23 when booting mips32 ?, wilbur.chan |
| Next by Thread: | Re: Got trap No.23 when booting mips32 ?, wilbur.chan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |