Protocol not attached

Protocol not attached

[Leandro Sales]

Hello folks,
  I'm getting this message while using 2.6.27:

  Can not create DCCP socket (Protocol driver not attached)

  "uname -a" output:
      Linux localhost 2.6.27-rc4-44301-g8269be1 #7 SMP Sun Sep 28 17:02:25
      BRT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux

  Anything wrong? I tried compile DCCP using both static and module
methods and it produces the same effect.

Thank you,
Leandro.

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Em Mon, Sep 29, 2008 at 03:33:44PM -0300, Leandro Sales escreveu:
> Hello folks,
>   I'm getting this message while using 2.6.27:
> 
>   Can not create DCCP socket (Protocol driver not attached)

What is the source of such messages? VLC? What? Try strace to see what
is the syscall that fails just before this message is printed, etc.
 
>   "uname -a" output:
>       Linux localhost 2.6.27-rc4-44301-g8269be1 #7 SMP Sun Sep 28 17:02:25
>       BRT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
> 
>   Anything wrong? I tried compile DCCP using both static and module
> methods and it produces the same effect.

- Arnaldo

Re: Protocol not attached

[Leandro Sales]

On Mon, Sep 29, 2008 at 3:37 PM, Arnaldo Carvalho de Melo
<acme@redhat.com> wrote:
> Em Mon, Sep 29, 2008 at 03:33:44PM -0300, Leandro Sales escreveu:
>> Hello folks,
>>   I'm getting this message while using 2.6.27:
>>
>>   Can not create DCCP socket (Protocol driver not attached)
>
> What is the source of such messages? VLC? What? Try strace to see what
> is the syscall that fails just before this message is printed, etc.
>
>>   "uname -a" output:
>>       Linux localhost 2.6.27-rc4-44301-g8269be1 #7 SMP Sun Sep 28 17:02:25
>>       BRT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
>>
>>   Anything wrong? I tried compile DCCP using both static and module
>> methods and it produces the same effect.
>
> - Arnaldo
>

Hello Arnaldo,
  I'm just running tests with iperf to later use gstreamer plugin that
I developed. Here it is the output provided by strace while executing
iperf. I'm sorry for the long message. In addition, I'm providing
support for a guy from China that wants to use my gstreamer plugin and
he is facing similar problem, getting a permission denied message
while using the plugin, even then he run the plugin as root.

execve("/usr/local/bin/iperf", ["iperf", "-s", "-d", "-l", "1424",
"-i", "1"], [/* 32 vars */]) = 0
brk(0)                                  = 0x8057000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_sizey675, ...}) = 0
mmap2(NULL, 79675, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fce000
close(3)                                = 0
open("/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\30\4\0004\0\0\0"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_sizeí5472, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7fcd000
mmap2(NULL, 951972, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb7ee4000
mmap2(0xb7fc2000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xdd) = 0xb7fc2000
mmap2(0xb7fc7000, 22180, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7fc7000
close(3)                                = 0
open("/lib/libm.so.6", O_RDONLY)        = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p4\0\0004\0\0\0"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size\x149256, ...}) = 0
mmap2(NULL, 151680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb7ebe000
mmap2(0xb7ee2000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x23) = 0xb7ee2000
close(3)                                = 0
open("/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\30\0\0004\0\0\0"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_sizeB348, ...}) = 0
mmap2(NULL, 45508, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb7eb2000
mmap2(0xb7ebc000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x9) = 0xb7ebc000
close(3)                                = 0
open("/lib/libpthread.so.0", O_RDONLY)  = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0
H\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size\x118677, ...}) = 0
mmap2(NULL, 90592, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb7e9b000
mmap2(0xb7eae000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13) = 0xb7eae000
mmap2(0xb7eb0000, 4576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7eb0000
close(3)                                = 0
open("/lib/libc.so.6", O_RDONLY)        = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@a\1\0004\0\0\0"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size\x1237276, ...}) = 0
mmap2(NULL, 1242576, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE,
3, 0) = 0xb7d6b000
mmap2(0xb7e95000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12a) = 0xb7e95000
mmap2(0xb7e98000, 9680, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7e98000
close(3)                                = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7d6a000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7d69000
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7d696d0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = 0
mprotect(0xb7e95000, 8192, PROT_READ)   = 0
mprotect(0xb7eae000, 4096, PROT_READ)   = 0
mprotect(0xb7ebc000, 4096, PROT_READ)   = 0
mprotect(0xb7ee2000, 4096, PROT_READ)   = 0
mprotect(0xb7fc2000, 16384, PROT_READ)  = 0
mprotect(0x8055000, 4096, PROT_READ)    = 0
mprotect(0xb7ffc000, 4096, PROT_READ)   = 0
munmap(0xb7fce000, 79675)               = 0
set_tid_address(0xb7d69718)             = 11228
set_robust_list(0xb7d69720, 0xc)        = 0
rt_sigaction(SIGRTMIN, {0xb7e9f320, [], SA_SIGINFO}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0xb7e9f3a0, [], SA_RESTART|SA_SIGINFO}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
getrlimit(RLIMIT_STACK, {rlim_curÅ92*1024, rlim_max=RLIM_INFINITY}) = 0
uname({sys="Linux", node="localhost", ...}) = 0
futex(0xb7fc84fc, FUTEX_WAKE, 2147483647) = 0
rt_sigaction(SIGTERM, {0x80509e0, [], SA_RESTART}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {0x80509e0, [], SA_RESTART}, {SIG_DFL}, 8) = 0
brk(0)                                  = 0x8057000
brk(0x8078000)                          = 0x8078000
mmap2(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb7568000
mprotect(0xb7568000, 4096, PROT_NONE)   = 0
clone(child_stack=0xb7d684a4,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0xb7d68bd8, {entry_number:6, base_addr:0xb7d68b90,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1},
child_tidptr=0xb7d68bd8) = 11229
mmap2(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb6d67000
mprotect(0xb6d67000, 4096, PROT_NONE)   = 0
clone(child_stack=0xb75674a4,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0xb7567bd8, {entry_number:6, base_addr:0xb7567b90,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1},
child_tidptr=0xb7567bd8) = 11234
futex(0x8056364, FUTEX_WAIT, 1, NULL)   = 0
futex(0x8056390, FUTEX_WAKE, 1)         = 0
futex(0x8056364, FUTEX_WAIT, 3, NULLCan not create DCCP socket
(Protocol driver not attached)
 <unfinished ... exit status 1>

Thanks,
Leandro.
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Em Tue, Sep 30, 2008 at 03:32:17PM -0300, Leandro Sales escreveu:
> On Mon, Sep 29, 2008 at 3:37 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
> > Em Mon, Sep 29, 2008 at 03:33:44PM -0300, Leandro Sales escreveu:
> >> Hello folks,
> >>   I'm getting this message while using 2.6.27:
> >>
> >>   Can not create DCCP socket (Protocol driver not attached)
> >
> > What is the source of such messages? VLC? What? Try strace to see what
> > is the syscall that fails just before this message is printed, etc.
> >
> >>   "uname -a" output:
> >>       Linux localhost 2.6.27-rc4-44301-g8269be1 #7 SMP Sun Sep 28 17:02:25
> >>       BRT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
> >>
> >>   Anything wrong? I tried compile DCCP using both static and module
> >> methods and it produces the same effect.
> >
> > - Arnaldo
> >
> 
> Hello Arnaldo,
>   I'm just running tests with iperf to later use gstreamer plugin that
> I developed. Here it is the output provided by strace while executing
> iperf. I'm sorry for the long message. In addition, I'm providing
> support for a guy from China that wants to use my gstreamer plugin and
> he is facing similar problem, getting a permission denied message
> while using the plugin, even then he run the plugin as root.

iperf is multithreaded, so you need to run strace with -f to trace child
processes, also please try limiting the output to just the networking
syscalls:

strace -f -e trace=network iperf

"net namespaces" blipped in my mind, but it may well be just my brain
needing more coffee...

- Arnaldo

Re: Protocol not attached

[Leandro Sales]

On Tue, Sep 30, 2008 at 4:16 PM, Arnaldo Carvalho de Melo
<acme@redhat.com> wrote:
> Em Tue, Sep 30, 2008 at 03:32:17PM -0300, Leandro Sales escreveu:
>> On Mon, Sep 29, 2008 at 3:37 PM, Arnaldo Carvalho de Melo
>> <acme@redhat.com> wrote:
>> > Em Mon, Sep 29, 2008 at 03:33:44PM -0300, Leandro Sales escreveu:
>> >> Hello folks,
>> >>   I'm getting this message while using 2.6.27:
>> >>
>> >>   Can not create DCCP socket (Protocol driver not attached)
>> >
>> > What is the source of such messages? VLC? What? Try strace to see what
>> > is the syscall that fails just before this message is printed, etc.
>> >
>> >>   "uname -a" output:
>> >>       Linux localhost 2.6.27-rc4-44301-g8269be1 #7 SMP Sun Sep 28 17:02:25
>> >>       BRT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
>> >>
>> >>   Anything wrong? I tried compile DCCP using both static and module
>> >> methods and it produces the same effect.
>> >
>> > - Arnaldo
>> >
>>
>> Hello Arnaldo,
>>   I'm just running tests with iperf to later use gstreamer plugin that
>> I developed. Here it is the output provided by strace while executing
>> iperf. I'm sorry for the long message. In addition, I'm providing
>> support for a guy from China that wants to use my gstreamer plugin and
>> he is facing similar problem, getting a permission denied message
>> while using the plugin, even then he run the plugin as root.
>
> iperf is multithreaded, so you need to run strace with -f to trace child
> processes, also please try limiting the output to just the networking
> syscalls:
>
> strace -f -e trace=network iperf
>
> "net namespaces" blipped in my mind, but it may well be just my brain
> needing more coffee...
>
> - Arnaldo
>

Arnaldo, thank you for the reply. Please, check the strace output
below. I'm not sure what it happen, although I have a thought. Any
clue?

Process 5849 attached (waiting for parent)
Process 5849 resumed (parent 5848 ready)
[pid  5849] socket(PF_NETLINK, SOCK_RAW, 0) = 3
[pid  5849] bind(3, {sa_family¯_NETLINK, pid=0, groups\0000000}, 12) = 0
[pid  5849] getsockname(3, {sa_family¯_NETLINK, pidX48,
groups\0000000}, [12]) = 0
[pid  5849] sendto(3, "\24\0\0\0\26\0\1\3&\230\342H\0\0\0\0\0\0\0\0",
20, 0, {sa_family¯_NETLINK, pid=0, groups\0000000}, 12) = 20
[pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
groups\0000000},
msg_iov(1)=[{"8\0\0\0\24\0\2\0&\230\342H\330\26\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 116
[pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
groups\0000000},
msg_iov(1)=[{"@\0\0\0\24\0\2\0&\230\342H\330\26\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 128
[pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
groups\0000000},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0&\230\342H\330\26\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
[pid  5849] socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3
[pid  5849] connect(3, {sa_family¯_INET6, sin6_port=htons(5001),
inet_pton(AF_INET6, "::", &sin6_addr), sin6_flowinfo=0,
sin6_scope_id=0}, 28) = 0
[pid  5849] getsockname(3, {sa_family¯_INET6,
sin6_port=htons(56372), inet_pton(AF_INET6, "::1", &sin6_addr),
sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
[pid  5849] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
[pid  5849] connect(3, {sa_family¯_INET, sin_port=htons(5001),
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
[pid  5849] getsockname(3, {sa_family¯_INET, sin_port=htons(37587),
sin_addr=inet_addr("127.0.0.1")}, [16]) = 0
[pid  5849] socket(PF_INET6, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/) = -1 EUNATCH (Protocol driver not attached)
[pid  5849] socket(PF_INET6, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/Process 5854 attached
) = -1 EUNATCH (Protocol driver not attached)
[pid  5849] socket(PF_INET6, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/) = -1 EUNATCH (Protocol driver not attached)
[pid  5849] socket(PF_INET, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/) = -1 EUNATCH (Protocol driver not attached)
[pid  5849] socket(PF_INET, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/) = -1 EUNATCH (Protocol driver not attached)
[pid  5849] socket(PF_INET, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/) = -1 EUNATCH (Protocol driver not attached)
Can not create DCCP socket (Protocol driver not attached)

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Em Tue, Sep 30, 2008 at 06:24:57PM -0300, Leandro Sales escreveu:
> On Tue, Sep 30, 2008 at 4:16 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
> > Em Tue, Sep 30, 2008 at 03:32:17PM -0300, Leandro Sales escreveu:
> >> On Mon, Sep 29, 2008 at 3:37 PM, Arnaldo Carvalho de Melo
> >> <acme@redhat.com> wrote:
> >> > Em Mon, Sep 29, 2008 at 03:33:44PM -0300, Leandro Sales escreveu:
> >> >> Hello folks,
> >> >>   I'm getting this message while using 2.6.27:
> >> >>
> >> >>   Can not create DCCP socket (Protocol driver not attached)
> >> >
> >> > What is the source of such messages? VLC? What? Try strace to see what
> >> > is the syscall that fails just before this message is printed, etc.
> >> >
> >> >>   "uname -a" output:
> >> >>       Linux localhost 2.6.27-rc4-44301-g8269be1 #7 SMP Sun Sep 28 17:02:25
> >> >>       BRT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
> >> >>
> >> >>   Anything wrong? I tried compile DCCP using both static and module
> >> >> methods and it produces the same effect.
> >> >
> >> > - Arnaldo
> >> >
> >>
> >> Hello Arnaldo,
> >>   I'm just running tests with iperf to later use gstreamer plugin that
> >> I developed. Here it is the output provided by strace while executing
> >> iperf. I'm sorry for the long message. In addition, I'm providing
> >> support for a guy from China that wants to use my gstreamer plugin and
> >> he is facing similar problem, getting a permission denied message
> >> while using the plugin, even then he run the plugin as root.
> >
> > iperf is multithreaded, so you need to run strace with -f to trace child
> > processes, also please try limiting the output to just the networking
> > syscalls:
> >
> > strace -f -e trace=network iperf
> >
> > "net namespaces" blipped in my mind, but it may well be just my brain
> > needing more coffee...
> >
> > - Arnaldo
> >
> 
> Arnaldo, thank you for the reply. Please, check the strace output
> below. I'm not sure what it happen, although I have a thought. Any
> clue?
> 
> Process 5849 attached (waiting for parent)
> Process 5849 resumed (parent 5848 ready)
> [pid  5849] socket(PF_NETLINK, SOCK_RAW, 0) = 3
> [pid  5849] bind(3, {sa_family¯_NETLINK, pid=0, groups\0000000}, 12) = 0
> [pid  5849] getsockname(3, {sa_family¯_NETLINK, pidX48,
> groups\0000000}, [12]) = 0
> [pid  5849] sendto(3, "\24\0\0\0\26\0\1\3&\230\342H\0\0\0\0\0\0\0\0",
> 20, 0, {sa_family¯_NETLINK, pid=0, groups\0000000}, 12) = 20
> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
> groups\0000000},
> msg_iov(1)=[{"8\0\0\0\24\0\2\0&\230\342H\330\26\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"...,
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 116
> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
> groups\0000000},
> msg_iov(1)=[{"@\0\0\0\24\0\2\0&\230\342H\330\26\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"...,
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 128
> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
> groups\0000000},
> msg_iov(1)=[{"\24\0\0\0\3\0\2\0&\230\342H\330\26\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0"...,
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
> [pid  5849] socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3
> [pid  5849] connect(3, {sa_family¯_INET6, sin6_port=htons(5001),
> inet_pton(AF_INET6, "::", &sin6_addr), sin6_flowinfo=0,
> sin6_scope_id=0}, 28) = 0
> [pid  5849] getsockname(3, {sa_family¯_INET6,
> sin6_port=htons(56372), inet_pton(AF_INET6, "::1", &sin6_addr),
> sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
> [pid  5849] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
> [pid  5849] connect(3, {sa_family¯_INET, sin_port=htons(5001),
> sin_addr=inet_addr("0.0.0.0")}, 16) = 0
> [pid  5849] getsockname(3, {sa_family¯_INET, sin_port=htons(37587),
> sin_addr=inet_addr("127.0.0.1")}, [16]) = 0
> [pid  5849] socket(PF_INET6, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
> */) = -1 EUNATCH (Protocol driver not attached)


Here we gett the EUNATACH when trying SOCK_DCCP (6), IPPROTO_DCCP (33),
but I couldn't find any EUNATACH return in the sock_create path, do you
have selinux running?

It tries several times PF_INET6 then falls back to PF_INET. Is this
using glibc? dietlibc? ARM? lsmod output can also help.

- Arnaldo

Re: Protocol not attached

[Leandro Sales]

On Tue, Sep 30, 2008 at 7:11 PM, Arnaldo Carvalho de Melo
<acme@redhat.com> wrote:
> Em Tue, Sep 30, 2008 at 06:24:57PM -0300, Leandro Sales escreveu:
>> On Tue, Sep 30, 2008 at 4:16 PM, Arnaldo Carvalho de Melo
>> <acme@redhat.com> wrote:
>> > Em Tue, Sep 30, 2008 at 03:32:17PM -0300, Leandro Sales escreveu:
>> >> On Mon, Sep 29, 2008 at 3:37 PM, Arnaldo Carvalho de Melo
>> >> <acme@redhat.com> wrote:
>> >> > Em Mon, Sep 29, 2008 at 03:33:44PM -0300, Leandro Sales escreveu:
>> >> >> Hello folks,
>> >> >>   I'm getting this message while using 2.6.27:
>> >> >>
>> >> >>   Can not create DCCP socket (Protocol driver not attached)
>> >> >
>> >> > What is the source of such messages? VLC? What? Try strace to see what
>> >> > is the syscall that fails just before this message is printed, etc.
>> >> >
>> >> >>   "uname -a" output:
>> >> >>       Linux localhost 2.6.27-rc4-44301-g8269be1 #7 SMP Sun Sep 28 17:02:25
>> >> >>       BRT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
>> >> >>
>> >> >>   Anything wrong? I tried compile DCCP using both static and module
>> >> >> methods and it produces the same effect.
>> >> >
>> >> > - Arnaldo
>> >> >
>> >>
>> >> Hello Arnaldo,
>> >>   I'm just running tests with iperf to later use gstreamer plugin that
>> >> I developed. Here it is the output provided by strace while executing
>> >> iperf. I'm sorry for the long message. In addition, I'm providing
>> >> support for a guy from China that wants to use my gstreamer plugin and
>> >> he is facing similar problem, getting a permission denied message
>> >> while using the plugin, even then he run the plugin as root.
>> >
>> > iperf is multithreaded, so you need to run strace with -f to trace child
>> > processes, also please try limiting the output to just the networking
>> > syscalls:
>> >
>> > strace -f -e trace=network iperf
>> >
>> > "net namespaces" blipped in my mind, but it may well be just my brain
>> > needing more coffee...
>> >
>> > - Arnaldo
>> >
>>
>> Arnaldo, thank you for the reply. Please, check the strace output
>> below. I'm not sure what it happen, although I have a thought. Any
>> clue?
>>
>> Process 5849 attached (waiting for parent)
>> Process 5849 resumed (parent 5848 ready)
>> [pid  5849] socket(PF_NETLINK, SOCK_RAW, 0) = 3
>> [pid  5849] bind(3, {sa_family¯_NETLINK, pid=0, groups\0000000}, 12) = 0
>> [pid  5849] getsockname(3, {sa_family¯_NETLINK, pidX48,
>> groups\0000000}, [12]) = 0
>> [pid  5849] sendto(3, "\24\0\0\0\26\0\1\3&\230\342H\0\0\0\0\0\0\0\0",
>> 20, 0, {sa_family¯_NETLINK, pid=0, groups\0000000}, 12) = 20
>> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
>> groups\0000000},
>> msg_iov(1)=[{"8\0\0\0\24\0\2\0&\230\342H\330\26\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"...,
>> 4096}], msg_controllen=0, msg_flags=0}, 0) = 116
>> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
>> groups\0000000},
>> msg_iov(1)=[{"@\0\0\0\24\0\2\0&\230\342H\330\26\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"...,
>> 4096}], msg_controllen=0, msg_flags=0}, 0) = 128
>> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
>> groups\0000000},
>> msg_iov(1)=[{"\24\0\0\0\3\0\2\0&\230\342H\330\26\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0"...,
>> 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
>> [pid  5849] socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3
>> [pid  5849] connect(3, {sa_family¯_INET6, sin6_port=htons(5001),
>> inet_pton(AF_INET6, "::", &sin6_addr), sin6_flowinfo=0,
>> sin6_scope_id=0}, 28) = 0
>> [pid  5849] getsockname(3, {sa_family¯_INET6,
>> sin6_port=htons(56372), inet_pton(AF_INET6, "::1", &sin6_addr),
>> sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
>> [pid  5849] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
>> [pid  5849] connect(3, {sa_family¯_INET, sin_port=htons(5001),
>> sin_addr=inet_addr("0.0.0.0")}, 16) = 0
>> [pid  5849] getsockname(3, {sa_family¯_INET, sin_port=htons(37587),
>> sin_addr=inet_addr("127.0.0.1")}, [16]) = 0
>> [pid  5849] socket(PF_INET6, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
>> */) = -1 EUNATCH (Protocol driver not attached)
>
>
> Here we gett the EUNATACH when trying SOCK_DCCP (6), IPPROTO_DCCP (33),
> but I couldn't find any EUNATACH return in the sock_create path, do you
> have selinux running?
>
> It tries several times PF_INET6 then falls back to PF_INET. Is this
> using glibc? dietlibc? ARM? lsmod output can also help.
>
> - Arnaldo
>

Hello Arnaldo,

kernel version: 2.6.27-rc4 (from gerrit git three)

sys-libs/glibc version: 2.6.1

No selinux running.

In addition, this problem is occurring in both the desktop and on nokia n800.

Thank you,
Leandro.

Re: Protocol not attached

[Leandro Sales]

On Wed, Oct 1, 2008 at 3:27 PM, Leandro Sales <leandroal@gmail.com> wrote:
> On Tue, Sep 30, 2008 at 7:11 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
>> Em Tue, Sep 30, 2008 at 06:24:57PM -0300, Leandro Sales escreveu:
>>> On Tue, Sep 30, 2008 at 4:16 PM, Arnaldo Carvalho de Melo
>>> <acme@redhat.com> wrote:
>>> > Em Tue, Sep 30, 2008 at 03:32:17PM -0300, Leandro Sales escreveu:
>>> >> On Mon, Sep 29, 2008 at 3:37 PM, Arnaldo Carvalho de Melo
>>> >> <acme@redhat.com> wrote:
>>> >> > Em Mon, Sep 29, 2008 at 03:33:44PM -0300, Leandro Sales escreveu:
>>> >> >> Hello folks,
>>> >> >>   I'm getting this message while using 2.6.27:
>>> >> >>
>>> >> >>   Can not create DCCP socket (Protocol driver not attached)
>>> >> >
>>> >> > What is the source of such messages? VLC? What? Try strace to see what
>>> >> > is the syscall that fails just before this message is printed, etc.
>>> >> >
>>> >> >>   "uname -a" output:
>>> >> >>       Linux localhost 2.6.27-rc4-44301-g8269be1 #7 SMP Sun Sep 28 17:02:25
>>> >> >>       BRT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
>>> >> >>
>>> >> >>   Anything wrong? I tried compile DCCP using both static and module
>>> >> >> methods and it produces the same effect.
>>> >> >
>>> >> > - Arnaldo
>>> >> >
>>> >>
>>> >> Hello Arnaldo,
>>> >>   I'm just running tests with iperf to later use gstreamer plugin that
>>> >> I developed. Here it is the output provided by strace while executing
>>> >> iperf. I'm sorry for the long message. In addition, I'm providing
>>> >> support for a guy from China that wants to use my gstreamer plugin and
>>> >> he is facing similar problem, getting a permission denied message
>>> >> while using the plugin, even then he run the plugin as root.
>>> >
>>> > iperf is multithreaded, so you need to run strace with -f to trace child
>>> > processes, also please try limiting the output to just the networking
>>> > syscalls:
>>> >
>>> > strace -f -e trace=network iperf
>>> >
>>> > "net namespaces" blipped in my mind, but it may well be just my brain
>>> > needing more coffee...
>>> >
>>> > - Arnaldo
>>> >
>>>
>>> Arnaldo, thank you for the reply. Please, check the strace output
>>> below. I'm not sure what it happen, although I have a thought. Any
>>> clue?
>>>
>>> Process 5849 attached (waiting for parent)
>>> Process 5849 resumed (parent 5848 ready)
>>> [pid  5849] socket(PF_NETLINK, SOCK_RAW, 0) = 3
>>> [pid  5849] bind(3, {sa_family¯_NETLINK, pid=0, groups\0000000}, 12) = 0
>>> [pid  5849] getsockname(3, {sa_family¯_NETLINK, pidX48,
>>> groups\0000000}, [12]) = 0
>>> [pid  5849] sendto(3, "\24\0\0\0\26\0\1\3&\230\342H\0\0\0\0\0\0\0\0",
>>> 20, 0, {sa_family¯_NETLINK, pid=0, groups\0000000}, 12) = 20
>>> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
>>> groups\0000000},
>>> msg_iov(1)=[{"8\0\0\0\24\0\2\0&\230\342H\330\26\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"...,
>>> 4096}], msg_controllen=0, msg_flags=0}, 0) = 116
>>> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
>>> groups\0000000},
>>> msg_iov(1)=[{"@\0\0\0\24\0\2\0&\230\342H\330\26\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"...,
>>> 4096}], msg_controllen=0, msg_flags=0}, 0) = 128
>>> [pid  5849] recvmsg(3, {msg_name(12)={sa_family¯_NETLINK, pid=0,
>>> groups\0000000},
>>> msg_iov(1)=[{"\24\0\0\0\3\0\2\0&\230\342H\330\26\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0"...,
>>> 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
>>> [pid  5849] socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3
>>> [pid  5849] connect(3, {sa_family¯_INET6, sin6_port=htons(5001),
>>> inet_pton(AF_INET6, "::", &sin6_addr), sin6_flowinfo=0,
>>> sin6_scope_id=0}, 28) = 0
>>> [pid  5849] getsockname(3, {sa_family¯_INET6,
>>> sin6_port=htons(56372), inet_pton(AF_INET6, "::1", &sin6_addr),
>>> sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
>>> [pid  5849] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
>>> [pid  5849] connect(3, {sa_family¯_INET, sin_port=htons(5001),
>>> sin_addr=inet_addr("0.0.0.0")}, 16) = 0
>>> [pid  5849] getsockname(3, {sa_family¯_INET, sin_port=htons(37587),
>>> sin_addr=inet_addr("127.0.0.1")}, [16]) = 0
>>> [pid  5849] socket(PF_INET6, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
>>> */) = -1 EUNATCH (Protocol driver not attached)
>>
>>
>> Here we gett the EUNATACH when trying SOCK_DCCP (6), IPPROTO_DCCP (33),
>> but I couldn't find any EUNATACH return in the sock_create path, do you
>> have selinux running?
>>
>> It tries several times PF_INET6 then falls back to PF_INET. Is this
>> using glibc? dietlibc? ARM? lsmod output can also help.
>>
>> - Arnaldo
>>
>
> Hello Arnaldo,
>
> kernel version: 2.6.27-rc4 (from gerrit git three)
>
> sys-libs/glibc version: 2.6.1
>
> No selinux running.
>
> In addition, this problem is occurring in both the desktop and on nokia n800.
>
> Thank you,
> Leandro.
>

Just completing the information. Using 2.6.26 on arm worked.

Regards,
Leandro.

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Em Thu, Oct 02, 2008 at 08:32:20AM +1300, Ian McDonald escreveu:
> >
> > Just completing the information. Using 2.6.26 on arm worked.
> >
> > Time to use git-bisect then I would guess...

Yes, its possible that this problem is not DCCP specific, perhaps
affecting SCTP too. I.e. both are loadable modules usually, while TCP is
always builtin.

- Arnaldo

Re: Protocol not attached

[Leandro Sales]

On Wed, Oct 1, 2008 at 4:37 PM, Arnaldo Carvalho de Melo
<acme@redhat.com> wrote:
> Em Thu, Oct 02, 2008 at 08:32:20AM +1300, Ian McDonald escreveu:
>> >
>> > Just completing the information. Using 2.6.26 on arm worked.
>> >
>> > Time to use git-bisect then I would guess...
>
> Yes, its possible that this problem is not DCCP specific, perhaps
> affecting SCTP too. I.e. both are loadable modules usually, while TCP is
> always builtin.
>
> - Arnaldo
>

Thanks Arnaldo and Ian.

Then, is it necessary to report this issue in the kernel dev maillist?

Regards,
Leandro.

Re: Protocol not attached

[Leandro Sales]

On Wed, Oct 1, 2008 at 4:43 PM, Leandro Sales <leandroal@gmail.com> wrote:
> On Wed, Oct 1, 2008 at 4:37 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
>> Em Thu, Oct 02, 2008 at 08:32:20AM +1300, Ian McDonald escreveu:
>>> >
>>> > Just completing the information. Using 2.6.26 on arm worked.
>>> >
>>> > Time to use git-bisect then I would guess...
>>
>> Yes, its possible that this problem is not DCCP specific, perhaps
>> affecting SCTP too. I.e. both are loadable modules usually, while TCP is
>> always builtin.
>>
>> - Arnaldo
>>
>
> Thanks Arnaldo and Ian.
>
> Then, is it necessary to report this issue in the kernel dev maillist?
>
> Regards,
> Leandro.
>

An additional information:
   I didn't run exhaustive tests, but I created a simple SCTP
application and it didn't work too using 2.6.27.r6. Both (DCCP and
SCTP) applications worked using 2.6.26.

Regards,
Leandro.

Re: Protocol not attached

[Ian McDonald]

On Thu, Oct 2, 2008 at 10:38 AM, Leandro Sales <leandroal@gmail.com> wrote:
>
> On Wed, Oct 1, 2008 at 4:43 PM, Leandro Sales <leandroal@gmail.com> wrote:
> > On Wed, Oct 1, 2008 at 4:37 PM, Arnaldo Carvalho de Melo
> > <acme@redhat.com> wrote:
> >> Em Thu, Oct 02, 2008 at 08:32:20AM +1300, Ian McDonald escreveu:
> >>> >
> >>> > Just completing the information. Using 2.6.26 on arm worked.
> >>> >
> >>> > Time to use git-bisect then I would guess...
> >>
> >> Yes, its possible that this problem is not DCCP specific, perhaps
> >> affecting SCTP too. I.e. both are loadable modules usually, while TCP is
> >> always builtin.
> >>
> >> - Arnaldo
> >>
> >
> > Thanks Arnaldo and Ian.
> >
> > Then, is it necessary to report this issue in the kernel dev maillist?
> >
> > Regards,
> > Leandro.
> >
>
> An additional information:
>   I didn't run exhaustive tests, but I created a simple SCTP
> application and it didn't work too using 2.6.27.r6. Both (DCCP and
> SCTP) applications worked using 2.6.26.
>
> Regards,
> Leandro.

Well now would be time to test with vanilla Linus tree/2.6.27rc8 and
then post to netdev as it has become a regression then... And there is
probably another 5 people in the world who use SCTP to add to the 5
who use DCCP ;-)

Ian

Re: Protocol not attached

[Gerrit Renker]

| 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.

Re: Protocol not attached

[Leandro Sales]

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?

Thank you,
Leandro.

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

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

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Forwarded to leandro/mailing list.

Em Fri, Oct 03, 2008 at 03:01:18PM +0100, gerrit@erg.abdn.ac.uk escreveu:
> >> # modprobe -l
> >> /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
> 
> <snip>
> 
> >> The module did not start in the boot (expected!). I then ran
> >>
> <snip>
> 
> > 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.
> >
> Yes can you please confirm if that is the case.
> 
> I wonder if this can be influenced by a configuration setting. I tried
> the same, with -rc7 and -rc8, on a Sempron 3700 64 bit and a Dual Core,
> worked without problem.

- Arnaldo

Re: Protocol not attached

[Gerrit Renker]

Leandro -
| # 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?
| 
are there any news regarding this issue? If there is a problem I would
like to address it since I am submitting this patch set.

Re: Protocol not attached

[Leandro Sales]

---------- Forwarded message ----------
From: Leandro Sales <leandroal@gmail.com>
Date: Sat, Oct 11, 2008 at 2:28 PM
Subject: Re: Protocol not attached
To: Gerrit Renker <gerrit@erg.abdn.ac.uk>, Leandro Sales
<leandroal@gmail.com>, DCCP Mailing List <dccp@vger.kernel.org>,
Erivaldo <desadoc@gmail.com>


On Sat, Oct 11, 2008 at 4:35 AM, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
>
> Leandro -
> | # 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?
> |
> are there any news regarding this issue? If there is a problem I would
> like to address it since I am submitting this patch set.

Hello Gerrit,

> > 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.
> >

After boot the following dccp modules were loaded:
Module                  Size  Used by
dccp_tfrc_lib          17868  0
dccp_ipv6              14916  2
dccp_ipv4              14596  3 dccp_ipv6
dccp                   58112  2 dccp_ipv6,dccp_ipv4

I run iperf and that error message appeared again. I then did what
Arnaldo suggested: I loaded dccp_ccid2 using modprobe, but iperf shows
the same error message. I ran iperf using strace com o 2.6.27-rc8:

strace -f -e trace=network iperf -s -d -l 1424 -1
Process 4374 attached
Process 4375 attached
[pid  4374] socket(PF_INET, 0x6 /* SOCK_??? */, IPPROTO_IP) = 3
[pid  4374] setsockopt(3, 0x10d /* SOL_?? */, 2, [1179796816], 4) = 0
[pid  4374] setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
[pid  4374] bind(3, {sa_family¯_INET, sin_port=htons(5001),
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
[pid  4374] listen(3, 5)                = 0
[pid  4374] accept(3,  <unfinished ...>
[pid  4375] getsockopt(3, SOL_SOCKET, SO_RCVBUF, [106496], [4]) = 0


Regards,
Leandro.

Re: Protocol not attached

[Gerrit Renker]

Hi Leandro
| 
|    After boot the following dccp modules were loaded:
|    Module                  Size  Used by
|    dccp_tfrc_lib          17868  0
|    dccp_ipv6              14916  2
|    dccp_ipv4              14596  3 dccp_ipv6
|    dccp                   58112  2 dccp_ipv6,dccp_ipv4
| 
|    I run iperf and that error message appeared again. I then did what Arnaldo
|    suggested: I loaded dccp_ccid2 using modprobe, but iperf shows the same
|    error message. I ran iperf using strace com o 2.6.27-rc8:
Unfortunately, loading just dccp_ccid2 is not sufficient to diagnose:
the feature-negotiation code preloads all CCID modules that it is going
to advertise to the peer. 

I can not find an error in the strace below. What I am asking is whether
the fault is due to 
 (1) a module loadin problem in general or
 (2) whether this problem is specific to DCCP.

Can you please check again -- thanks.

Gerrit
| 
|    strace -f -e trace=network iperf -s -d -l 1424 -1
|    Process 4374 attached
|    Process 4375 attached
|    [pid  4374] socket(PF_INET, 0x6 /* SOCK_??? */, IPPROTO_IP) = 3
|    [pid  4374] setsockopt(3, 0x10d /* SOL_?? */, 2, [1179796816], 4) = 0
|    [pid  4374] setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
|    [pid  4374] bind(3, {sa_family¯_INET, sin_port=htons(5001),
|    sin_addr=inet_addr("MailScanner warning: numerical links are often
|    malicious: 0.0.0.0")}, 16) = 0
|    [pid  4374] listen(3, 5)                = 0
|    [pid  4374] accept(3,  <unfinished ...>
|    [pid  4375] getsockopt(3, SOL_SOCKET, SO_RCVBUF, [106496], [4]) = 0

Re: Protocol not attached

[Leandro Sales]

On Mon, Oct 13, 2008 at 2:51 PM, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
>
> Hi Leandro
> |
> |    After boot the following dccp modules were loaded:
> |    Module                  Size  Used by
> |    dccp_tfrc_lib          17868  0
> |    dccp_ipv6              14916  2
> |    dccp_ipv4              14596  3 dccp_ipv6
> |    dccp                   58112  2 dccp_ipv6,dccp_ipv4
> |
> |    I run iperf and that error message appeared again. I then did what Arnaldo
> |    suggested: I loaded dccp_ccid2 using modprobe, but iperf shows the same
> |    error message. I ran iperf using strace com o 2.6.27-rc8:
> Unfortunately, loading just dccp_ccid2 is not sufficient to diagnose:
> the feature-negotiation code preloads all CCID modules that it is going
> to advertise to the peer.
>
> I can not find an error in the strace below. What I am asking is whether
> the fault is due to
>  (1) a module loadin problem in general or
>  (2) whether this problem is specific to DCCP.
>
> Can you please check again -- thanks.
>
> Gerrit
> |
> |    strace -f -e trace=network iperf -s -d -l 1424 -1
> |    Process 4374 attached
> |    Process 4375 attached
> |    [pid  4374] socket(PF_INET, 0x6 /* SOCK_??? */, IPPROTO_IP) = 3
> |    [pid  4374] setsockopt(3, 0x10d /* SOL_?? */, 2, [1179796816], 4) = 0
> |    [pid  4374] setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
> |    [pid  4374] bind(3, {sa_family¯_INET, sin_port=htons(5001),
> |    sin_addr=inet_addr("MailScanner warning: numerical links are often
> |    malicious: 0.0.0.0")}, 16) = 0
> |    [pid  4374] listen(3, 5)                = 0
> |    [pid  4374] accept(3,  <unfinished ...>
> |    [pid  4375] getsockopt(3, SOL_SOCKET, SO_RCVBUF, [106496], [4]) = 0

Hello Gerrit,

I tried to be more precise.

I run the same kernel in two very similar computers, in one computer
it works perfect, in another one, not. Maybe this problem is happening
due to miss-configuring in the computer that occurs this error. In all
the case, I have here de .config for both machines (kernel 2.6.27-rc8)
and the complete strace.log for both execution. If you'd like to
analyze them I can send you. Please let me know in case that you want
me to send you the configs and strace log files.

Regards,
Leandro.

Re: Protocol not attached

[Gerrit Renker]

| Please let me know in case that you want me to send you the configs and strace log files.
Yes, please do -- on the computers I have tried (32/64 bit) it works.

Gerrit

Re: Protocol not attached

[Gerrit Renker]

| > | Please let me know in case that you want me to send you the configs and strace log files.
| > Yes, please do -- on the computers I have tried (32/64 bit) it works.
| >
| > Gerrit
| >
| 
| Hello Gerrit,
|   here they are!
Thanks very much. 

In the error log the EUNATCH appears within the call to socket, before any
other call (connect, listen). This means that DCCP is not able to load the
CCID modules at initialisation time.

I have compared the two .config files, below are a few ideas. I tested
by adding/disabling configuration options, then unloading all modules and
starting 'ipdf -sd'. If this loads the CCID modules, then everything is ok.

 1. the Pentium4 has no CONFIG_HIBERNATION set, while the K8 (which has
    the module load error) has it set; adding this feature did not cause
    an error to appear;
 2. the K8 has no IPv6 support enabled -- I built a kernel without IPv6
    and it still worked ok;
 3. could it have to do with security ?:- the Pentium (which works)
    has no security enabled, while the K8 (which doesn't work) has
    CONFIG_SECURITY=y;
 4. a thing which I could not test was CONFIG_USB_NET, which was enabled
    on the K8.

Unfortunately, on the Centrino-Duo I could not provoke a faulty behaviour.

Since 2.6.27 just came out, would it be a lot of effort to try again
with the more recent kernel and see if the problem persists?

Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
net/ (towards removing KMOD entirely)", so perhaps there is something in
progress.

I have uploaded the new test tree, after changing the patch "Auto-load
(when supported) CCID plugins for negotiation"
http://eden-feed.erg.abdn.ac.uk/cgi-bin/gitweb.cgi?p‹cp_exp.git;a=commitdiff;hVbcfc75b874d27039c1a26055669dd8c69c57b7

Gerrit
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Em Sat, Oct 18, 2008 at 01:06:28PM +0200, Gerrit Renker escreveu:

<SNIP>

> Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
> net/ (towards removing KMOD entirely)", so perhaps there is something in
> progress.

Is CONFIG_MODULES present in the config file that produces a kernel that
has the problem?

I guess not, Leandro, can you please add it manually, then do a make
oldconfig, check that it is still there, then build the kernel?

This is the part of the patch Gerrit mentioned
(95a5afca4a8d2e1cb77e1d4bc6ff9f718dc32f7a) that could be hitting you.


diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c
index 4809753..8fe931a 100644
--- a/net/dccp/ccid.c
+++ b/net/dccp/ccid.c
@@ -154,7 +154,7 @@ struct ccid *ccid_new(unsigned char id, struct sock *sk, int rx, gfp_t gfp)
        struct ccid *ccid = NULL;
 
        ccids_read_lock();
-#ifdef CONFIG_KMOD
+#ifdef CONFIG_MODULES
        if (ccids[id] = NULL) {
                /* We only try to load if in process context */
                ccids_read_unlock();

- Arnaldo

Re: Protocol not attached

[Leandro Sales]

[-- Attachment #1: Type: text/plain, Size: 3027 bytes --]

On Mon, Oct 20, 2008 at 10:13 AM, Arnaldo Carvalho de Melo
<acme@redhat.com> wrote:
> Em Sat, Oct 18, 2008 at 01:06:28PM +0200, Gerrit Renker escreveu:
>
> <SNIP>
>
>> Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
>> net/ (towards removing KMOD entirely)", so perhaps there is something in
>> progress.
>
> Is CONFIG_MODULES present in the config file that produces a kernel that
> has the problem?
>
> I guess not, Leandro, can you please add it manually, then do a make
> oldconfig, check that it is still there, then build the kernel?
>
> This is the part of the patch Gerrit mentioned
> (95a5afca4a8d2e1cb77e1d4bc6ff9f718dc32f7a) that could be hitting you.
>
>
> diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c
> index 4809753..8fe931a 100644
> --- a/net/dccp/ccid.c
> +++ b/net/dccp/ccid.c
> @@ -154,7 +154,7 @@ struct ccid *ccid_new(unsigned char id, struct sock *sk, int rx, gfp_t gfp)
>        struct ccid *ccid = NULL;
>
>        ccids_read_lock();
> -#ifdef CONFIG_KMOD
> +#ifdef CONFIG_MODULES
>        if (ccids[id] == NULL) {
>                /* We only try to load if in process context */
>                ccids_read_unlock();
>
> - Arnaldo
>

I run the test again. I run git clone --reference, git checkgout
origin/dccp as usual. It does not show 2.6.27-rc8 in the DCCP tree,
only 2.6.27. Is that correct?

# `uname -a`
Linux localhost 2.6.27-48036-g29aae39 #1 SMP Tue Oct 21 09:43:27 BRT
2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux

I compiled dccp as module, disabled CONFIG_SECURITY, CONFIG_USBNET and
Ipv6 as per Gerrit suggestion and CONFIG_MODULES=y as per Arnaldo
suggestion. Here it is the strace result:

`strace -f -e trace=network iperf -sd`

Process 5947 attached
Process 5948 attached
[pid  5947] socket(PF_NETLINK, SOCK_RAW, 0) = 3
[pid  5947] bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
[pid  5947] getsockname(3, {sa_family=AF_NETLINK, pid=5946,
groups=00000000}, [12]) = 0
[pid  5947] sendto(3, "\24\0\0\0\26\0\1\3/\332\375H\0\0\0\0\0\0\0\0",
20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
[pid  5947] recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0,
groups=00000000},
msg_iov(1)=[{"8\0\0\0\24\0\2\0/\332\375H:\27\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 116
[pid  5947] recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0,
groups=00000000},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0/\332\375H:\27\0\0\0\0\0\0\1\0\0\0\10\0\1\0\177\0\0\1"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
[pid  5947] socket(PF_INET, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/) = -1 EUNATCH (Protocol driver not attached)
[pid  5947] socket(PF_INET, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/) = -1 EUNATCH (Protocol driver not attached)
[pid  5947] socket(PF_INET, 0x6 /* SOCK_??? */, 0x21 /* IPPROTO_???
*/) = -1 EUNATCH (Protocol driver not attached)
Can not create DCCP socket (Protocol driver not attached)
Process 5947 detached

My .config is attached.

Leandro.

[-- Attachment #2: config_desktop --]
[-- Type: application/octet-stream, Size: 45447 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.27
# Tue Oct 21 09:32:43 2008
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_ARCH_SUPPORTS_AOUT=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
# CONFIG_CGROUPS is not set
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_GROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_IPC_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
# CONFIG_MARKERS is not set
CONFIG_OPROFILE=y
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
# CONFIG_HAVE_DMA_ATTRS is not set
CONFIG_USE_GENERIC_SMP_HELPERS=y
# CONFIG_HAVE_CLK is not set
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_CLASSIC_RCU=y

#
# Processor type and features
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
# CONFIG_X86_RDC321X is not set
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
CONFIG_MK8=y
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CPU=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_MINIMUM_CPU_FAMILY=4
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_X86_DS=y
CONFIG_X86_PTRACE_BTS=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
CONFIG_NR_CPUS=32
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
# CONFIG_X86_PAT is not set
# CONFIG_EFI is not set
CONFIG_IRQBALANCE=y
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_SCHED_HRTICK is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x200000
CONFIG_HOTPLUG_CPU=y
CONFIG_COMPAT_VDSO=y
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_WMI is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_DEBUG=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=y
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
CONFIG_X86_POWERNOW_K8=y
CONFIG_X86_POWERNOW_K8_ACPI=y
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set

#
# shared options
#
CONFIG_X86_ACPI_CPUFREQ_PROC_INTF=y
# CONFIG_X86_SPEEDSTEP_LIB is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
# CONFIG_PCI_GOOLPC is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIEASPM is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_HT_IRQ is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_OLPC is not set
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
CONFIG_IP_DCCP_CCID2_DEBUG=y
CONFIG_IP_DCCP_CCID3=m
CONFIG_IP_DCCP_CCID3_DEBUG=y
CONFIG_IP_DCCP_CCID3_MEASURE_S_AS_MPS=y
# CONFIG_IP_DCCP_CCID3_MEASURE_S_AS_AVG is not set
# CONFIG_IP_DCCP_CCID3_MEASURE_S_AS_MAX is not set
CONFIG_IP_DCCP_CCID3_RTO=100
CONFIG_IP_DCCP_TFRC_LIB=m
CONFIG_IP_DCCP_TFRC_DEBUG=y

#
# DCCP Kernel Hacking
#
CONFIG_IP_DCCP_DEBUG=y
CONFIG_NET_DCCPPROBE=m
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_PHONET is not set
# CONFIG_WIRELESS is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_TC1100_WMI is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_INTEL_MENLOW is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
CONFIG_HAVE_IDE=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide/ide.txt for help/info on IDE drives
#
CONFIG_IDE_TIMINGS=y
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_BLK_DEV_IDEACPI=y
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_PLATFORM is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEDMA_SFF=y

#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_BLK_DEV_TC86C001 is not set
CONFIG_BLK_DEV_IDEDMA=y

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
CONFIG_SCSI_NETLINK=y
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=y
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=4000
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_DH is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=y
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
CONFIG_SATA_SVW=y
CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
CONFIG_SATA_NV=y
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
CONFIG_SATA_SIL=y
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
CONFIG_SATA_VIA=y
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ACPI is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_SCH is not set
# CONFIG_MD is not set
CONFIG_FUSION=y
CONFIG_FUSION_SPI=y
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set
CONFIG_FUSION_MAX_SGE=128
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LOGGING is not set

#
# IEEE 1394 (FireWire) support
#

#
# Enable only one of the two stacks, unless you know what you are doing
#
# CONFIG_FIREWIRE is not set
CONFIG_IEEE1394=y
CONFIG_IEEE1394_OHCI1394=y
# CONFIG_IEEE1394_PCILYNX is not set
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394_ROM_ENTRY is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_RAWIO=y
# CONFIG_IEEE1394_VIDEO1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=y

#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_FIXED_PHY is not set
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
CONFIG_VIA_RHINE=y
CONFIG_VIA_RHINE_MMIO=y
# CONFIG_SC92031 is not set
# CONFIG_ATL2 is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
# CONFIG_E1000E is not set
# CONFIG_IP1000 is not set
# CONFIG_IGB is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_R8169=y
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=y
CONFIG_BNX2=y
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_JME is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_IWLWIFI_LEDS is not set

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=y
CONFIG_HW_RANDOM_AMD=y
CONFIG_HW_RANDOM_GEODE=y
CONFIG_HW_RANDOM_VIA=y
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=256
CONFIG_HPET=y
CONFIG_HPET_RTC_IRQ=y
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
# CONFIG_I2C_CHARDEV is not set
CONFIG_I2C_HELPER_AUTO=y

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_SIMTEC is not set

#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set

#
# Graphics adapter I2C/DDC channel drivers
#
# CONFIG_I2C_VOODOO3 is not set

#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_STUB is not set
# CONFIG_SCx200_ACB is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
# CONFIG_AT24 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_PCF8575 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
# CONFIG_SPI is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_HWMON is not set
CONFIG_THERMAL=y
# CONFIG_WATCHDOG is not set

#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
CONFIG_SSB=y
CONFIG_SSB_SPROM=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
# CONFIG_SSB_B43_PCI_BRIDGE is not set
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_UCB1400_CORE is not set
# CONFIG_MFD_TMIO is not set

#
# Multimedia devices
#

#
# Multimedia core support
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_VIDEO_MEDIA is not set

#
# Multimedia drivers
#
CONFIG_DAB=y
# CONFIG_USB_DABUSB is not set

#
# Graphics support
#
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=y
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
CONFIG_DRM_I810=y
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=y
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=256
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_SEQ_DUMMY=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_MPU401_UART=y
CONFIG_SND_AC97_CODEC=y
CONFIG_SND_DRIVERS=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_AC97_POWER_SAVE is not set
CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_HIFIER is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SIS7019 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
CONFIG_SND_VIA82XX=y
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_US122L is not set
# CONFIG_SND_SOC is not set
CONFIG_SOUND_PRIME=y
# CONFIG_SOUND_OSS is not set
CONFIG_AC97_BUS=y
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=y

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_HCD_SSB is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
# CONFIG_USB_WDM is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_UIO is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
# CONFIG_ISCSI_IBFT_FIND is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_EXT2_FS_SECURITY is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
# CONFIG_REISERFS_FS_SECURITY is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
CONFIG_ROOT_NFS=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_HAVE_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
# CONFIG_FTRACE is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_CONTEXT_SWITCH_TRACER is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_X86_PTDUMP is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_4KSTACKS is not set
CONFIG_DOUBLEFAULT=y
# CONFIG_MMIOTRACE is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
# CONFIG_OPTIMIZE_INLINING is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

#
# Block modes
#
# CONFIG_CRYPTO_CBC is not set
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set

#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_586 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set

#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_LZO is not set

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
# CONFIG_CRYPTO_DEV_GEODE is not set
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
# CONFIG_LGUEST is not set
# CONFIG_VIRTIO_PCI is not set
# CONFIG_VIRTIO_BALLOON is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Em Tue, Oct 21, 2008 at 11:19:36AM -0300, Leandro Sales escreveu:
> On Mon, Oct 20, 2008 at 10:13 AM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
> > Em Sat, Oct 18, 2008 at 01:06:28PM +0200, Gerrit Renker escreveu:
> >
> > <SNIP>
> >
> >> Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
> >> net/ (towards removing KMOD entirely)", so perhaps there is something in
> >> progress.
> >
> > Is CONFIG_MODULES present in the config file that produces a kernel that
> > has the problem?

Well, he has both CONFIG_KMOD and CONFIG_MODULES...

> > I guess not, Leandro, can you please add it manually, then do a make
> > oldconfig, check that it is still there, then build the kernel?
> >
> > This is the part of the patch Gerrit mentioned
> > (95a5afca4a8d2e1cb77e1d4bc6ff9f718dc32f7a) that could be hitting you.
> >
> >
> > diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c
> > index 4809753..8fe931a 100644
> > --- a/net/dccp/ccid.c
> > +++ b/net/dccp/ccid.c
> > @@ -154,7 +154,7 @@ struct ccid *ccid_new(unsigned char id, struct sock *sk, int rx, gfp_t gfp)
> >        struct ccid *ccid = NULL;
> >
> >        ccids_read_lock();
> > -#ifdef CONFIG_KMOD
> > +#ifdef CONFIG_MODULES
> >        if (ccids[id] = NULL) {
> >                /* We only try to load if in process context */
> >                ccids_read_unlock();
> >
> > - Arnaldo
> >
> 
> I run the test again. I run git clone --reference, git checkgout
> origin/dccp as usual. It does not show 2.6.27-rc8 in the DCCP tree,
> only 2.6.27. Is that correct?

I guess that there was when Gerrit branched, can you try using Linus
tree?

I.e. start bisecting, and it doesn't even needs to be with git, do it
the old way :)

- Arnaldo

Re: Protocol not attached

[Leandro Sales]

On Tue, Oct 21, 2008 at 2:32 PM, Arnaldo Carvalho de Melo
<acme@redhat.com> wrote:
> Em Tue, Oct 21, 2008 at 11:19:36AM -0300, Leandro Sales escreveu:
>> On Mon, Oct 20, 2008 at 10:13 AM, Arnaldo Carvalho de Melo
>> <acme@redhat.com> wrote:
>> > Em Sat, Oct 18, 2008 at 01:06:28PM +0200, Gerrit Renker escreveu:
>> >
>> > <SNIP>
>> >
>> >> Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
>> >> net/ (towards removing KMOD entirely)", so perhaps there is something in
>> >> progress.
>> >
>> > Is CONFIG_MODULES present in the config file that produces a kernel that
>> > has the problem?
>
> Well, he has both CONFIG_KMOD and CONFIG_MODULES...
>
>> > I guess not, Leandro, can you please add it manually, then do a make
>> > oldconfig, check that it is still there, then build the kernel?
>> >
>> > This is the part of the patch Gerrit mentioned
>> > (95a5afca4a8d2e1cb77e1d4bc6ff9f718dc32f7a) that could be hitting you.
>> >
>> >
>> > diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c
>> > index 4809753..8fe931a 100644
>> > --- a/net/dccp/ccid.c
>> > +++ b/net/dccp/ccid.c
>> > @@ -154,7 +154,7 @@ struct ccid *ccid_new(unsigned char id, struct sock *sk, int rx, gfp_t gfp)
>> >        struct ccid *ccid = NULL;
>> >
>> >        ccids_read_lock();
>> > -#ifdef CONFIG_KMOD
>> > +#ifdef CONFIG_MODULES
>> >        if (ccids[id] = NULL) {
>> >                /* We only try to load if in process context */
>> >                ccids_read_unlock();
>> >
>> > - Arnaldo
>> >
>>
>> I run the test again. I run git clone --reference, git checkgout
>> origin/dccp as usual. It does not show 2.6.27-rc8 in the DCCP tree,
>> only 2.6.27. Is that correct?
>
> I guess that there was when Gerrit branched, can you try using Linus
> tree?
>
> I.e. start bisecting, and it doesn't even needs to be with git, do it
> the old way :)
>
> - Arnaldo
>

Hello Arnaldo and others,

I tested with the stable 2.6.27.2 and it worked. I will try the Linus git now.

Leandro.

Re: Protocol not attached

[Leandro Sales]

On Tue, Oct 21, 2008 at 3:08 PM, Leandro Sales <leandroal@gmail.com> wrote:
> On Tue, Oct 21, 2008 at 2:32 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
>> Em Tue, Oct 21, 2008 at 11:19:36AM -0300, Leandro Sales escreveu:
>>> On Mon, Oct 20, 2008 at 10:13 AM, Arnaldo Carvalho de Melo
>>> <acme@redhat.com> wrote:
>>> > Em Sat, Oct 18, 2008 at 01:06:28PM +0200, Gerrit Renker escreveu:
>>> >
>>> > <SNIP>
>>> >
>>> >> Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
>>> >> net/ (towards removing KMOD entirely)", so perhaps there is something in
>>> >> progress.
>>> >
>>> > Is CONFIG_MODULES present in the config file that produces a kernel that
>>> > has the problem?
>>
>> Well, he has both CONFIG_KMOD and CONFIG_MODULES...
>>
>>> > I guess not, Leandro, can you please add it manually, then do a make
>>> > oldconfig, check that it is still there, then build the kernel?
>>> >
>>> > This is the part of the patch Gerrit mentioned
>>> > (95a5afca4a8d2e1cb77e1d4bc6ff9f718dc32f7a) that could be hitting you.
>>> >
>>> >
>>> > diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c
>>> > index 4809753..8fe931a 100644
>>> > --- a/net/dccp/ccid.c
>>> > +++ b/net/dccp/ccid.c
>>> > @@ -154,7 +154,7 @@ struct ccid *ccid_new(unsigned char id, struct sock *sk, int rx, gfp_t gfp)
>>> >        struct ccid *ccid = NULL;
>>> >
>>> >        ccids_read_lock();
>>> > -#ifdef CONFIG_KMOD
>>> > +#ifdef CONFIG_MODULES
>>> >        if (ccids[id] = NULL) {
>>> >                /* We only try to load if in process context */
>>> >                ccids_read_unlock();
>>> >
>>> > - Arnaldo
>>> >
>>>
>>> I run the test again. I run git clone --reference, git checkgout
>>> origin/dccp as usual. It does not show 2.6.27-rc8 in the DCCP tree,
>>> only 2.6.27. Is that correct?
>>
>> I guess that there was when Gerrit branched, can you try using Linus
>> tree?
>>
>> I.e. start bisecting, and it doesn't even needs to be with git, do it
>> the old way :)
>>
>> - Arnaldo
>>
>
> Hello Arnaldo and others,
>
> I tested with the stable 2.6.27.2 and it worked. I will try the Linus git now.
>
> Leandro.
>

Using the Linus git iperf run successfully. Then, does we have
something broken in Gerrit git three?

Leandro.

Re: Protocol not attached

[Leandro Sales]

On Tue, Oct 21, 2008 at 10:37 PM, Leandro Sales <leandroal@gmail.com> wrote:
> On Tue, Oct 21, 2008 at 3:08 PM, Leandro Sales <leandroal@gmail.com> wrote:
>> On Tue, Oct 21, 2008 at 2:32 PM, Arnaldo Carvalho de Melo
>> <acme@redhat.com> wrote:
>>> Em Tue, Oct 21, 2008 at 11:19:36AM -0300, Leandro Sales escreveu:
>>>> On Mon, Oct 20, 2008 at 10:13 AM, Arnaldo Carvalho de Melo
>>>> <acme@redhat.com> wrote:
>>>> > Em Sat, Oct 18, 2008 at 01:06:28PM +0200, Gerrit Renker escreveu:
>>>> >
>>>> > <SNIP>
>>>> >
>>>> >> Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
>>>> >> net/ (towards removing KMOD entirely)", so perhaps there is something in
>>>> >> progress.
>>>> >
>>>> > Is CONFIG_MODULES present in the config file that produces a kernel that
>>>> > has the problem?
>>>
>>> Well, he has both CONFIG_KMOD and CONFIG_MODULES...
>>>
>>>> > I guess not, Leandro, can you please add it manually, then do a make
>>>> > oldconfig, check that it is still there, then build the kernel?
>>>> >
>>>> > This is the part of the patch Gerrit mentioned
>>>> > (95a5afca4a8d2e1cb77e1d4bc6ff9f718dc32f7a) that could be hitting you.
>>>> >
>>>> >
>>>> > diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c
>>>> > index 4809753..8fe931a 100644
>>>> > --- a/net/dccp/ccid.c
>>>> > +++ b/net/dccp/ccid.c
>>>> > @@ -154,7 +154,7 @@ struct ccid *ccid_new(unsigned char id, struct sock *sk, int rx, gfp_t gfp)
>>>> >        struct ccid *ccid = NULL;
>>>> >
>>>> >        ccids_read_lock();
>>>> > -#ifdef CONFIG_KMOD
>>>> > +#ifdef CONFIG_MODULES
>>>> >        if (ccids[id] = NULL) {
>>>> >                /* We only try to load if in process context */
>>>> >                ccids_read_unlock();
>>>> >
>>>> > - Arnaldo
>>>> >
>>>>
>>>> I run the test again. I run git clone --reference, git checkgout
>>>> origin/dccp as usual. It does not show 2.6.27-rc8 in the DCCP tree,
>>>> only 2.6.27. Is that correct?
>>>
>>> I guess that there was when Gerrit branched, can you try using Linus
>>> tree?
>>>
>>> I.e. start bisecting, and it doesn't even needs to be with git, do it
>>> the old way :)
>>>
>>> - Arnaldo
>>>
>>
>> Hello Arnaldo and others,
>>
>> I tested with the stable 2.6.27.2 and it worked. I will try the Linus git now.
>>
>> Leandro.
>>
>
> Using the Linus git iperf run successfully. Then, does we have
> something broken in Gerrit git three?
>
> Leandro.
>


I meant, (...) "Gerrit git tree"

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Em Tue, Oct 21, 2008 at 10:37:38PM -0300, Leandro Sales escreveu:
> On Tue, Oct 21, 2008 at 10:37 PM, Leandro Sales <leandroal@gmail.com> wrote:
> > On Tue, Oct 21, 2008 at 3:08 PM, Leandro Sales <leandroal@gmail.com> wrote:
> >> On Tue, Oct 21, 2008 at 2:32 PM, Arnaldo Carvalho de Melo
> >> <acme@redhat.com> wrote:
> >>> Em Tue, Oct 21, 2008 at 11:19:36AM -0300, Leandro Sales escreveu:
> >>>> On Mon, Oct 20, 2008 at 10:13 AM, Arnaldo Carvalho de Melo
> >>>> <acme@redhat.com> wrote:
> >>>> > Em Sat, Oct 18, 2008 at 01:06:28PM +0200, Gerrit Renker escreveu:
> >>>> >
> >>>> > <SNIP>
> >>>> >
> >>>> >> Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
> >>>> >> net/ (towards removing KMOD entirely)", so perhaps there is something in
> >>>> >> progress.
> >>>> >
> >>>> > Is CONFIG_MODULES present in the config file that produces a kernel that
> >>>> > has the problem?
> >>>
> >>> Well, he has both CONFIG_KMOD and CONFIG_MODULES...
> >>>
> >>>> > I guess not, Leandro, can you please add it manually, then do a make
> >>>> > oldconfig, check that it is still there, then build the kernel?
> >>>> >
> >>>> > This is the part of the patch Gerrit mentioned
> >>>> > (95a5afca4a8d2e1cb77e1d4bc6ff9f718dc32f7a) that could be hitting you.
> >>>> >
> >>>> >
> >>>> > diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c
> >>>> > index 4809753..8fe931a 100644
> >>>> > --- a/net/dccp/ccid.c
> >>>> > +++ b/net/dccp/ccid.c
> >>>> > @@ -154,7 +154,7 @@ struct ccid *ccid_new(unsigned char id, struct sock *sk, int rx, gfp_t gfp)
> >>>> >        struct ccid *ccid = NULL;
> >>>> >
> >>>> >        ccids_read_lock();
> >>>> > -#ifdef CONFIG_KMOD
> >>>> > +#ifdef CONFIG_MODULES
> >>>> >        if (ccids[id] = NULL) {
> >>>> >                /* We only try to load if in process context */
> >>>> >                ccids_read_unlock();
> >>>> >
> >>>> > - Arnaldo
> >>>> >
> >>>>
> >>>> I run the test again. I run git clone --reference, git checkgout
> >>>> origin/dccp as usual. It does not show 2.6.27-rc8 in the DCCP tree,
> >>>> only 2.6.27. Is that correct?
> >>>
> >>> I guess that there was when Gerrit branched, can you try using Linus
> >>> tree?
> >>>
> >>> I.e. start bisecting, and it doesn't even needs to be with git, do it
> >>> the old way :)
> >>>
> >>> - Arnaldo
> >>>
> >>
> >> Hello Arnaldo and others,
> >>
> >> I tested with the stable 2.6.27.2 and it worked. I will try the Linus git now.
> >>
> >> Leandro.
> >>
> >
> > Using the Linus git iperf run successfully. Then, does we have
> > something broken in Gerrit git three?
> >
> > Leandro.
> >
> 
> 
> I meant, (...) "Gerrit git tree"

I looks like, you could then try to help Gerrit by doing a git bisection
on his tree, starting from where he branched, see:

http://www.arthurgeek.net/git-bisect/

for a git bisect tutorial, even in portuguese :-)

- Arnaldo

Re: Protocol not attached

[Leandro Sales]

On Wed, Oct 22, 2008 at 11:38 AM, Arnaldo Carvalho de Melo
<acme@redhat.com> wrote:
> Em Tue, Oct 21, 2008 at 10:37:38PM -0300, Leandro Sales escreveu:
>> On Tue, Oct 21, 2008 at 10:37 PM, Leandro Sales <leandroal@gmail.com> wrote:
>> > On Tue, Oct 21, 2008 at 3:08 PM, Leandro Sales <leandroal@gmail.com> wrote:
>> >> On Tue, Oct 21, 2008 at 2:32 PM, Arnaldo Carvalho de Melo
>> >> <acme@redhat.com> wrote:
>> >>> Em Tue, Oct 21, 2008 at 11:19:36AM -0300, Leandro Sales escreveu:
>> >>>> On Mon, Oct 20, 2008 at 10:13 AM, Arnaldo Carvalho de Melo
>> >>>> <acme@redhat.com> wrote:
>> >>>> > Em Sat, Oct 18, 2008 at 01:06:28PM +0200, Gerrit Renker escreveu:
>> >>>> >
>> >>>> > <SNIP>
>> >>>> >
>> >>>> >> Incidentally the new netdev-2.6 has a commit called "Remove CONFIG_KMOD from
>> >>>> >> net/ (towards removing KMOD entirely)", so perhaps there is something in
>> >>>> >> progress.
>> >>>> >
>> >>>> > Is CONFIG_MODULES present in the config file that produces a kernel that
>> >>>> > has the problem?
>> >>>
>> >>> Well, he has both CONFIG_KMOD and CONFIG_MODULES...
>> >>>
>> >>>> > I guess not, Leandro, can you please add it manually, then do a make
>> >>>> > oldconfig, check that it is still there, then build the kernel?
>> >>>> >
>> >>>> > This is the part of the patch Gerrit mentioned
>> >>>> > (95a5afca4a8d2e1cb77e1d4bc6ff9f718dc32f7a) that could be hitting you.
>> >>>> >
>> >>>> >
>> >>>> > diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c
>> >>>> > index 4809753..8fe931a 100644
>> >>>> > --- a/net/dccp/ccid.c
>> >>>> > +++ b/net/dccp/ccid.c
>> >>>> > @@ -154,7 +154,7 @@ struct ccid *ccid_new(unsigned char id, struct sock *sk, int rx, gfp_t gfp)
>> >>>> >        struct ccid *ccid = NULL;
>> >>>> >
>> >>>> >        ccids_read_lock();
>> >>>> > -#ifdef CONFIG_KMOD
>> >>>> > +#ifdef CONFIG_MODULES
>> >>>> >        if (ccids[id] = NULL) {
>> >>>> >                /* We only try to load if in process context */
>> >>>> >                ccids_read_unlock();
>> >>>> >
>> >>>> > - Arnaldo
>> >>>> >
>> >>>>
>> >>>> I run the test again. I run git clone --reference, git checkgout
>> >>>> origin/dccp as usual. It does not show 2.6.27-rc8 in the DCCP tree,
>> >>>> only 2.6.27. Is that correct?
>> >>>
>> >>> I guess that there was when Gerrit branched, can you try using Linus
>> >>> tree?
>> >>>
>> >>> I.e. start bisecting, and it doesn't even needs to be with git, do it
>> >>> the old way :)
>> >>>
>> >>> - Arnaldo
>> >>>
>> >>
>> >> Hello Arnaldo and others,
>> >>
>> >> I tested with the stable 2.6.27.2 and it worked. I will try the Linus git now.
>> >>
>> >> Leandro.
>> >>
>> >
>> > Using the Linus git iperf run successfully. Then, does we have
>> > something broken in Gerrit git three?
>> >
>> > Leandro.
>> >
>>
>>
>> I meant, (...) "Gerrit git tree"
>
> I looks like, you could then try to help Gerrit by doing a git bisection
> on his tree, starting from where he branched, see:
>
> http://www.arthurgeek.net/git-bisect/
>
> for a git bisect tutorial, even in portuguese :-)
>
> - Arnaldo
>

OK Arnaldo, I will do this. Gerrit, do you think about which commit
this bug was introduced?

Leandro.

Re: Protocol not attached

[Gerrit Renker]

| > > Using the Linus git iperf run successfully. Then, does we have
| > > something broken in Gerrit git three?
| > >
| > > Leandro.
| > >
| > 
| > 
| > I meant, (...) "Gerrit git tree"
| 
| I looks like, you could then try to help Gerrit by doing a git bisection
| on his tree, starting from where he branched, see:
| 
| http://www.arthurgeek.net/git-bisect/
| 
| for a git bisect tutorial, even in portuguese :-)
| 
I will have a more detailed look at home. But between the stable tree
and the linus sources there is another intermediate step that one could
try, which is testing if the netdev-2.6 has any problems:

 1) if you are pulling the entire dccp_exp tree, you could test this
    by simply checking out 'master';
 2) otherwise, the netdev-2.6 tree can be pulled via
    git pull git://eden-feed.erg.abdn.ac.uk/dccp_exp  +master:my_local_subtree

Many thanks for this testing, I will also look through.

Gerrit

Re: Protocol not attached

[Leandro Sales]

On Wed, Oct 22, 2008 at 3:55 PM, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
> | > > Using the Linus git iperf run successfully. Then, does we have
> | > > something broken in Gerrit git three?
> | > >
> | > > Leandro.
> | > >
> | >
> | >
> | > I meant, (...) "Gerrit git tree"
> |
> | I looks like, you could then try to help Gerrit by doing a git bisection
> | on his tree, starting from where he branched, see:
> |
> | http://www.arthurgeek.net/git-bisect/
> |
> | for a git bisect tutorial, even in portuguese :-)
> |
> I will have a more detailed look at home. But between the stable tree
> and the linus sources there is another intermediate step that one could
> try, which is testing if the netdev-2.6 has any problems:
>
>  1) if you are pulling the entire dccp_exp tree, you could test this
>    by simply checking out 'master';
>  2) otherwise, the netdev-2.6 tree can be pulled via
>    git pull git://eden-feed.erg.abdn.ac.uk/dccp_exp  +master:my_local_subtree
>
> Many thanks for this testing, I will also look through.
>
> Gerrit

We've tested using netdev tree and it is working.

Leandro.

Re: Protocol not attached

[gerrit]

>
> We've tested using netdev tree and it is working.
>
Unfortunately, the fact that it works under the Linus tree and under the
netdev-2.6 tree does not mean that the cause of the problem has gone.

This is because the request_module calls from the DCCP tree are missing.
So one could test by

 1) trying the DCCP patch on the Linus tree
    http://eden-feed.erg.abdn.ac.uk/latest-dccp-test-tree.diff.gz

 2) check netdev-2.6 + DCCP patches -- but you already tested this
    and it was the reason for this thread.

Looking at your .config file again yesterday I noted that it sets
 # CONFIG_64BIT is not set
 CONFIG_X86_32=y
 # CONFIG_X86_64 is not set
 CONFIG_X86=y,

i.e. you are compiling a 32 bit kernel on a 64bit (Athlon) processor. On
the Sempron I use a 64 bit kernel and it works. Yesterday evening I tried
(with some difficulties) to build the 32-bit variant and, ecce, after
building it it hung in a call to request_modules for a binformat module.

Hence I think that one likely cause may be a 32/64 bit issue. Did you notice
any other module-related build problems on the 32 bit kernel? Earlier you
mentioned that SCTP also was not working.

There are other parts of the (networking) system that also call
request_module, (grep -R request_module net/), for instance if TCP
pluggable congestion control is built as a module -- I take it this is
working correctly?

Gerrit

 CONFIG_64BIT=y
 # CONFIG_X86_32 is not set
 CONFIG_X86_64=y

Re: Protocol not attached

[Leandro Sales]

On Wed, Nov 5, 2008 at 5:27 AM, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
> Hi Leandro
>
> is there any news regarding the CCID/module loading problem on the 64
> bit computer with 32 bit kernel?
>
> I have tried to compile 32 bit at home, but am currently lacking the
> bits and pieces to do all of it since the installation is mostly 64 bit.
>
> I may try this later.
>
> Gerrit
>
> --
>

Hello Gerrit,
    yes! I think that we found the commit that inserted the problem (probably).

    This is the list of commits, the first time that the problem
occurs is in "f76fd327a8b32d3ad5b51639faf6f54d18be0981". I'm sending
to you the tree commits before the BAD that it is working properly.

 - BAD - Gerrit Renker f76fd327a8b32d3ad5b51639faf6f54d18be0981 dccp
ccid-3: Runtime verification of timer resolution
 - GOOD - Tomasz Grobelny 7d1af6a8d935678248d057564e75e1452409a53c
dccp qpolicy: Parameter checking of cmsg qpolicy parameters
 - GOOD - Tomasz Grobelny d6da3511d6b558d0b017777b61dc08b8fbc06ea4
dccp: Policy-based packet dequeueing infrastructure
 - GOOD - Gerrit Renker ddab05568eaa70fc92b2aae957136f188f724e9c dccp:
Clean up slow-path input processing

Regards,
Leandro.

Re: Protocol not attached

[Gerrit Renker]

| > is there any news regarding the CCID/module loading problem on the 64
| > bit computer with 32 bit kernel?
| >
<snip>
| Hello Gerrit,
|     yes! I think that we found the commit that inserted the problem (probably).
| 
|     This is the list of commits, the first time that the problem
| occurs is in "f76fd327a8b32d3ad5b51639faf6f54d18be0981". I'm sending
| to you the tree commits before the BAD that it is working properly.
| 
|  - BAD - Gerrit Renker f76fd327a8b32d3ad5b51639faf6f54d18be0981 dccp
Ah that would explain it. Did you check the logs - if the not-loading
was due to low timer resolution, then there should be a message like
"Timer to coarse (xxx usec), need 10usec".

If that is the case, 
    1. does the problem disappear when commenting out 
       'return -ESOCKTNOSUPPORT' in  ccid3_module_init() below or if
    2. the kernel is compiled with support for high-resolution timers?        


+       if (tp.tv_sec || tp.tv_nsec > DCCP_TIME_RESOLUTION * NSEC_PER_USEC) {
+               printk(KERN_ERR "%s: Timer too coarse (%ld usec), need %u-usec"
+                      " resolution - check your clocksource.\n", __func__,
+                      tp.tv_nsec/NSEC_PER_USEC, DCCP_TIME_RESOLUTION);
+               return -ESOCKTNOSUPPORT;
+       }

Thanks a lot for following this up, this now looks a much more likely cause.

Gerrit

Re: Protocol not attached

[Arnaldo Carvalho de Melo]

Em Thu, Nov 06, 2008 at 04:20:48PM +0100, Gerrit Renker escreveu:
> | > is there any news regarding the CCID/module loading problem on the 64
> | > bit computer with 32 bit kernel?
> | >
> <snip>
> | Hello Gerrit,
> |     yes! I think that we found the commit that inserted the problem (probably).
> | 
> |     This is the list of commits, the first time that the problem
> | occurs is in "f76fd327a8b32d3ad5b51639faf6f54d18be0981". I'm sending
> | to you the tree commits before the BAD that it is working properly.
> | 
> |  - BAD - Gerrit Renker f76fd327a8b32d3ad5b51639faf6f54d18be0981 dccp
> Ah that would explain it. Did you check the logs - if the not-loading
> was due to low timer resolution, then there should be a message like
> "Timer to coarse (xxx usec), need 10usec".
> 
> If that is the case, 
>     1. does the problem disappear when commenting out 
>        'return -ESOCKTNOSUPPORT' in  ccid3_module_init() below or if
>     2. the kernel is compiled with support for high-resolution timers?        
> 
> 
> +       if (tp.tv_sec || tp.tv_nsec > DCCP_TIME_RESOLUTION * NSEC_PER_USEC) {
> +               printk(KERN_ERR "%s: Timer too coarse (%ld usec), need %u-usec"
> +                      " resolution - check your clocksource.\n", __func__,
> +                      tp.tv_nsec/NSEC_PER_USEC, DCCP_TIME_RESOLUTION);
> +               return -ESOCKTNOSUPPORT;
> +       }
> 
> Thanks a lot for following this up, this now looks a much more likely cause.

Makes complete sense, to finish this, Leandro, can you please tell us
what is the value of CONFIG_HZ in your config? 

- Arnaldo

Re: Protocol not attached

[Leandro Sales]

On Thu, Nov 6, 2008 at 3:38 PM, Arnaldo Carvalho de Melo
<acme@redhat.com> wrote:
> Em Thu, Nov 06, 2008 at 04:20:48PM +0100, Gerrit Renker escreveu:
>> | > is there any news regarding the CCID/module loading problem on the 64
>> | > bit computer with 32 bit kernel?
>> | >
>> <snip>
>> | Hello Gerrit,
>> |     yes! I think that we found the commit that inserted the problem (probably).
>> |
>> |     This is the list of commits, the first time that the problem
>> | occurs is in "f76fd327a8b32d3ad5b51639faf6f54d18be0981". I'm sending
>> | to you the tree commits before the BAD that it is working properly.
>> |
>> |  - BAD - Gerrit Renker f76fd327a8b32d3ad5b51639faf6f54d18be0981 dccp
>> Ah that would explain it. Did you check the logs - if the not-loading
>> was due to low timer resolution, then there should be a message like
>> "Timer to coarse (xxx usec), need 10usec".
>>
>> If that is the case,
>>     1. does the problem disappear when commenting out
>>        'return -ESOCKTNOSUPPORT' in  ccid3_module_init() below or if
>>     2. the kernel is compiled with support for high-resolution timers?
>>
>>
>> +       if (tp.tv_sec || tp.tv_nsec > DCCP_TIME_RESOLUTION * NSEC_PER_USEC) {
>> +               printk(KERN_ERR "%s: Timer too coarse (%ld usec), need %u-usec"
>> +                      " resolution - check your clocksource.\n", __func__,
>> +                      tp.tv_nsec/NSEC_PER_USEC, DCCP_TIME_RESOLUTION);
>> +               return -ESOCKTNOSUPPORT;
>> +       }
>>
>> Thanks a lot for following this up, this now looks a much more likely cause.
>
> Makes complete sense, to finish this, Leandro, can you please tell us
> what is the value of CONFIG_HZ in your config?
>
> - Arnaldo
>

CONFIG_HZ_250=y
CONFIG_HZ%0

Re: Protocol not attached

[Leandro Sales]

On Thu, Nov 6, 2008 at 5:46 PM, Leandro Sales <leandroal@gmail.com> wrote:
> On Thu, Nov 6, 2008 at 3:38 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
>> Em Thu, Nov 06, 2008 at 04:20:48PM +0100, Gerrit Renker escreveu:
>>> | > is there any news regarding the CCID/module loading problem on the 64
>>> | > bit computer with 32 bit kernel?
>>> | >
>>> <snip>
>>> | Hello Gerrit,
>>> |     yes! I think that we found the commit that inserted the problem (probably).
>>> |
>>> |     This is the list of commits, the first time that the problem
>>> | occurs is in "f76fd327a8b32d3ad5b51639faf6f54d18be0981". I'm sending
>>> | to you the tree commits before the BAD that it is working properly.
>>> |
>>> |  - BAD - Gerrit Renker f76fd327a8b32d3ad5b51639faf6f54d18be0981 dccp
>>> Ah that would explain it. Did you check the logs - if the not-loading
>>> was due to low timer resolution, then there should be a message like
>>> "Timer to coarse (xxx usec), need 10usec".
>>>
>>> If that is the case,
>>>     1. does the problem disappear when commenting out
>>>        'return -ESOCKTNOSUPPORT' in  ccid3_module_init() below or if
>>>     2. the kernel is compiled with support for high-resolution timers?
>>>
>>>
>>> +       if (tp.tv_sec || tp.tv_nsec > DCCP_TIME_RESOLUTION * NSEC_PER_USEC) {
>>> +               printk(KERN_ERR "%s: Timer too coarse (%ld usec), need %u-usec"
>>> +                      " resolution - check your clocksource.\n", __func__,
>>> +                      tp.tv_nsec/NSEC_PER_USEC, DCCP_TIME_RESOLUTION);
>>> +               return -ESOCKTNOSUPPORT;
>>> +       }
>>>
>>> Thanks a lot for following this up, this now looks a much more likely cause.
>>
>> Makes complete sense, to finish this, Leandro, can you please tell us
>> what is the value of CONFIG_HZ in your config?
>>
>> - Arnaldo
>>
>
> CONFIG_HZ_250=y
> CONFIG_HZ%0
>

For the BAD and for last GOOD using HZ%0 I got:

"warning: #warning Coarse CONFIG_HZ resolution -- higher value
recommended for TFRC."

Leandro.

Re: Protocol not attached

[Leandro Sales]

On Thu, Nov 6, 2008 at 6:04 PM, Leandro Sales <leandroal@gmail.com> wrote:
> On Thu, Nov 6, 2008 at 5:46 PM, Leandro Sales <leandroal@gmail.com> wrote:
>> On Thu, Nov 6, 2008 at 3:38 PM, Arnaldo Carvalho de Melo
>> <acme@redhat.com> wrote:
>>> Em Thu, Nov 06, 2008 at 04:20:48PM +0100, Gerrit Renker escreveu:
>>>> | > is there any news regarding the CCID/module loading problem on the 64
>>>> | > bit computer with 32 bit kernel?
>>>> | >
>>>> <snip>
>>>> | Hello Gerrit,
>>>> |     yes! I think that we found the commit that inserted the problem (probably).
>>>> |
>>>> |     This is the list of commits, the first time that the problem
>>>> | occurs is in "f76fd327a8b32d3ad5b51639faf6f54d18be0981". I'm sending
>>>> | to you the tree commits before the BAD that it is working properly.
>>>> |
>>>> |  - BAD - Gerrit Renker f76fd327a8b32d3ad5b51639faf6f54d18be0981 dccp
>>>> Ah that would explain it. Did you check the logs - if the not-loading
>>>> was due to low timer resolution, then there should be a message like
>>>> "Timer to coarse (xxx usec), need 10usec".
>>>>
>>>> If that is the case,
>>>>     1. does the problem disappear when commenting out
>>>>        'return -ESOCKTNOSUPPORT' in  ccid3_module_init() below or if
>>>>     2. the kernel is compiled with support for high-resolution timers?
>>>>
>>>>
>>>> +       if (tp.tv_sec || tp.tv_nsec > DCCP_TIME_RESOLUTION * NSEC_PER_USEC) {
>>>> +               printk(KERN_ERR "%s: Timer too coarse (%ld usec), need %u-usec"
>>>> +                      " resolution - check your clocksource.\n", __func__,
>>>> +                      tp.tv_nsec/NSEC_PER_USEC, DCCP_TIME_RESOLUTION);
>>>> +               return -ESOCKTNOSUPPORT;
>>>> +       }
>>>>
>>>> Thanks a lot for following this up, this now looks a much more likely cause.
>>>
>>> Makes complete sense, to finish this, Leandro, can you please tell us
>>> what is the value of CONFIG_HZ in your config?
>>>
>>> - Arnaldo
>>>
>>
>> CONFIG_HZ_250=y
>> CONFIG_HZ%0
>>
>
> For the BAD and for last GOOD using HZ%0 I got:
>
> "warning: #warning Coarse CONFIG_HZ resolution -- higher value
> recommended for TFRC."
>
> Leandro.
>

BAD: Using CONFIG_HZ\x1000 "Protocol Not attached"
GOOD: Using CONFIG_HZ\x1000 "OK"

Re: Protocol not attached

[Leandro Sales]

On Thu, Nov 6, 2008 at 6:17 PM, Leandro Sales <leandroal@gmail.com> wrote:
> On Thu, Nov 6, 2008 at 6:04 PM, Leandro Sales <leandroal@gmail.com> wrote:
>> On Thu, Nov 6, 2008 at 5:46 PM, Leandro Sales <leandroal@gmail.com> wrote:
>>> On Thu, Nov 6, 2008 at 3:38 PM, Arnaldo Carvalho de Melo
>>> <acme@redhat.com> wrote:
>>>> Em Thu, Nov 06, 2008 at 04:20:48PM +0100, Gerrit Renker escreveu:
>>>>> | > is there any news regarding the CCID/module loading problem on the 64
>>>>> | > bit computer with 32 bit kernel?
>>>>> | >
>>>>> <snip>
>>>>> | Hello Gerrit,
>>>>> |     yes! I think that we found the commit that inserted the problem (probably).
>>>>> |
>>>>> |     This is the list of commits, the first time that the problem
>>>>> | occurs is in "f76fd327a8b32d3ad5b51639faf6f54d18be0981". I'm sending
>>>>> | to you the tree commits before the BAD that it is working properly.
>>>>> |
>>>>> |  - BAD - Gerrit Renker f76fd327a8b32d3ad5b51639faf6f54d18be0981 dccp
>>>>> Ah that would explain it. Did you check the logs - if the not-loading
>>>>> was due to low timer resolution, then there should be a message like
>>>>> "Timer to coarse (xxx usec), need 10usec".
>>>>>
>>>>> If that is the case,
>>>>>     1. does the problem disappear when commenting out
>>>>>        'return -ESOCKTNOSUPPORT' in  ccid3_module_init() below or if
>>>>>     2. the kernel is compiled with support for high-resolution timers?
>>>>>
>>>>>
>>>>> +       if (tp.tv_sec || tp.tv_nsec > DCCP_TIME_RESOLUTION * NSEC_PER_USEC) {
>>>>> +               printk(KERN_ERR "%s: Timer too coarse (%ld usec), need %u-usec"
>>>>> +                      " resolution - check your clocksource.\n", __func__,
>>>>> +                      tp.tv_nsec/NSEC_PER_USEC, DCCP_TIME_RESOLUTION);
>>>>> +               return -ESOCKTNOSUPPORT;
>>>>> +       }
>>>>>
>>>>> Thanks a lot for following this up, this now looks a much more likely cause.
>>>>
>>>> Makes complete sense, to finish this, Leandro, can you please tell us
>>>> what is the value of CONFIG_HZ in your config?
>>>>
>>>> - Arnaldo
>>>>
>>>
>>> CONFIG_HZ_250=y
>>> CONFIG_HZ%0
>>>
>>
>> For the BAD and for last GOOD using HZ%0 I got:
>>
>> "warning: #warning Coarse CONFIG_HZ resolution -- higher value
>> recommended for TFRC."
>>
>> Leandro.
>>
>
> BAD: Using CONFIG_HZ\x1000 "Protocol Not attached"
> GOOD: Using CONFIG_HZ\x1000 "OK"
>

Tests using High Resolution Timers using BAD:

100hz OK
250hz OK
1000hz OK

Leandro.

Re: Protocol not attached

[Gerrit Renker]

Arnaldo, Leandro, -
| >> For the BAD and for last GOOD using HZ%0 I got:
| >>
| >> "warning: #warning Coarse CONFIG_HZ resolution -- higher value
| >> recommended for TFRC."
| >>
| >> Leandro.
| >>
| >
| > BAD: Using CONFIG_HZ\x1000 "Protocol Not attached"
| > GOOD: Using CONFIG_HZ\x1000 "OK"
| >
| 
| Tests using High Resolution Timers using BAD:
| 
| 100hz OK
| 250hz OK
| 1000hz OK
| 
This confirms that the cause of the problem was in not enabling
High-Resolution timers. There will then be the warning message in
the system logs saying that the timer resolution is too low.

I tried to find Leandros .config file again, it seems that high-resolution
timers were not enabled; the only other possibility is when passing
clocksource=jiffies (or something else coarse-grained).

The HZ variable is not really relevant here; you are still seeing this
messages since your version of the test tree is older than 2 weeks:
http://marc.info/?l‹cp&m\x122451741426680&w=2

The fact that the CCID-3 module is not loaded when the timer resolution
is too coarse is not a bug, it is there to avoid problems that result
when using coarse-grained timers on high-speed interfaces: most PCs
laptops now come with Gigabit Ethernet per default, local loopback also
operates at high speeds; when using such interfaces I noticed several
problems as described in the commit message, 
http://eden-feed.erg.abdn.ac.uk/cgi-bin/gitweb.cgi?p‹cp_exp.git;a=commitdiff;hBc46151aedc99689341ac73131cd56c2aec55c4

Maybe it is a good idea to rethink the whole high-resolution timer
issue. I can see only two ways:

 (1) Consistently use coarse-grained timers everywhere (jiffy resolution)
     --------------------------------------------------------------------	
     Ian McDonald suggested this, and I can see the advantages - we could
     unify RTT measurement for all the CCIDs, use a simpler implementation.

 (2) Consistentlly use high-resolution timers everywhere
     ---------------------------------------------------
     This would require to use the above protection in general. In a
     discussion about the build warning, Dave Miller suggested
     converting to high-resolution timers and he is right about it -
     if we decide to stick with high-resolution timers - since mixing
     high-resolution code (currently the computation of X_recv and RTT)
     with low-resolution code (dccp_xmit_timer) is neither here nor
     there and gives bad performance.

Arnaldo, Leandro and others - it would be good to have input on this. I
have looked into the conversion to high-resolution timers, but I have 
doubt that it will improve the performance of CCID-3. 

From earlier discussion I know, Arnaldo, that you were in favour of
keeping the resolution high. But if we want to do that then I think we
need to convert the rest to high-resolution timers also. Or decide to
use (1).

Gerrit
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html