From: George Nychis <gnychis@cmu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to debug RTNETLINK invalid argument?
Date: Wed, 24 May 2006 01:04:24 +0000 [thread overview]
Message-ID: <4473B118.3070405@cmu.edu> (raw)
In-Reply-To: <44733597.4000208@cmu.edu>
Larry Brigman wrote:
> On 5/23/06, George Nychis <gnychis@cmu.edu> wrote:
>> Larry Brigman wrote:
>> > On 5/23/06, George Nychis <gnychis@cmu.edu> wrote:
>> >> Larry Brigman wrote:
>> >> > On 5/23/06, George Nychis <gnychis@cmu.edu> wrote:
>> >> >> Hey,
>> >> >>
>> >> >> I am getting an invalid argument trying to insert a qdisc:
>> >> >>
>> >> >> [root@emu-5 iproute2]# tc qdisc add dev eth0 root xcp capacity
>> 50Mbit
>> >> >> limit 500
>> >> >> RTNETLINK answers: Invalid argument
>> >> >>
>> >> >> I'm not sure whats wrong here, because i can successfully insert
>> this
>> >> >> qdisc on other computers of mine.
>> >> >>
>> >> >> How can i debug this?
>> >> >>
>> >> > Check to see which kernel versions you have on the boxes that
>> work and
>> >> > the one that
>> >> > does not. Also check to see if you have the latest version of
>> >> > iproute2 installed on the
>> >> > machine that does not work.
>> >> >
>> >>
>> >> They are both running the exact same kernel and version of iproute2,
>> >> however they are in different environments, what could the environment
>> >> have to do with it?
>> >>
>> > Modules that are not loaded? modprobe.conf?
>> > lsmod on both boxes looking for specific networking modules.
>> >
>>
>> What modules would qdisc's be dependent on? The weird thing is, netem
>> works on both machines... therefore I know qdisc's in general are
>> working. Lets just say its not working on my other machine, how do i go
>> about debugging it on the one machine alone?
>>
>
> Has the tc command been changed recently from your customized version back
> to the standard release (ie yum running via cron) or your environment
> path changed to
> pick up the wrong tc command?
>
the tc I am using is the standard tc, i didn't change anything about tc,
only trying to use a new custom qdisc with it... i'm not sure honestly,
theres no way to figure out why i'm getting the invalid argument?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-05-24 1:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 16:17 [LARTC] how to debug RTNETLINK invalid argument? George Nychis
2006-05-23 16:23 ` Larry Brigman
2006-05-23 17:12 ` George Nychis
2006-05-23 17:51 ` Larry Brigman
2006-05-23 23:29 ` George Nychis
2006-05-24 0:21 ` Larry Brigman
2006-05-24 1:04 ` George Nychis [this message]
2006-05-24 1:40 ` Stephen Hemminger
2006-05-24 2:12 ` Luciano Ruete
2006-05-24 14:14 ` George Nychis
2006-05-24 15:06 ` George Nychis
2006-05-24 15:24 ` George Nychis
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=4473B118.3070405@cmu.edu \
--to=gnychis@cmu.edu \
--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