From: mlachwani <mlachwani@mvista.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-mips@linux-mips.org
Subject: Re: start_kernel(): bug: interrupts were enabled early
Date: Wed, 18 Oct 2006 09:51:26 -0700 [thread overview]
Message-ID: <45365B8E.8040704@mvista.com> (raw)
In-Reply-To: <20061018155009.GA22031@deprecation.cyrius.com>
Martin Michlmayr wrote:
> I see the following message when I boot a 2.6.18 kernel on a SWARM
> board:
>
> PID hash table entries: 4096 (order: 12, 32768 bytes)
> Using 512.000 MHz high precision timer.
> start_kernel(): bug: interrupts were enabled early <--
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
> Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
>
> Has anyone else seen this?
>
Yes, I do see it. I have a patch for it as well. Will send it out shortly.
The issue is the on_each_cpu() calls made in arch/mips/mm/c-sb1.c. This
function enables the interrupts on exit. As a result, you will get this
error
on bootup. The fix is similar to arch/mips/mm/c-r4k.c, i.e. to have
something like r4k_on_each_cpu().
Thanks,
Manish Lachwani
next prev parent reply other threads:[~2006-10-18 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 15:50 start_kernel(): bug: interrupts were enabled early Martin Michlmayr
2006-10-18 16:51 ` mlachwani [this message]
2006-10-18 18: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=45365B8E.8040704@mvista.com \
--to=mlachwani@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=tbm@cyrius.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox