Messages in this thread | | | Date | Wed, 12 Jun 2002 22:38:37 -0700 | From | "Anjali Kulkarni" <> | Subject | Re: scheduler problems |
| |
> > > > [...] It is due to the fact that the schedule() function does not > > find > > > > the 'current' process in the runqueue. [...] > > > > > > a crash in line 384 means that the runqueue got corrupted by > > something, > > > most likely caused by buggy kernel code outside of the scheduler. > > > > Right, I thought of that, but how is it that it gets corrupt at exactly > > the same offset in task_struct of that process and every time with > > different processes? (I have run it atleast 20-30 times). And it just > > doesnt come if I kill the process in question? > > I've had similar problems when some code invalidated CPU cache > and an interrupt came in at the wrong time. >
Hi!
I have not very clear on what u mean. Can u explain in more detail?
Thanks, Anjali
> Richard > >
Anjali Kulkarni Software Engineer Indra Networks
~Living Well is the best Revenge~ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |