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 know, that I'm not invoking the scheduler explicitly, so it must be done
somewhere implicitly. What functions could invoke the sceduler? Adding and
deleting timers in interrupts shouldn't be a problem. I know that the
functions associated with wait queues can. Are there any other?
Thanks,
Olaf
Olaf Meyer writes:
> Kaz,
>
> thanks for the debugging advice. Now that I'm not using X anymore
> I actually can see the reason for my freeze. I'm now
> just dropping the packets in the hard_xmit routine and freeing the
> skb's with dev_kfree_skb. After some while my system freezes with the
> console full of
>
> Aiee: scheduling in interrupt 00124b3
>
> log messages. What does this mean? Am I in some kind of infinite loop?
>
> Thanks,
>
> Olaf
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
