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

["DeviPrasad Natesan" <ndprasad@xxxxxxxxx>]

Thanx for the response.  Any idea how (or what) to check the kernel
parameter when i get a bug like this and the system hangs..!!!.

(I typically began getting this when i configured another uart to
receive packets from the external thirdparty board with around 100
bytes per second as the through put (100 rx interrupts/sec). Although
i cannot really say the problem is due to that).

Thanx
- Prasad

On 4/19/06, Brettschneider Falk <fbrettschneider@xxxxxxxxxxxxxxxxx> wrote:
> Hi,
>
> DeviPrasad Natesan wrote:
> >
> > What typically causes this "kernel BUG at sched.c:562".
> The code is: BUG_ON(!current->active_mm);
> I think the scheduler has an inconsistent state here already. Hard to say
> why but I think, corrupted memory in 'current' could be the most likely
> reason. Maybe task switching doesn't save/restore some data properly
> (although it seems so), anyway I suppose the scheduler is one of the first
> things that is called after a task switch.
>
> Cheers, F@lk
> ___________________________
> 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/