From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb warning (error?)
Date: Sun, 27 Oct 2002 15:38:55 +0000 [thread overview]
Message-ID: <marc-lartc-103573316924244@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103572484819181@msgid-missing>
On Sunday 27 October 2002 14:19, Razvan Cosma wrote:
> I'm getting lots of this in the logs:
> kernel: HTB: mindelay=500, report it please !
> so - I'm reporting it :)
> I use htb3.6-020525, imq-2.4.18.diff-10.1, kernel 2.4.18, iptables
> v1.2.6a.
> What causes this message, and what other info would be useful for
> debugging?
It's a debug message so there is no real error.
But I don't know what it means. I think it means that htb is dequeing to
fast.
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/
prev parent reply other threads:[~2002-10-27 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 13:19 [LARTC] htb warning (error?) Razvan Cosma
2002-10-27 15:38 ` Stef Coene [this message]
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=marc-lartc-103573316924244@msgid-missing \
--to=stef.coene@docum.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox