Re: RE:RE:[LARTC] 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" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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 / [EMAIL PROTECTED] > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
On Thursday 03 July 2003 13:14, [EMAIL PROTECTED] 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 -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: RE:RE:[LARTC] 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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: RE:RE:[LARTC] 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 [EMAIL PROTECTED] 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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: RE:RE:[LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
urb 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" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] 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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
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 [EMAIL PROTECTED] 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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
RE:RE:[LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 ?
Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
[LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
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 / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/