From: "Göran Runfeldt" <goran@wasadata.se>
To: lartc@vger.kernel.org
Subject: SV: [LARTC] 2.4.20 htb3 oops
Date: Tue, 11 Mar 2003 08:52:03 +0000 [thread overview]
Message-ID: <marc-lartc-104737297230820@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104677871700498@msgid-missing>
>
> Any solution to the problems describe above? Im currently looking into
> building a new kernel 2.4.20 with HTB compiled as module in a
> production enviroment (2,5mbits average, 6-10mbits/peak). I wont use
> it if its broken though?
>
Unfortunately we have not yet come to a solution when it comes to our problems.
We have had the machines running for more than five days now, without any
HTB qdisc/classes loaded. This confirms that this is a problem with HTB.
I have activated the rules again in hope of getting a useful crash dump.
I do not know if anyone else has or will have this problem. All I know is
that we have the problem over here.
Göran
_______________________________________________
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-11 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 11:49 SV: [LARTC] 2.4.20 htb3 oops Göran Runfeldt
2003-03-10 20:20 ` Thomas Kirk
2003-03-11 8:52 ` Göran Runfeldt [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-104737297230820@msgid-missing \
--to=goran@wasadata.se \
--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.