From: Andrew Morton <akpm@osdl•org>
To: netdev@oss•sgi.com
Subject: Fw: [Bugme-new] [Bug 3747] New: HTB causes machine lockups
Date: Mon, 15 Nov 2004 12:20:59 -0800 [thread overview]
Message-ID: <20041115122059.4cfcd213.akpm@osdl.org> (raw)
Begin forwarded message:
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
http://bugme.osdl.org/show_bug.cgi?id=3747
Summary: HTB causes machine lockups
Kernel Version: 2.4.26
Status: NEW
Severity: high
Owner: acme@conectiva•com.br
Submitter: alchemyx@uznam•net.pl
Distribution: PLD Linux 1.1 with 2.4.26 vanilla kernel
Hardware Environment: 2x Xeon 2.4 GHz, 1 GB of ram, 2x e1000 NICs
Software Environment: iproute2-2.4.7.ss020116
Problem Description:
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.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-11-15 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:20 Andrew Morton [this message]
2004-11-15 23:38 ` Fw: [Bugme-new] [Bug 3747] New: HTB causes machine lockups Thomas Graf
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=20041115122059.4cfcd213.akpm@osdl.org \
--to=akpm@osdl$(echo .)org \
--cc=netdev@oss$(echo .)sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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