All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC traffic loss bug, kernel 2.6.16.24
Date: Wed, 13 Sep 2006 16:38:16 +0000	[thread overview]
Message-ID: <450833F8.30008@trash.net> (raw)
In-Reply-To: <20060910152735.81EB3405C@outpost.ds9a.nl>

Leo Wetz wrote:
> Hello,
> 
> I have finally managed to understand HFSC up to a level which allowed me to
> create a QoS script which maintains low VoIP latency while running stuff
> like eMule.
> 
> Unfortunately, HFSC seems to have a severe bug.
> Why do I consider this as a bug defenitely?
> Well, my script runs without any errors, then QoS works perfectly for some
> hours, no error messages in kernel log.
> Then randomly the kernel starts saying this:
> 
> Sep 10 17:14:51 router kernel: HFSC: Non-work-conserving qdisc ?
> Sep 10 17:14:56 router kernel: printk: 266 messages suppressed.
> Sep 10 17:14:56 router kernel: HFSC: Non-work-conserving qdisc ?
> Sep 10 17:15:01 router kernel: printk: 259 messages suppressed.
> Sep 10 17:15:01 router kernel: HFSC: Non-work-conserving qdisc ?
> Sep 10 17:15:06 router kernel: printk: 294 messages suppressed.
> Sep 10 17:15:06 router kernel: HFSC: Non-work-conserving qdisc ?
> 
> It floods the whole kernel log with this.
> Traffic is also heavily affected by package loss when this happens, thus I
> cannot ignore it.
> I have to check my kernel log when I notice that I cannot access websites
> anymore and then restart QoS manually.
> 
> My complete QoS script is attached to this mail.
> If this is not the right location for the bug report please tell me whom I
> should contact.

This is not a bug. You can't attach non-work-conserving qdiscs to
HFSC (and it doesn't make any sense). Just use classes instead
of adding HTB qdiscs.


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2006-09-13 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10 15:28 [LARTC] HFSC traffic loss bug, kernel 2.6.16.24 Leo Wetz
2006-09-13 16:38 ` Patrick McHardy [this message]
2006-09-14 11:52 ` Re : " gerald HUET
2006-09-15  4:50 ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=450833F8.30008@trash.net \
    --to=kaber@trash.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.