From: Jaume Catarineu <jaume.catarineu@upf.edu>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: hadi@cyberus.ca, "David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com, Francois Romieu <romieu@fr.zoreil.com>
Subject: Kernel BUG: Qos seg. fault (part II)
Date: Tue, 25 May 2004 03:29:29 +0000 [thread overview]
Message-ID: <40B2BD99.4000500@upf.edu> (raw)
In-Reply-To: <1085436571.1041.69.camel@jzny.localdomain>
Hi again,
I've found another problem that seems strongly related to the first one.
In this case we just need a TBF root qdisc:
tc qdisc add dev lo root handle 1: tbf rate 250kbit burst 5k limit 5k
After adding it, when we ask for the filters...
tc filter show dev lo
Voilà!
Segmentation fault
Does the patch provided by Dmitry arrange this? And the Jamal's patch?
Which is better?
Thanks,
Jaume,
next prev parent reply other threads:[~2004-05-25 3:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 21:53 Kernel BUG: Qos seg. fault Dmitry Torokhov
2004-05-24 22:09 ` jamal
2004-05-25 2:06 ` Jaume Catarineu
2004-05-25 3:29 ` Jaume Catarineu [this message]
2004-05-25 2:08 ` Kernel BUG: Qos seg. fault (part II) jamal
2004-05-25 13:09 ` Jaume Catarineu
2004-05-25 7:07 ` Kernel BUG: Qos seg. fault Dmitry Torokhov
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=40B2BD99.4000500@upf.edu \
--to=jaume.catarineu@upf.edu \
--cc=davem@redhat.com \
--cc=dtor_core@ameritech.net \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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).