GCC4 fun.

[Rune Torgersen]

I have seen it since 2.6.11-rc2

It is not a fatal error, just more of a warning.
It complains because schedule() was called while scheduling is disabled
during initial setup

As far as I have been able to track it down, schedule gets called after
syscalls, and in this case (and in mine on a 8260)
It gets called when the proc filesystem is enabled.

These errors surfaced on PPC after Ingo Molnars patches to get rid of
the BKL (Big Kernel Lock)

> -----Original Message-----
> From: linuxppc-dev-bounces at ozlabs.org 
> [mailto:linuxppc-dev-bounces at ozlabs.org] On Behalf Of Marc Leeman
> Sent: Thursday, March 03, 2005 07:14
> To: Joerg Dorchain
> Cc: linuxppc-dev at ozlabs.org
> Subject: Re: GCC4 fun.
> 
> > scheduling while atomic: swapper/0x00000002/0
> > Call trace:
> >  [c0007620] dump_stack+0x18/0x28
> >  [c01de704] schedule+0x678/0x67c
> >  [c0004500] syscall_exit_work+0x108/0x10c
> >  [c02a97b4] proc_root_init+0x168/0x174
> >  [ff847288] 0xff847288
> >  [c02945e8] start_kernel+0x144/0x170
> >  [00003a30] 0x3a30
> 
> We have something similar with PPC 8245, I was planning to have a look
> at it, but didn't get round to it. Since our system is 
> crunching numbers
> since yesterday evening without fault, I guess it's not that 
> serious...
> 
> -- 
>   greetz, marc
> Aeryn died so you could live John. She would want you to keep 
> fighting.
> 	D'Argo - Season of Death
> scorpius 2.6.11 #1 Wed Mar 2 16:38:38 CET 2005 GNU/Linux
>