> Thanks for your answers. Indeed after digging more into documentation (the
> docum.org one is great) we got more less logs. But our logs werent flooded
> with "quantum" related messages but with that kernel assertion thing. If
> nobody cant help me here Ill try to contact Mr Martin Devera directly.
So the quantum errors are gone?
> In fact we dont keep at a time more than 1 tree. So I have qdisc htb 1:
> and qdisc htb 10: or 20: at a time. When I want to reinitilize my htb
> trees I create the other tree from the new data (the trees are created db
> based) but if the current tree is 10: I create the new one 20: . Then
> after the new tree creation completes I do a tc filter change to classify
> packets onto the new tree and then a tc qdisc del the old tree (for
> example 10:). I observed that if between tc filter change (making new
> packets classify into the new tree) and tc qdisc del (deleting the old
> tree) I put a delay smaller than a certain ammount (here is 2 seconds)
> then I get those kernel assertion messages. And I dont get them only for a
> finite ammount of time, but I get them continously flooding my logs. If I
> reinitilize the htb tree again but having a bigger delay then I dont get
> any of that messages.
>
> Help ? :)
A htb qdisc attached to a htb class is useless and will only eat cpu cycles.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
