On Tue, 11 Jun 2002, Anjali Kulkarni wrote:
> I am getting a problem in the scheduler() function....
>
> I am running an in-kernel proxy on linux 2.2.16 and I get a problem in
> sched.c at line 384. [...]
(given that the current 2.2 kernel is 2.2.21, the first thing would be to
test it there too.)
> [...] 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.
> Can anyone tell me what's happening here? My kernel module is no way the
> cause of any of this. [...]
does it happen if you do not run your kernel module after bootup, ever?
Ingo
-
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/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:24 EST