From: Yoann Allain <yallain@avilinks.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: sti() freezes the kernel
Date: Mon, 17 Oct 2005 15:39:24 +0200 [thread overview]
Message-ID: <4353A98C.80508@avilinks.com> (raw)
In-Reply-To: <20051017131047.GF4884@linux-mips.org>
Ralf Baechle a écrit :
>On Mon, Oct 17, 2005 at 10:48:46AM +0200, Yoann Allain wrote:
>
>
>
>>I'm actually trying to start a 2.4 kernel on our new card.
>>The kernel freezes when enabling interrupts with sti() in start_kernel()
>>(just before calculating BogoMips...).
>>This looks like an interrupts is up when enabling so that it stops the
>>MIPS and freezes the kernel.
>>I'm looking after this interrupt but I would like to know if there could
>>be any others reasons for my kernel to freeze when doing a call to sti();
>>
>>
>
>This is a fairly scenario and as you suspect it's being caused by interrupt
>problems, such as interrupts still pending from the firmware, being
>not initialized at all or similar.
>
> Ralf
>
>
Since last mail I played with the interrupt masks (IM - bits 15-8 in
MIPS status register) . From the MIPS cause register, it seems that the
bit 15 (hardware interrupt 5 or timer interrupt) is the originator of
the freezing interrupt. And the exception code shown for this interrupt
is 6 corresponding to a Bus error exception. I think there's a pointer
to the interrupt handler not correctly initialized. So that the
interrupt makes a jump to nowhere.
The Bus monitors are not enabled, this is perhaps why the kernel freezes
instead of printing the details of the exception.
Am I right?
next prev parent reply other threads:[~2005-10-17 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 8:48 sti() freezes the kernel Yoann Allain
2005-10-17 13:10 ` Ralf Baechle
2005-10-17 13:39 ` Yoann Allain [this message]
2005-10-17 15:14 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4353A98C.80508@avilinks.com \
--to=yallain@avilinks.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox