linux-mips
[Top] [All Lists]

Re: Reserved instruction in kernel code

To: Ales Mulej <Ales.Mulej@HSTX.com>
Subject: Re: Reserved instruction in kernel code
From: David Daney <ddaney@caviumnetworks.com>
Date: Wed, 02 Dec 2009 09:45:48 -0800
Cc: linux-mips@linux-mips.org
In-reply-to: <C5BD21D6E1A3114C8765C8FBBD0087BA330A85@exchtxuk2.HSTX.global.vpn>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <C5BD21D6E1A3114C8765C8FBBD0087BA330A85@exchtxuk2.HSTX.global.vpn>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Thunderbird 2.0.0.21 (X11/20090320)
Ales Mulej wrote:
Hi,

I'm porting linux(2.6.31.6) to the Wintegra WINHDP2 refrence board.

As a refrence I already have an old BSP from Wintegra based on kernel 2.6.10.

During the kernel start up process I receive following error:

Reserved instruction in kernel code[#1]:

Cpu 0

$ 0   : 00000000 1000fc00 802be630 00000001

$ 4   : 802be670 802be674 ffffffff 802f4d4c

$ 8   : 1000fc01 1000001f 00000001 0000002b

$12   : 00000000 000001f5 07a0d380 00000000

$16   : 00000000 00000000 00000000 1000fc00

$20   : 802e9674 bd030f04 3e490000 00000a72

$24 : 00000008 8000167c
$28   : 802ba000 802bbd30 ffffffff 802f4d4c

Hi    : 000000fb

Lo    : 00000001

epc   : 801013a0 handle_ri_int+0x18/0x38

    Not tainted

ra    : 802f4d4c __log_buf+0x0/0x20000

Status: 1000fc03    KERNEL EXL IE

Cause : 50808000

PrId  : 00019365 (MIPS 24Kc)

Modules linked in:

Process swapper (pid: 0, threadinfo=802ba000, task=802bc000, tls=00000000)

Stack : 1000fc00 1000001f 00000001 0000002b 00000000 000001f5 00000000 1000fc00

802be630 00000001 802be670 802be674 ffffffff 802f4d4c 1000fc00 1000001f

00000001 0000002b 00000000 000001f5 07a0d380 00000000 00000000 00000000

00000000 1000fc00 802e9674 bd030f04 3e490000 00000a72 00000008 8000167c

802bbe94 802a2954 802ba000 802bbde0 ffffffff 802f4d4c 1000fc02 000000fb

        ...

Call Trace:

[<801013a0>] handle_ri_int+0x18/0x38

Code: 01094025 3908001e 40886000 <00000040> 00000040 00000040

      ...   ssnop ssnop ssnop ...

One would think a 'PrId  : 00019365 (MIPS 24Kc)' would execute those.

The cause value indicates an 'Interrupt' but you are somehow executing in handle_ri_int, so it could be that multiple exceptions are messing up the OOPS output...




Disabling lock debugging due to kernel taint

Kernel panic - not syncing: Attempted to kill the idle task!

Does anybody know where is the problem?

I suspect, that the problem is in my interrupt routine, because I receive this error as soon as the tick timer start's up.

Regards,

Ales



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