On Mon, 16 Nov 1998, Olaf Meyer wrote:
> By scanning the scheduler code I found the place where the
> error message is produced. And it means what it says :-)
> The scheduler is being invoked from an interrupt and obviously
> that should not happen. I guess I have to resolve the address,
> to see who could do such a thing ...
I guess this might be caused by calling kmalloc or functions which call
kmalloc with wrong "priority" (not GFP_ATOMIC) what on turn can schedule
in low memory situations (to let other jobs free memory).
Correct me if I'm wrong :-)
Karlis
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
