From: Thomas Graf <tgraf@suug.ch>
To: alchemyx@uznam.net.pl
Cc: netdev@oss.sgi.com, Andrew Morton <akpm@osdl.org>
Subject: Re: Fw: [Bugme-new] [Bug 3747] New: HTB causes machine lockups
Date: Tue, 16 Nov 2004 00:38:06 +0100 [thread overview]
Message-ID: <20041115233806.GC31969@postel.suug.ch> (raw)
In-Reply-To: <20041115122059.4cfcd213.akpm@osdl.org>
> Date: Mon, 15 Nov 2004 04:46:38 -0800
> From: bugme-daemon@osdl.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 3747] New: HTB causes machine lockups
>
> I have some network traffic shaping rules used on a Linux box. For example I
> have hundreds of them on eth1. I am using HTB in all cases (sometimes attaching
> SFQ to HTB rules). Everything works fine, until I issue:
>
> tc qdisc del dev eth1 root
>
> Which causes a machine lockup. Sometimes it happens day after day, but sometimes
> once a month. There are no traces in logs, no oopses, and so on. Machine just
> freezes (you see login on your screen, but can't type anything, can't ping that
> machine, ctrl-alt-del or sysrq doesn't work). Problem was on kernels from 2.4.21
> up to 2.4.26. Haven't tried 2.4.27 and 2.6.x on that box yet.
>
> Steps to reproduce:
> Hard to tell really. You need to set up a script creating hunderds of HTB rules
> and regenerating them every (let say) 15 minutes, issuing 'tc qdisc del dev
> ethX' everytime.
Did you ever experience the same problems with other classful qdiscs such as
CBQ? Would it be possible for you to run a similar CBQ setup on a dummy device
and see if it happens as well? Is anything going on at the time of the
deadlocks like an interface going down etc.?
next prev parent reply other threads:[~2004-11-15 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:20 Fw: [Bugme-new] [Bug 3747] New: HTB causes machine lockups Andrew Morton
2004-11-15 23:38 ` Thomas Graf [this message]
2004-11-22 18:10 ` Michał Margula
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=20041115233806.GC31969@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=akpm@osdl.org \
--cc=alchemyx@uznam.net.pl \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).