On Mon, 16 Nov 1998, Olaf Meyer wrote:
> 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?
It means that the scheduler is somehow being invoked while interrupt processing
is taking place. For example, one way for this to happen would be for
some bottom-half code or interrupt-service code to call schedule(), directly or
indirectly. The scheduler inspects the intr_count global variable (the
interrupt nesting count) and emits the diagnostic, as an aid in debugging.
Of course, if you mess up intr_count, weird things can happen too; you can, for
instance, fool the system into thinking that it's in an interrupt when it's
not.
I would have to see the specific changes you made in order to say anything
more.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
