From: Mihai RUSU <dizzy@roedu.net>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB flooding my kernel logs
Date: Tue, 21 Jan 2003 08:43:47 +0000 [thread overview]
Message-ID: <marc-lartc-104313862704874@msgid-missing> (raw)
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
f class 100610 is small. Consider r2q change.<4>HTB: quantum of class 100622 is
small. Consider r2q change.<4>HTB: quantum of class 100642 is small. Consider r2
q change.<4>HTB: quantum of class 10068B is small. Consider r2q change.<4>HTB: q
uantum of class 10068C is small. Consider r2q change.<4>HTB: quantum of class 10
0732 is small. Consider r2q change.<4>HTB: quantum of class 10070B is small. Con
sider r2q change.<4>HTB: quantum of class 10070C is small. Consider r2q change.<
4>HTB: quantum of class 10070D is small. Consider r2q change.<4>HTB: quantum of
class 1006A6 is small. Consider r2q change.<4>HTB: quantum of class 1006B1 is sm
all. Consider r2q change.<4>HTB: quantum of class 1006B2 is small. Consider r2q
change.<4>HTB: quantum of class 1006C3 is small. Consider r2q change.<4>HTB: qua
ntum of class 1006D5 is small. Consider r2q change.<4>HTB: quan
Jan 21 09:50:33 s kernel: of class 1006D6 is small. Consider r2q change.<4>HTB
: quantum of class 100725 is small. Consider r2q change.<4>HTB: quantum of class
10072A is small. Consider r2q change.<4>HTB: quantum of class 100737 is small.
Consider r2q change.<4>HTB: quantum of class 100738 is small. Consider r2q chang
e.<4>HTB: quantum of class 1011C8 is small. Consider r2q change.<4>HTB: quantum
of class 1011C9 is small. Consider r2q change.<4>HTB: quantum of class 1011CA is
small. Consider r2q change.<4>htb: class F00F10 isn't work conserving ?!
and so on...
What is wrong with the script ? Why doesnt HTB3 like it ?
Thanks
----------------------------
Mihai RUSU
Disclaimer: Any views or opinions presented within this e-mail are solely
those of the author and do not necessarily represent those of any company,
unless otherwise specifically stated.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-01-21 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 8:43 Mihai RUSU [this message]
2003-01-21 11:55 ` [LARTC] HTB flooding my kernel logs Catalin Bucur
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-104313862704874@msgid-missing \
--to=dizzy@roedu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox