From: Ralf Baechle <ralf@linux-mips.org>
To: Yoann Allain <yallain@avilinks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: sti() freezes the kernel
Date: Mon, 17 Oct 2005 14:10:47 +0100 [thread overview]
Message-ID: <20051017131047.GF4884@linux-mips.org> (raw)
In-Reply-To: <4353656E.8070601@avilinks.com>
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
next prev parent reply other threads:[~2005-10-17 13:11 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 [this message]
2005-10-17 13:39 ` Yoann Allain
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=20051017131047.GF4884@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=yallain@avilinks.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.