From: Martin Volf <mv@inv.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2.4.20 htb3 oops
Date: Wed, 07 May 2003 18:31:54 +0000 [thread overview]
Message-ID: <marc-lartc-105233238820187@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104341174125310@msgid-missing>
On Tue, 6 May 2003 18:10:04 +0200
Kabelweb <office@kabelweb.at> wrote:
> I've also encountered machine-lockups once a day with stock 2.4.20 kernel and
> htb on SMP. I am using a setup with dynamically changing classes and have
> about 2-4mbit traffic. I was using 2.4.17, 2.4.18 and 2.4.19 with htb 3.6
> without problems before (other machine - not SMP though). Unfortunately I
> wasn't able to gather any debugging information on the crashes because
> getting the system up again was my primary concern. Since I have disabled all
> tc stuff on that machine it runs flawlessly (about a week now). I will soon
> try to reproduce the problem on another machine.
>
> Might the changes to htb in 2.4.21 be a solution? Is there any evidence that
> SMP might cause problems with htb?
>
> Any hints would be greatly appreciated!
Hello,
In 2.4.20 there is a bug in htb code, which was fixed in 2.4.21pre5 (or was it pre6?). You can use net/sched/sch_htb.c from 2.4.21rc1. For details see this thread in lkml:
http://marc.theaimsgroup.com/?l=linux-kernel&m\x105039488700308&w=2
--
Martin Volf
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-07 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 12:54 [LARTC] 2.4.20 htb3 oops Mihai RUSU
2003-01-24 14:29 ` Catalin Bucur
2003-01-25 21:51 ` Alexey Sheshka
2003-03-03 13:22 ` Göran Runfeldt
2003-03-03 13:39 ` Abraham van der Merwe
2003-03-03 14:53 ` Göran Runfeldt
2003-03-03 16:29 ` Abraham van der Merwe
2003-05-06 16:10 ` Kabelweb
2003-05-07 18:31 ` Martin Volf [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-105233238820187@msgid-missing \
--to=mv@inv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox