Re: [microblaze-uclinux] BUG: scheduling while atomic: (Kernel 2.6)

[Jim Van Vorst <jvanvorst@xxxxxxxxx>]

I get this a lot as well:

# more /proc/partitions
<< /proc/partitions >>
major minor  #blocks  name

 31     0        768 mtdblock0
 31     1        256 mtdblock1
 31     2        256 mtdblock2
 31     3        128 mtdblock3
 31     4       4096 mtdblock4
 31     5       1024 mtdblock5
 31     6   BUG: scheduling while atomic: sh/0x00000008/47

Stack:
 23effc08 2200ed08 23e9140c 00000000 00000000 22001c54 22161ca0 23c9d8ec
 00000008 0000002f 01c9c380 0000000e 23efe000 00000008 00000000 00000000
 23efffbd 23e9140c 00000000 00000000 2397ff1c 00000000 00000000 23e91c54
Call Trace: [<2200ed08>] [<22001c54>] [<2215daa4>] [<2200ed08>] 
[<220016b4>]
   9216 mtdblock6
 31     7       1424 mtdblock7

I then tried enabling CONFIG_PREEMPT:

# more /proc/partitions
<< /proc/partitions >>
maBUG: scheduling while atomic: more/0x7200546f/54

Stack:
 238efd34 00000000 2397ff1c 00000000 22001758 22001dd4 2217dcb0 238818f0
 7200546f 00000036 221b9bf0 00000000 00000008 238ee670 238ee474 0000001b
 00000000 238eff78 00000000 2397ff1c 00000000 00000000 00000000 238efe24
Call Trace: [<22001758>] [<22001dd4>]
jor minor  #blocks  name

 31     0        768 mtdblock0
 31     1        BUG: scheduling while atomic: more/0x7200546f/54

Stack:
 238efda0 00000000 2397ff1c 00000000 22001758 22001dd4 2217dcb0 238818f0
 7200546f 00000036 00989680 00000000 00000008 00000020 00000005 00000001
 0000000f 238eff78 00000000 2397ff1c 00000000 00000000 00000000 238efe90
Call Trace: [<22001758>] [<22001dd4>]
256 mtdblock1
 31     2        256 mtdblock2
 31     3        128 mtdblock3
 31     4       4096 mtdblock4
 31     5       1024 mtdblock5
 31     6       9216 mtdblock6
 31     7       1424 mtdblock7

Woohoo!  Crashes in more instead of sh...

I don't get these all the time but it's very easy to replicate.
Sometimes my board keeps going, sometimes it freezes.
It's not just more or cat.  Basically any command will do it.
I don't remember getting these with the 2.4 kernel.

John Williams wrote:
> Hi Chun Yeow,
>
> Thanks for the report - we'll look into it and let you know via the list.
>
> Thanks again,
>
> John
>
> Yeoh Chun Yeow wrote:
> > Dear all,
> >
> > I compile the 2.6 kernel in the petalogix distribution. My file 
> > system is in romfs format.
> >
> > I have found "BUG: scheduling while atomic: sh/0x00000008/43" in my 
> > kernel execution.
> >
> > BUG: scheduling while atomic: sh/0x00000008/43
> >
> > Stack:
> >   27efeac4 27ece5cc 245d1d20 00000001 0000005b 24001ed4 2418a0e4 
> > 244ea1c4
> >   00000008 0000002b 0ba0f600 27efea30 00000008 245d15e0 245d15e0 
> > 2459e000
> >   27ece5cc 245d1d20 00000001 0000005b 27effc30 00000000 00000000 
> > 27efebb4
> > Call Trace:
> > [<24001ed4>] ret_from_intr+0x1c/0x40
> >
> >
> > After I enable in CONFIG_PREEMPT, thing get better.
> >
> > But, now when I doing the ping, the following bugs occur:
> >
> >  bytes from 199.20.6.174 <http://199.20.6.174>: icmp_BUG: scheduling 
> > while atomic: ping/0x00000002/62
> >
> > Stack:
> >   2465fc14 27cb28b0 000000c0 00000000 27d1e120 241a7f9c 241ab0a8 
> > 27d1b1d8
> >   00000002 0000003e 2465e000 000000a2 240166c0 7fffffff 00000000 
> > 2465fc8c
> >   2465fce0 2465fd18 00000000 00000000 27cb28b0 000000c0 00000000 
> > 2411b36c
> > Call Trace:
> >
> > What is the reason behind that? Any ideas?
> >
> > Please advice. Thanks
> >
> > regards,
> > chun yeow
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/