Hello, I delete and recreate my root HTB qdiscs every minute as part of my rdd logging. From archive this seems to have come up a couple of times before although I dont see a resolution on the list, any advice on how I can find out what the problem is? Thanks I get the following errors logged: Jun 18 12:15:01 hostname kernel: HTB init, kernel part version 3.7 Jun 18 12:15:01 hostname kernel: KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) Jun 18 12:15:02 hostname last message repeated 14 times Jun 18 12:15:02 hostname kernel: HTB init, kernel part version 3.7 Jun 18 12:15:02 hostname kernel: KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) Jun 18 12:15:02 hostname last message repeated 15 times Jun 18 12:15:03 hostname kernel: HTB init, kernel part version 3.7 Jun 18 12:16:00 hostname kernel: HTB init, kernel part version 3.7 Jun 18 12:16:01 hostname last message repeated 3 times Jun 18 12:16:06 hostname kernel: KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) Jun 18 12:16:06 hostname kernel: htb: class 10029 isn''t work conserving ?! Jun 18 12:16:06 hostname kernel: KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) Jun 18 12:16:37 hostname last message repeated 433 times _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Wednesday 18 June 2003 13:29, David Watson wrote:> Hello, > I delete and recreate my root HTB qdiscs every minute as part of my rdd > logging.Why????? That''s not needed. Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Stef Coene wrote:> On Wednesday 18 June 2003 13:29, David Watson wrote: >> Ηello, >>I delete and recreate my root HTB qdiscs every minute as part of my rdd >>logging. > > Why????? That''s not needed.Never mind that. The most important issue here is that when you delete your queues, any packet that happens to pass through them at that time, are LOST! - Giannis Stoilis. _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Wednesday 18 June 2003 20:53, Giannis Stoilis wrote:> Stef Coene wrote: > > On Wednesday 18 June 2003 13:29, David Watson wrote: > >> Ηello, > >>I delete and recreate my root HTB qdiscs every minute as part of my rdd > >>logging. > > > > Why????? That''s not needed. > > Never mind that. The most important issue here is that when you delete > your queues, any packet that happens to pass through them at that time, > are LOST!Are you sure? I never tested it. Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Stef Coene wrote:> On Wednesday 18 June 2003 20:53, Giannis Stoilis wrote: >>Never mind that. The most important issue here is that when you delete >>your queues, any packet that happens to pass through them at that time, >>are LOST! > > Are you sure? I never tested it.This is how I know it: I constantly ping my linux server from another pc. At some poing I delete and recreate my queues. From the pc that pings my linux server, I can see the replies coming, and at the point of the restart I have missed pinging replies and at the point after the qdisc creation, I can see the icmp replies coming back again. Either every packet is lost at qdisc removal, or something else, same as nasty, is happening... You should try it and see... Also, if you have monitor_tc running at that time, you can see it dump some nice negative values... - Giannis _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Wednesday 18 June 2003 21:17, Giannis Stoilis wrote:> Stef Coene wrote: > > On Wednesday 18 June 2003 20:53, Giannis Stoilis wrote: > >>Never mind that. The most important issue here is that when you delete > >>your queues, any packet that happens to pass through them at that time, > >>are LOST! > > > > Are you sure? I never tested it. > > This is how I know it: > I constantly ping my linux server from another pc. At some poing I > delete and recreate my queues. From the pc that pings my linux server, I > can see the replies coming, and at the point of the restart I have > missed pinging replies and at the point after the qdisc creation, I can > see the icmp replies coming back again. > Either every packet is lost at qdisc removal, or something else, same as > nasty, is happening... > You should try it and see... > Also, if you have monitor_tc running at that time, you can see it dump > some nice negative values...:) That''s because the counters are resetten so the values are negative at that time. But that will not say are packets are gone. However, your ping test proves it. Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
I was recreating the qdiscs so that changes would be picked up automatically and not disturb the rrdtool generation, I''ve switched to a counter and cut out the resets. I did do a lot of ping tests and cannot replicate losing packets however. Thanks At 21:55 18/06/2003 +0200, you wrote:>On Wednesday 18 June 2003 21:17, Giannis Stoilis wrote: > > Stef Coene wrote: > > > On Wednesday 18 June 2003 20:53, Giannis Stoilis wrote: > > >>Never mind that. The most important issue here is that when you delete > > >>your queues, any packet that happens to pass through them at that time, > > >>are LOST! > > > > > > Are you sure? I never tested it. > > > > This is how I know it: > > I constantly ping my linux server from another pc. At some poing I > > delete and recreate my queues. From the pc that pings my linux server, I > > can see the replies coming, and at the point of the restart I have > > missed pinging replies and at the point after the qdisc creation, I can > > see the icmp replies coming back again. > > Either every packet is lost at qdisc removal, or something else, same as > > nasty, is happening... > > You should try it and see... > > Also, if you have monitor_tc running at that time, you can see it dump > > some nice negative values... >:) >That''s because the counters are resetten so the values are negative at that >time. But that will not say are packets are gone. However, your ping test >proves it. > >Stef > >-- > >stef.coene@docum.org > "Using Linux as bandwidth manager" > http://www.docum.org/ > #lartc @ irc.oftc.net > >_______________________________________________ >LARTC mailing list / LARTC@mailman.ds9a.nl >http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/_______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
David Watson wrote:> I did do a lot of ping tests and cannot replicate losing packets > however.Hmmm, let me get back to you on this. I will test it again on Monday... - Giannis _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Did someone solve this problem? I receive this error (on dmesg) when I launch my script for eth1: KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) Why ?????
you should provide more info, version, script .. On Thu, 3 Jul 2003 lartc@go.ro wrote:> Did someone solve this problem? > I receive this error (on dmesg) when I launch my script for eth1: > > KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) > > Why ?????_______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
<lartc@go.ro>
2003-Jul-03 10:44 UTC
Re: RE:RE:HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
OK No problem! I''m useing Slack 9.0/2.4.20( AMD K6 2-333Mhz with RAM 128MB) with HTB from kernel...and U32 filters! /* How can I tweak bash or something ...to get high histoy on Shift+PageUP and a higher bashhistory, too */ The dmesg paste: KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) eth0: Promiscuous mode enabled. device eth0 entered promiscuous mode eth1: Promiscuous mode enabled. device eth1 entered promiscuous mode tcpdump uses obsolete (PF_INET,SOCK_PACKET) eth0: Promiscuous mode enabled. device eth0 left promiscuous mode eth1: Promiscuous mode enabled. device eth1 left promiscuous mode htb*g j=1520405 htb*r7 m=0 htb*r6 m=0 htb*r5 m=0 htb*r4 m=0 htb*r3 m=0 htb*r2 m=0 htb*r1 m=0 htb*r0 m=0 htb*c10011 m=2 t=622399 c=622399 pq=0 df=761856 ql=0 pa=0 f: htb*c10231 m=2 t=178505 c=13040 pq=0 df=60000000 ql=0 pa=0 f: htb*c10246 m=2 t=180741 c=12740 pq=0 df=49152 ql=0 pa=0 f: htb*c10099 m=2 t=193067 c=13065 pq=0 df=4800512 ql=0 pa=0 f: htb*c10001 m=2 t=-4595 c=-4595 pq=0 df=8192 ql=0 pa=0 f: htb*c10230 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10247 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10222 m=2 t=17538 c=17538 pq=0 df=8192 ql=0 pa=0 f: htb*c10002 m=2 t=-9823 c=-14019 pq=0 df=8192 ql=0 pa=0 f: htb*c10233 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10244 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10102 m=2 t=184534 c=12840 pq=0 df=60000000 ql=0 pa=0 f: htb*c10232 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10254 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10105 m=2 t=183585 c=12815 pq=0 df=1204224 ql=0 pa=0 f: htb*c10235 m=2 t=185483 c=12866 pq=0 df=19382272 ql=0 pa=0 f: htb*c10242 m=2 t=192119 c=13040 pq=0 df=60000000 ql=0 pa=0 f: htb*c10253 m=2 t=178845 c=12690 pq=0 df=1187840 ql=0 pa=0 f: htb*c10027 m=2 t=59392 c=59392 pq=0 df=60000000 ql=0 pa=0 f: htb*c10115 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10234 m=2 t=192119 c=13040 pq=0 df=60000000 ql=0 pa=0 f: htb*c10243 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10666 m=2 t=4209 c=4209 pq=0 df=106496 ql=0 pa=0 f: htb*c10053 m=2 t=443199 c=443199 pq=0 df=6111232 ql=0 pa=0 f: htb*c10006 m=2 t=168099 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10116 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10226 m=2 t=192119 c=13040 pq=0 df=60000000 ql=0 pa=0 f: htb*c10237 m=2 t=-44811 c=10740 pq=0 df=8192 ql=0 pa=0 f: htb*c10240 m=2 t=178845 c=12690 pq=0 df=60000000 ql=0 pa=0 f: htb*c10106 m=2 t=192119 c=13040 pq=0 df=60000000 ql=0 pa=0 f: htb*c10227 m=2 t=192119 c=13040 pq=0 df=60000000 ql=0 pa=0 f: htb*c10236 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10241 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10250 m=2 t=-84557 c=8465 pq=0 df=8192 ql=0 pa=0 f: htb*c10228 m=2 t=-7675 c=2917 pq=0 df=8192 ql=0 pa=0 f: htb*c10239 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10229 m=2 t=-127349 c=8465 pq=0 df=8192 ql=0 pa=0 f: htb*c10238 m=2 t=197807 c=13189 pq=0 df=60000000 ql=0 pa=0 f: htb*c10192 m=2 t=178845 c=12690 pq=0 df=1187840 ql=0 pa=0 f: htb*c10248 m=2 t=186697 c=13040 pq=0 df=60000000 ql=0 pa=0 f: HTB init, kernel part version 3.7 htb*g j=1520407 htb*r7 m=0 htb*r6 m=0 htb*r5 m=0 htb*r4 m=0 htb*r3 m=0 htb*r2 m=0 htb*r1 m=0 htb*r0 m=0 My script for eth1 looks like this: #!/bin/sh TTRATE=2750kbit TRATE=2048kbit echo "delete!" tc qdisc del dev eth1 root 2>/dev/null >/dev/null echo "add qdisc..." tc qdisc add dev eth1 root handle 1: htb default 99 r2q 2 #atention!!! sum(child rate) <= parent rates !!!! echo "add classes..." tc class add dev eth1 parent 1: classid 1:1 htb rate $TTRATE ceil $TTRATE #clasa www facuta de PALI !!!!!!! tc class add dev eth1 parent 1: classid 1:666 htb rate 502kbit ceil 502kbit #ssh class pt conexiuni intre calc din retea si server tc class add dev eth1 parent 1: classid 1:222 htb rate 1024kbit ceil 1024kbit #Counter Strike tc class add dev eth1 parent 1: classid 1:27 htb rate 200Kbit ceil 200kbit #ICMP class tc class add dev eth1 parent 1: classid 1:11 htb rate 16kbit ceil 16kbit #DNS class tc class add dev eth1 parent 1: classid 1:53 htb rate 16kbit ceil 16kbit #rdc class tc class add dev eth1 parent 1:1 classid 1:6 htb rate 64Kbit ceil $TRATE prio 1 #other parent DOWN=1952 #640 tc class add dev eth1 parent 1:1 classid 1:2 htb rate $[DOWN]Kbit ceil $TRATE prio 3 #badboys classes N=32 #31 + 1(default) = 31(cu tot cu nerutabile) RATE=$[(9*$DOWN)/(10*$N)] echo "$[RATE]Kbit / class" tc class add dev eth1 parent 1:2 classid 1:102 htb rate $[RATE]Kbit ceil $TRATE prio 3 #192.168.10.2 tc class add dev eth1 parent 1:2 classid 1:105 htb rate $[RATE]Kbit ceil $TRATE prio 3 #192.168.10.5 tc class add dev eth1 parent 1:2 classid 1:106 htb rate $[RATE]Kbit ceil $TRATE prio 3 #192.168.10.6 tc class add dev eth1 parent 1:2 classid 1:115 htb rate $[RATE]Kbit ceil $TRATE prio 3 #192.168.11.5 tc class add dev eth1 parent 1:2 classid 1:116 htb rate $[RATE]Kbit ceil $TRATE prio 3 #192.168.11.6 tc class add dev eth1 parent 1:2 classid 1:192 htb rate $[RATE]Kbit ceil $TRATE prio 3 #192.168.10.3,4 192.168.11.2,3,4 neimportanti tc class add dev eth1 parent 1:2 classid 1:226 htb rate $[RATE]Kbit ceil $TRATE prio 3 #226 tc class add dev eth1 parent 1:2 classid 1:227 htb rate $[RATE]Kbit ceil $TRATE prio 3 #227 tc class add dev eth1 parent 1:2 classid 1:228 htb rate $[RATE]Kbit ceil $TRATE prio 3 #228 tc class add dev eth1 parent 1:2 classid 1:229 htb rate $[RATE]Kbit ceil $TRATE prio 3 #229 tc class add dev eth1 parent 1:2 classid 1:230 htb rate $[RATE]Kbit ceil $TRATE prio 3 #230 tc class add dev eth1 parent 1:2 classid 1:231 htb rate $[RATE]Kbit ceil $TRATE prio 3 #231 tc class add dev eth1 parent 1:2 classid 1:232 htb rate $[RATE]Kbit ceil $TRATE prio 3 #232 tc class add dev eth1 parent 1:2 classid 1:233 htb rate $[RATE]Kbit ceil $TRATE prio 3 #233 tc class add dev eth1 parent 1:2 classid 1:234 htb rate $[RATE]Kbit ceil $TRATE prio 3 #234 tc class add dev eth1 parent 1:2 classid 1:235 htb rate $[RATE]Kbit ceil $TRATE prio 3 #235 tc class add dev eth1 parent 1:2 classid 1:236 htb rate $[RATE]Kbit ceil $TRATE prio 3 #236 tc class add dev eth1 parent 1:2 classid 1:237 htb rate $[RATE]Kbit ceil $TRATE prio 3 #237 tc class add dev eth1 parent 1:2 classid 1:238 htb rate $[RATE]Kbit ceil $TRATE prio 3 #238 tc class add dev eth1 parent 1:2 classid 1:239 htb rate $[RATE]Kbit ceil $TRATE prio 3 #239 tc class add dev eth1 parent 1:2 classid 1:240 htb rate $[RATE]Kbit ceil $TRATE prio 3 #240 tc class add dev eth1 parent 1:2 classid 1:241 htb rate $[RATE]Kbit ceil $TRATE prio 3 #241 tc class add dev eth1 parent 1:2 classid 1:242 htb rate $[RATE]Kbit ceil $TRATE prio 3 #242 tc class add dev eth1 parent 1:2 classid 1:243 htb rate $[RATE]Kbit ceil $TRATE prio 3 #243 tc class add dev eth1 parent 1:2 classid 1:244 htb rate $[RATE]Kbit ceil $TRATE prio 3 #244 #tc class add dev eth1 parent 1:2 classid 1:245 htb rate $[RATE]Kbit ceil $TRATE prio 3 #245 !!! ip e luat, numai ca am bagat-o in clasa cu 236 --> vezi filtru tc class add dev eth1 parent 1:2 classid 1:246 htb rate $[RATE]Kbit ceil $TRATE prio 3 #246 tc class add dev eth1 parent 1:2 classid 1:247 htb rate $[RATE]Kbit ceil $TRATE prio 3 #247 tc class add dev eth1 parent 1:2 classid 1:248 htb rate $[RATE]Kbit ceil $TRATE prio 3 #248 #tc class add dev eth1 parent 1:2 classid 1:249 htb rate $[RATE]Kbit ceil $TRATE prio 3 #236 tc class add dev eth1 parent 1:2 classid 1:250 htb rate $[RATE]Kbit ceil $TRATE prio 3 #250 #tc class add dev eth1 parent 1:2 classid 1:251 htb rate $[RATE]Kbit ceil $TRATE prio 3 #250 vezi mai sus ....sunt in 250 vezi filtrele #tc class add dev eth1 parent 1:2 classid 1:252 htb rate $[RATE]Kbit ceil $TRATE prio 3 #250 tc class add dev eth1 parent 1:2 classid 1:253 htb rate $[RATE]Kbit ceil $TRATE prio 3 #253 tc class add dev eth1 parent 1:2 classid 1:254 htb rate $[RATE]Kbit ceil $TRATE prio 3 #254 #default class tc class add dev eth1 parent 1:2 classid 1:99 htb rate $[RATE]Kbit ceil $TRATE prio 3 #0 echo "add filters..." #icmp tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 \ match u8 0x01 0xff at 9 \ flowid 1:11 #DNS tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 \ match ip sport 53 0xff \ flowid 1:53 #WWW creata de PALI !!!!!!!!!!!!!! tc filter add dev eth1 parent 1:0 protocol ip prio 3 u32 match ip sport \ 80 0xffff flowid 1:666 #Counter Strike tc filter add dev eth1 parent 1:0 protocol ip prio 2 u32 match ip sport \ 27015 0xffff flowid 1:27 #rdc tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip dport \ 5901 0xffff flowid 1:6 tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip sport \ 5901 0xffff flowid 1:6 tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip sport \ 3389 0xffff flowid 1:6 tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip dport \ 3389 0xffff flowid 1:6 #ssh dinspre reta spre server tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip sport \ 22 0xffff flowid 1:222 #Clinets filters tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.10.2 flowid 1:102 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.10.3 flowid 1:192 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.10.4 flowid 1:192 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.10.5 flowid 1:105 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.10.6 flowid 1:106 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.11.2 flowid 1:192 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.11.3 flowid 1:192 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.11.4 flowid 1:192 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.11.5 flowid 1:115 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 192.168.11.6 flowid 1:116 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.226 flowid 1:226 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.227 flowid 1:227 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.228 flowid 1:228 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.229 flowid 1:229 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.230 flowid 1:230 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.231 flowid 1:231 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.232 flowid 1:232 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.233 flowid 1:233 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.234 flowid 1:234 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.235 flowid 1:235 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.236 flowid 1:236 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.237 flowid 1:237 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.238 flowid 1:238 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.239 flowid 1:239 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.240 flowid 1:240 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.241 flowid 1:241 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.242 flowid 1:242 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.243 flowid 1:243 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.244 flowid 1:244 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.245 flowid 1:236 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.246 flowid 1:246 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.247 flowid 1:247 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.248 flowid 1:248 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.249 flowid 1:236 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.250 flowid 1:250 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.251 flowid 1:250 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.252 flowid 1:250 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.253 flowid 1:253 tc filter add dev eth1 parent 1:0 protocol ip prio 4 u32 match ip dst \ 81.196.113.254 flowid 1:254 echo "add leaf qdisc..." #tc qdisc add dev eth1 parent 1:102 handle 102: sfq perturb 2 #tc qdisc add dev eth1 parent 1:105 handle 105: sfq perturb 2 #tc qdisc add dev eth1 parent 1:106 handle 106: sfq perturb 2 #tc qdisc add dev eth1 parent 1:115 handle 115: sfq perturb 2 #tc qdisc add dev eth1 parent 1:116 handle 116: sfq perturb 2 tc qdisc add dev eth1 parent 1:192 handle 192: sfq perturb 2 #tc qdisc add dev eth1 parent 1:226 handle 226: sfq perturb 2 #tc qdisc add dev eth1 parent 1:227 handle 227: sfq perturb 2 #tc qdisc add dev eth1 parent 1:228 handle 228: sfq perturb 2 #tc qdisc add dev eth1 parent 1:229 handle 229: sfq perturb 2 #tc qdisc add dev eth1 parent 1:230 handle 230: sfq perturb 2 #tc qdisc add dev eth1 parent 1:231 handle 231: sfq perturb 2 #tc qdisc add dev eth1 parent 1:232 handle 232: sfq perturb 2 #tc qdisc add dev eth1 parent 1:233 handle 233: sfq perturb 2 #tc qdisc add dev eth1 parent 1:234 handle 234: sfq perturb 2 #tc qdisc add dev eth1 parent 1:235 handle 235: sfq perturb 2 tc qdisc add dev eth1 parent 1:236 handle 236: sfq perturb 2 #tc qdisc add dev eth1 parent 1:237 handle 237: sfq perturb 2 #tc qdisc add dev eth1 parent 1:238 handle 238: sfq perturb 2 #tc qdisc add dev eth1 parent 1:239 handle 239: sfq perturb 2 #tc qdisc add dev eth1 parent 1:240 handle 240: sfq perturb 2 #tc qdisc add dev eth1 parent 1:241 handle 241: sfq perturb 2 #tc qdisc add dev eth1 parent 1:242 handle 242: sfq perturb 2 #tc qdisc add dev eth1 parent 1:243 handle 243: sfq perturb 2 #tc qdisc add dev eth1 parent 1:244 handle 244: sfq perturb 2 #tc qdisc add dev eth1 parent 1:245 handle 245: sfq perturb 2 #tc qdisc add dev eth1 parent 1:246 handle 246: sfq perturb 2 #tc qdisc add dev eth1 parent 1:247 handle 247: sfq perturb 2 #tc qdisc add dev eth1 parent 1:248 handle 248: sfq perturb 2 #tc qdisc add dev eth1 parent 1:249 handle 249: sfq perturb 2 tc qdisc add dev eth1 parent 1:250 handle 250: sfq perturb 2 #tc qdisc add dev eth1 parent 1:251 handle 251: sfq perturb 2 #tc qdisc add dev eth1 parent 1:252 handle 252: sfq perturb 2 #tc qdisc add dev eth1 parent 1:253 handle 253: sfq perturb 2 #tc qdisc add dev eth1 parent 1:254 handle 254: sfq perturb 2 tc qdisc add dev eth1 parent 1:666 handle 666: sfq perturb 2 tc qdisc add dev eth1 parent 1:99 handle 99: sfq perturb 2 ----- Original Message ----- From: "Martin Devera" <devik@cdi.cz> To: <lartc@go.ro> Cc: <lartc@mailman.ds9a.nl> Sent: 03 July, 2003 13:30 PM Subject: RE:RE:[LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)> you should provide more info, version, script .. > > On Thu, 3 Jul 2003 lartc@go.ro wrote: > > > Did someone solve this problem? > > I receive this error (on dmesg) when I launch my script for eth1: > > > > KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) > > > > Why ????? >_______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Martin Devera
2003-Jul-03 11:02 UTC
Re: RE:RE:HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
Ok, try please 2.4.21. Also can you trigger the bug often or only sometimes ? Does it depend on traffic ? I''m looking how to reproduce it here .. On Thu, 3 Jul 2003 lartc@go.ro wrote:> OK No problem! > I''m useing Slack 9.0/2.4.20( AMD K6 2-333Mhz with RAM 128MB) with HTB from > kernel...and U32 filters! > /* How can I tweak bash or something ...to get high histoy on Shift+PageUP > and a higher bashhistory, too */ > The dmesg paste: > KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) > KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) > KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) > KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) > KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) > KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959) > eth0: Promiscuous mode enabled._______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
<lartc@go.ro>
2003-Jul-03 11:14 UTC
Re: RE:RE:HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
yes I think it depends on traffic... but why this? PS 1) http://qos.dyndns.org:3389/cgi-bin/fom?file=40 what should I use on my K6 ??? default it''s PSCHED_JIFFIES, i think!! 2) http://qos.dyndns.org:3389/cgi-bin/fom?file=56 those filter destroy patches are applyed in 2.4.21 ?? 3) http://qos.dyndns.org:3389/cgi-bin/fom?file=21 What SFQ latency should I use? SFQ qdisc has a default queue length of 128 packets!!!! Or shuld I use ESFQ... Please advise me with this problems!! Thank you> Ok, try please 2.4.21. Also can you trigger the bug > often or only sometimes ? Does it depend on traffic ? > I''m looking how to reproduce it here .._______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Thursday 03 July 2003 13:14, lartc@go.ro wrote:> yes I think it depends on traffic... > but why this? > PS > 1) http://qos.dyndns.org:3389/cgi-bin/fom?file=40 what should I use on my > K6 ??? default it''s PSCHED_JIFFIES, i think!!I''m not sure but if you do cat /proc/cpuinfo, do you seetsc in the flags? I think that means your cpu has a timestamp counter.> 2) http://qos.dyndns.org:3389/cgi-bin/fom?file=56 those filter destroy > patches are applyed in 2.4.21 ??Yes.> 3) http://qos.dyndns.org:3389/cgi-bin/fom?file=21 What SFQ latency should I > use? > SFQ qdisc has a default queue length of 128 packets!!!!Try the default sfq and see if that''s enough. If not, you can try to change the queue depth. Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On kernel 2.4.18 through 20 I could reproduce this by deleting my root qdiscs and re-creating them every minute. I have since moved over to a different way of counting the packets so I no longer do this and the messages stopped. At 13:02 03/07/2003 +0200, you wrote:>Ok, try please 2.4.21. Also can you trigger the bug >often or only sometimes ? Does it depend on traffic ? >I''m looking how to reproduce it here .._______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
<lartc@go.ro>
2003-Jul-03 13:35 UTC
Re: RE:RE:HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
I don''t understand what u meen!Can you explain more detailed please!I''m from ROMANIA and my english it''s a little poor! What should I understand from this phrase "I have since moved over to a different way of counting the packets so I no longer do this and the messages stopped." Thanx ----- Original Message ----- From: "David Watson" <David.Watson@team17.com> To: <lartc@mailman.ds9a.nl> Sent: 03 July, 2003 15:48 PM Subject: Re: RE:RE:[LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)> > On kernel 2.4.18 through 20 I could reproduce this by deleting my root > qdiscs and re-creating them every minute. I have since moved over to a > different way of counting the packets so I no longer do this and the > messages stopped. > > At 13:02 03/07/2003 +0200, you wrote: > >Ok, try please 2.4.21. Also can you trigger the bug > >often or only sometimes ? Does it depend on traffic ? > >I''m looking how to reproduce it here .. > > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/_______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/