From: devik <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB 3.5 and some error explanations
Date: Tue, 21 May 2002 19:46:05 +0000 [thread overview]
Message-ID: <marc-lartc-102201051329810@msgid-missing> (raw)
Hi,
I fixed a few bugs and changed bug reporting so that it is
more valuable for me.
Regarding some "popular" bugs:
- HTB: bad diff in charge ....
it means that when comparing current time with time of last
class check we have got weird time difference (negative, too
big ...). There is bug in all 2.2, 2.4 kernels regarding this.
Part of HTB3.4 and 3.5 is fix for this one.
If you get the error and use these new patches, let me know.
- assertion failed: delay > 0 && delay < 5000000
- HTB: suspicious delay in wait_tree ...
some class wanted to add itself to waitlist and specified suspicious
delay to wait. I'm not sure why yet. In 3.5 I changed reporting of
it to include value of the delay and other info which could allow
me to locate the error.
3.5 version is at usual place http://luxik.cdi.cz/~devik/qos/htb/
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-05-21 19:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102201051329810@msgid-missing \
--to=devik@cdi.cz \
--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.