Hi Thomas,
>> Just tried it on a plain 2.6.19. posix timer version still hangs ...
>
> That's caused by user space breakage. Looking at the strace you sent:
>
> [pid 932] getpid() = 932
> [pid 932] rt_sigprocmask(SIG_SETMASK, [ALRM RTMIN], NULL, 8) = 0
> [pid 932] gettid() = 932
> [pid 932] rt_sigprocmask(SIG_BLOCK, [ALRM], NULL, 8) = 0
> [pid 932] sched_setscheduler(0, SCHED_FIFO, { 80 }) = 0
> [pid 932] clock_gettime(CLOCK_MONOTONIC, {325, 223507890}) = 0
> [pid 932] rt_sigaction(SIGALRM, {0xb7ed72c0, ~[], 0}, NULL, 8) = 0
> [pid 932] rt_sigprocmask(SIG_BLOCK, NULL, [ALRM RTMIN], 8) = 0
> [pid 932] rt_sigsuspend(~[ALRM RT_1] <unfinished ...>
> [pid 930] <... nanosleep resumed> NULL) = 0
Ah. Thanks for that hint!
> This looks like a serious problem with your cross compiler / glibc
> setup. Can you compile cyclictest on one of your desktop machines and
> link it statically ?
gcc -Wall -O2 -lpthread -lrt cyclictest.c -o cyclictest -static
results in
/tmp/ccIsApGI.o: In function `main':
cyclictest.c:(.text+0x4a2): undefined reference to `pthread_create'
cyclictest.c:(.text+0x6d9): undefined reference to `pthread_kill'
cyclictest.c:(.text+0x6f0): undefined reference to `pthread_join'
/tmp/ccIsApGI.o: In function `timerthread':
cyclictest.c:(.text+0x839): undefined reference to `clock_gettime'
cyclictest.c:(.text+0x881): undefined reference to `timer_settime'
cyclictest.c:(.text+0x90c): undefined reference to `clock_gettime'
cyclictest.c:(.text+0xa7b): undefined reference to `clock_gettime'
cyclictest.c:(.text+0xa8c): undefined reference to `clock_nanosleep'
cyclictest.c:(.text+0xb08): undefined reference to `timer_delete'
cyclictest.c:(.text+0xb79): undefined reference to `clock_gettime'
cyclictest.c:(.text+0xbd8): undefined reference to `clock_nanosleep'
cyclictest.c:(.text+0xc37): undefined reference to `timer_create'
collect2: ld returned 1 exit status
???
Shouldn't pthread_* be in libpthread?
Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
