linux-mips
[Top] [All Lists]

Re: Got trap No.23 when booting mips32 ?

To: Sergei Shtylyov <sshtylyov@ru.mvista.com>, ddaney@caviumnetworks.com
Subject: Re: Got trap No.23 when booting mips32 ?
From: "wilbur.chan" <wilbur512@gmail.com>
Date: Thu, 22 Oct 2009 08:04:21 +0800
Cc: linux-mips@linux-mips.org
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=q9m89a3GluRyt5eMu9298MLGoyZqJWWIXUekKFMyReY=; b=OOK+DiyO/zgdJyrI6qd3lt/2vMGDHtGnoAm04gek+GFgowou6dsZ/QHJrmOoLNfmVe 3xxdZwFO1aexfmpxa77iDVRboTcV7hX/fDJtXoD/6q4+VbxhNNelMbUmpgQ2PIBXQSa8 Xt9CKbSv0ckmxjOFCwVYXxDwv3IOSHESRfYFA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=jgBi73umHIF+6uRf6sNDAH8YIntDCErM4FTp1yKfsQuwQdM5W/lX8wLUtTYv6khUCj vxGOUyf8uplTWDYUACvgYee/NGz7SF9bvDpzEJfdyyQ4uNPqhqMt4kGRmPDbACZcge3D +vHTU5R28RE8cjJMgOB9tjN7exOHuHmFIn1fo=
In-reply-to: <4ADF32D1.6030801@ru.mvista.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <e997b7420910210740l4a8fefai27c81152a6c288ef@mail.gmail.com> <4ADF32D1.6030801@ru.mvista.com>
Sender: linux-mips-bounce@linux-mips.org
2009/10/22 David Daney <ddaney@caviumnetworks.com>:
> 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@ru.mvista.com>:
>   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?

<Prev in Thread] Current Thread [Next in Thread>