All of lore.kernel.org
 help / color / mirror / Atom feed
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

  reply	other threads:[~2006-10-18 16:51 UTC|newest]

Thread overview: 50+ 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
  -- strict thread matches above, loose matches on Subject: below --
2010-03-25 19:41 Rabin Vincent
2010-03-31 20:40 ` Andrew Morton
2010-03-31 20:47   ` Yinghai Lu
2010-03-31 20:52     ` Andrew Morton
2010-03-31 21:12       ` H. Peter Anvin
2010-03-31 21:28         ` Andrew Morton
2010-03-31 22:35           ` Benjamin Herrenschmidt
2010-04-01 16:13         ` Linus Torvalds
2010-04-01 14:27           ` Andrew Morton
2010-04-01 20:12             ` Linus Torvalds
2010-04-02 14:46               ` David Howells
2010-04-02 14:54                 ` Linus Torvalds
2010-04-07 19:09           ` Kevin Hilman
2010-04-07 19:09             ` Kevin Hilman
2010-04-08 15:55             ` Américo Wang
2010-04-08 15:55               ` Américo Wang
2010-03-31 21:01     ` Matthew Wilcox
2010-03-31 21:05       ` H. Peter Anvin
2010-03-31 21:17         ` Matthew Wilcox
2010-03-31 21:42           ` Christoph Lameter
2010-03-31 21:54             ` Russell King
2010-03-31 21:57               ` H. Peter Anvin
2010-03-31 21:57                 ` H. Peter Anvin
2010-03-31 22:30                 ` Russell King
2010-03-31 22:37                 ` Benjamin Herrenschmidt
2010-03-31 22:49                   ` Andrew Morton
2010-04-01  1:17                     ` Benjamin Herrenschmidt
2010-03-31 22:26                       ` Andrew Morton
2010-04-01  6:26                         ` H. Peter Anvin
2010-04-01  3:33                           ` Andrew Morton
2010-04-01  6:48                             ` Benjamin Herrenschmidt
2010-04-01 11:06                               ` David Howells
2010-04-01 15:55                                 ` Christoph Lameter
2010-04-01 23:00                                 ` Benjamin Herrenschmidt
2010-04-01 16:15                               ` H. Peter Anvin
2010-04-01  6:50                           ` Benjamin Herrenschmidt
2010-03-31 22:36             ` Benjamin Herrenschmidt
2010-04-01 15:57               ` Christoph Lameter
2010-03-31 21:05     ` Russell King
2010-03-31 21:08       ` H. Peter Anvin
2010-03-31 21:08         ` H. Peter Anvin
2010-03-31 22:58       ` David Howells
2010-04-01  9:41         ` Jamie Lokier
2010-04-01 10:50           ` David Howells
2010-04-01 11:23           ` Matthew Wilcox
2010-03-31 22:31     ` Benjamin Herrenschmidt
2010-03-31 22:36       ` H. Peter Anvin

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 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.