On Thu, 2007-01-04 at 16:01 +0100, Steven Scholz wrote:
> > cyclictest does not need any extra functionality. You only need a new
> > glibc if you want to use priority inheritance mutexes.
>
> So IIUC the cyclictest should run and give results even on kernels with no
> real time, preempt, lowlatency support at all?
Right.
> 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
There is neither a call of timer_create() nor of timer_settime(). So the
posix timer is not setup, which results in the endless wait for the
signal.
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 ?
tglx
-
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
