From: Catalin Bucur <cata@geniusnet.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB flooding my kernel logs
Date: Tue, 21 Jan 2003 11:55:41 +0000 [thread overview]
Message-ID: <marc-lartc-104315019717285@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104313862704874@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mihai RUSU wrote:
| Hi
|
| I am trying to upgrade our systems with 2.4.20/HTB3 (before that I used
| 2.4.9 based kernel with HTB2 patch with no such problems). Since it booted
| the new kernel I get a lot of kernel messages that keeps klogd using CPU.
|
| Here is a sample:
|
| Jan 21 09:57:34 s kernel: KERNEL: assertion (cl &&
cl->un.leaf.q->q.qlen) failed at sch_htb.c(959)
| Jan 21 09:58:05 s last message repeated 447911 times
| Jan 21 09:59:06 s last message repeated 879964 times
| Jan 21 10:00:07 s last message repeated 901413 times
|
| I can comment out that assertion from sources but what exactly does that
| warning mean ? Should I silently ignore it or do I need to fix it ?
|
| Also when I run our htb configuration script I get a lot of this kind of
| messages:
|
| Jan 21 09:50:15 s kernel: uantum of class 10056B is small. Consider
r2q change
| .<4>HTB: quantum of class 100578 is small. Consider r2q change.<4>HTB:
quantum o
|
| and so on...
|
| What is wrong with the script ? Why doesnt HTB3 like it ?
These messages appear because of too small rates or ceils for that
classes (10:056B, 10:0578, ...). The implicit value for r2q is 10 and
because of this the quantum value is too small. "Consider r2q change"
it's a good ideea indeed ;-)
You can take a look at devik's faq page, maybe it can help:
http://luxik.cdi.cz/~devik/qos/htb/htbfaq.htm
I don't know if that assertion has the same reason, I haven't noticed
something like that in my logs.
- --
Catalin Bucur mailto:cata@geniusnet.ro
NOC @ Genius Network SRL - Galati - Romania
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE+LTU8pDe20wwI9oIRAo+HAJ90pY9n1oCHkxn4vT+JeTUtkr/3fwCffHlU
uBMA2jrV0D1+P5moftwTjbA=yiPG
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-21 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 8:43 [LARTC] HTB flooding my kernel logs Mihai RUSU
2003-01-21 11:55 ` Catalin Bucur [this message]
2003-01-21 16:40 ` Stef Coene
2003-01-22 9:46 ` Mihai RUSU
2003-01-22 11:43 ` Catalin BOIE
2003-01-22 17:14 ` Stef Coene
2003-01-22 23:58 ` Mihai RUSU
2003-01-23 18:50 ` Stef Coene
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-104315019717285@msgid-missing \
--to=cata@geniusnet.ro \
--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