linux-mips
[Top] [All Lists]

Re: Got trap No.23 when booting mips32 ?

To: David Daney <ddaney@caviumnetworks.com>
Subject: Re: Got trap No.23 when booting mips32 ?
From: "wilbur.chan" <wilbur512@gmail.com>
Date: Thu, 22 Oct 2009 08:02:20 +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 :content-transfer-encoding; bh=lJGfaq312dIbD4FHmNKgpMGPy0NVFcakB1mF5JJFF1A=; b=O+01rxmgEy7rbHZwBM5GEwPxSNaMVA+LUhj4Q4o9al9E8MowEZcfv4X3KxGpQPLRwL kCYsX4ATX/uNwhhJeYnlYiP4UBXdxrqmixxXZyqsKoo8692ly2gHYzjcqm9RXnsgMmQd +nXURx4YTMQkOO4ripbb2gHe6rYFuCkJyDpr0=
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:content-transfer-encoding; b=fqMWYNEa7mdEL52NQ+59td+AihWbaD+JSLSpGWDwHTRbOwU8IYZa/Mk4kHL6lI7VCJ w6JN+chyUcEVCKh/TWUyWzh0mLYG3Vy6hC4pKyw/jvO3bRhFxxPqpgCDckpucJTKiq2Z Erh3mCIhT2WzD3IPmfxgrjuYg2OO5ROw3QvIU=
In-reply-to: <4ADF3240.9040900@caviumnetworks.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <e997b7420910210740l4a8fefai27c81152a6c288ef@mail.gmail.com> <4ADF3240.9040900@caviumnetworks.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>:
>> No.23 trap is a Watch trap, which means that, when
>
>   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>