| To: | Martin Michlmayr <tbm@cyrius.com> |
|---|---|
| Subject: | Re: start_kernel(): bug: interrupts were enabled early |
| From: | mlachwani <mlachwani@mvista.com> |
| Date: | Wed, 18 Oct 2006 09:51:26 -0700 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <20061018155009.GA22031@deprecation.cyrius.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20061018155009.GA22031@deprecation.cyrius.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Thunderbird 1.5.0.7 (X11/20060909) |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH][MIPS] merge a few printk in check_wait(), Ralf Baechle |
|---|---|
| Next by Date: | Re: patch: include/asm-mips/system.h __cmpxchg64 bugfix and cleanup, Antonio SJ Musumeci |
| Previous by Thread: | start_kernel(): bug: interrupts were enabled early, Martin Michlmayr |
| Next by Thread: | Re: start_kernel(): bug: interrupts were enabled early, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |