[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] kernel BUG at sched.c:687!
Hi,
I saw the same thing happening again in our custom board after running
for few hours and i could reproduce it in the xilinx-ml403 eval board.
Can i check any more kernel datastructure to debug this. Any
suggestion on debugging this will be really helpful.
Thnx
- Prasad
On 4/25/06, DeviPrasad Natesan <ndprasad@xxxxxxxxx> wrote:
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
___________________________
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/