From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: dccp@vger.kernel.org
Subject: Re: Protocol not attached
Date: Fri, 03 Oct 2008 13:24:13 +0000 [thread overview]
Message-ID: <20081003132413.GG17843@ghostprotocols.net> (raw)
In-Reply-To: <5bc4c4570809291133k3f5841b1qde962bd3b4882439@mail.gmail.com>
Em Fri, Oct 03, 2008 at 02:44:43AM -0300, Leandro Sales escreveu:
> On Thu, Oct 2, 2008 at 1:47 AM, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
> > | Then, is it necessary to report this issue in the kernel dev maillist?
> > |
> > Before you do, can you check whether this issue is due to loading
> > modules on request. The DCCP protocol driver will return EUNATCH if it
> > is not able to load the compiled-in CCID modules.
> >
> > The way to test this is: unload all DCCP modules, start application
> > (with or without error), and then see which modules are loaded.
> >
> > If the compiled-in CCIDs have been loaded successfully from within DCCP
> > then the problem is somewhere else.
> >
>
> Hello Gerrit and others,
> we compiled 2.6.27-rc4 with DCCP as module in my testbed desktop.
>
> # modprobe -l
> /lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp_diag.ko
> /lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/ccids/lib/dccp_tfrc_lib.ko
> /lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/ccids/dccp_ccid2.ko
> /lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/ccids/dccp_ccid3.ko
> /lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp_ipv6.ko
> /lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp_ipv4.ko
> /lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp.ko
> /lib/modules/2.6.27-rc4-44301-g8269be1/kernel/net/dccp/dccp_probe.ko
>
> The module did not start in the boot (expected!). I then ran
>
> "strace -f -e trace=network iperf -s -d -l 1424 -i 1"
>
> and:
>
> # lsmod
> Module Size Used by
> dccp_tfrc_lib 17868 0
> dccp_ipv6 14916 2
> dccp_ipv4 14596 3 dccp_ipv6
> dccp 58176 2 dccp_ipv6,dccp_ipv4
>
> DCCP did not load the dccp_ccid2 module. Is this the problem?
>
> Just to let you know:
> # cat /proc/sys/net/dccp/default/rx_ccid /proc/sys/net/dccp/default/tx_ccid
> 2
> 2
>
> I then tested tested with 2.6.27-rc8, the same as with 2.6.27-rc4.
>
> So, what is your opinion?
Go ahead and load it manually, to check if the problem goes away when
dccp_ccid2 is loaded.
If it is, its narrowed down to the autoloading of CCID modules.
- Arnaldo
next prev parent reply other threads:[~2008-10-03 13:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 18:33 Protocol not attached Leandro Sales
2008-09-29 18:37 ` Arnaldo Carvalho de Melo
2008-09-30 18:32 ` Leandro Sales
2008-09-30 19:16 ` Arnaldo Carvalho de Melo
2008-09-30 21:24 ` Leandro Sales
2008-09-30 22:11 ` Arnaldo Carvalho de Melo
2008-10-01 18:27 ` Leandro Sales
2008-10-01 19:18 ` Leandro Sales
2008-10-01 19:37 ` Arnaldo Carvalho de Melo
2008-10-01 19:43 ` Leandro Sales
2008-10-01 21:38 ` Leandro Sales
2008-10-01 22:20 ` Ian McDonald
2008-10-02 4:47 ` Gerrit Renker
2008-10-03 5:44 ` Leandro Sales
2008-10-03 13:24 ` Arnaldo Carvalho de Melo [this message]
2008-10-03 14:18 ` Arnaldo Carvalho de Melo
2008-10-11 7:35 ` Gerrit Renker
2008-10-11 17:28 ` Leandro Sales
2008-10-13 14:51 ` Gerrit Renker
2008-10-16 21:09 ` Leandro Sales
2008-10-17 6:06 ` Gerrit Renker
2008-10-18 11:06 ` Gerrit Renker
2008-10-20 13:13 ` Arnaldo Carvalho de Melo
2008-10-21 14:19 ` Leandro Sales
2008-10-21 14:32 ` Arnaldo Carvalho de Melo
2008-10-21 18:08 ` Leandro Sales
2008-10-22 1:37 ` Leandro Sales
2008-10-22 1:37 ` Leandro Sales
2008-10-22 11:38 ` Arnaldo Carvalho de Melo
2008-10-22 13:30 ` Leandro Sales
2008-10-22 15:55 ` Gerrit Renker
2008-10-22 19:27 ` Leandro Sales
2008-10-23 5:18 ` gerrit
2008-11-06 13:38 ` Leandro Sales
2008-11-06 15:20 ` Gerrit Renker
2008-11-06 15:38 ` Arnaldo Carvalho de Melo
2008-11-06 17:46 ` Leandro Sales
2008-11-06 18:04 ` Leandro Sales
2008-11-06 18:17 ` Leandro Sales
2008-11-06 22:05 ` Leandro Sales
2008-11-08 8:50 ` Gerrit Renker
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=20081003132413.GG17843@ghostprotocols.net \
--to=acme@redhat.com \
--cc=dccp@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