Re: [microblaze-uclinux] kernel BUG at sched.c:687!

["DeviPrasad Natesan" <ndprasad@xxxxxxxxx>]

Hi,
When i get the "kernel BUG at sched.c:562!" this is what my "current"
task_struct (which always is ntpd) says.

current->state   2   (or 0 manytimes)
current->flags   0x504
current->need_reshed   1
current->mm    0
current->active_mm    0
current->comm   "ntpd"
current->blocked->sig[0]  0x41e00000
current->blocked->sig[0]  0x00

According to the flags, it is killed by a signal (PF_SIGNALED and
PF_EXITING). How do i find out which signal killed it and why should
the kernel hang becos of that. Should it not gracefully exit..!!! My
backtrace doesn't reveal anything either as currrent->mm is already 0.

Please let me know if you have any idea on whats happening.

Thanx
- Prasad


On 4/24/06, Alejandro Lucero <alucero@xxxxxxxxx> wrote:
>
> Hi Prasan,
>
> This is not a bug. Just it is necessary for the stack checking code.
>
> Regards.
> >
> > Thanx
> > - DeviPrasad
> >
> > On 4/23/06, Alejandro Lucero <alucero@xxxxxxxxx> wrote:
> > > Hi Prasad,
> > >
> > > Surely the problem is when an interrupt arrives in the middle of a switch
> > > thread. I don't have this problem in my code since I have other
> > > modifications to the entry.S file.
> > >
> > > It should work adding a BIPSET(r11) and BIPCLR(r11) to the switch_thread
> > > code:
> > >
> > > C_ENTRY(switch_thread):
> > >

___________________________
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/