Linux MIPS Architecture development
 help / color / mirror / Atom feed
* start_kernel(): bug: interrupts were enabled early
@ 2006-10-18 15:50 Martin Michlmayr
  2006-10-18 16:51 ` mlachwani
  0 siblings, 1 reply; 3+ messages in thread
From: Martin Michlmayr @ 2006-10-18 15:50 UTC (permalink / raw)
  To: linux-mips

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?
-- 
Martin Michlmayr
http://www.cyrius.com/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: start_kernel(): bug: interrupts were enabled early
  2006-10-18 15:50 start_kernel(): bug: interrupts were enabled early Martin Michlmayr
@ 2006-10-18 16:51 ` mlachwani
  2006-10-18 18:14   ` Ralf Baechle
  0 siblings, 1 reply; 3+ messages in thread
From: mlachwani @ 2006-10-18 16:51 UTC (permalink / raw)
  To: Martin Michlmayr; +Cc: linux-mips

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: start_kernel(): bug: interrupts were enabled early
  2006-10-18 16:51 ` mlachwani
@ 2006-10-18 18:14   ` Ralf Baechle
  0 siblings, 0 replies; 3+ messages in thread
From: Ralf Baechle @ 2006-10-18 18:14 UTC (permalink / raw)
  To: mlachwani; +Cc: Martin Michlmayr, linux-mips

On Wed, Oct 18, 2006 at 09:51:26AM -0700, mlachwani wrote:

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

Also cosider using the local_* variant of a cache or tlb flush operation
wherever possible.

  Ralf

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-10-18 18:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-18 15:50 start_kernel(): bug: interrupts were enabled early Martin Michlmayr
2006-10-18 16:51 ` mlachwani
2006-10-18 18:14   ` Ralf Baechle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox