From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bad diff
Date: Sat, 22 Mar 2003 14:21:55 +0000 [thread overview]
Message-ID: <marc-lartc-104834303013608@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104830988431948@msgid-missing>
you should upgrade to 2.4.20. There was some problems with
TC API changes between 2.4.18-2.4.20.
The problem you see is with timer value overflow.
devik
On Sat, 22 Mar 2003, Damian Halloran wrote:
> Am having a problem with HTB. The following message is generated twice
> every 4 minutes in syslog.
>
> Mar 20 18:17:52 sale kernel: HTB: bad diff in events, cl\x10011
> diffñAB2000 now@54360064 thenB94803456 j\x115313989
>
> The HTB rules are generated by:
> /sbin/tc qdisc del dev wp1_fr16 root
> /sbin/tc qdisc add dev wp1_fr16 root handle 1: htb default 11
> /sbin/tc class add dev wp1_fr16 parent 1: classid 1:1 htb rate 60kbit
> ceil 60kbit burst 2k
> /sbin/tc class add dev wp1_fr16 parent 1:1 classid 1:10 htb rate 48kbit
> ceil 60kbit burst 2k prio 0
> /sbin/tc class add dev wp1_fr16 parent 1:1 classid 1:11 htb rate 12kbit
> ceil 60kbit burst 2k prio 1
> /sbin/tc qdisc add dev wp1_fr16 parent 1:10 handle 10: sfq perturb 10
> /sbin/tc qdisc add dev wp1_fr16 parent 1:11 handle 11: sfq perturb 10
> /sbin/tc filter add dev wp1_fr16 protocol ip parent 1:0 prio 0 u32
> match ip src 192.168.0.2 flowid 1:10
>
> The HTB version is 3.6, and kernel version 2.4.19 on RHLinux 7.2,
>
> All assistance is appreciated.
>
> Regards,
>
> Damian Halloran.
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-03-22 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 5:09 [LARTC] Bad diff Damian Halloran
2003-03-22 14:21 ` Martin Devera [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-104834303013608@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.