make check problems

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

make check problems

S.Çağlar Onur-2
Hi;

Following tests (nptl/tst-mutexpi5, nptl/tst-mutexpi5a, nptl/tst-mutexpi6,
nptl/tst-robustpi, rt/tst-cpuclock1) failed for 20070317 snapshot on
kernel-2.6.20.4 with binutils-2.17.50.0.14 and gcc-4.2.0 RC1.

Is it safe to ignore these or they are indicates a kernel-side problem like
[1] to report LKML (assuming my toolchain not borked)?

[caglar@zangetsu]
[/var/pisi/glibc-2.5-17/work/build-default-i686-pc-linux-gnu-nptl]> ./testrun.sh
nptl/tst-mutexpi5
timedlock error != ETIMEDOUT: 35

[caglar@zangetsu]
[/var/pisi/glibc-2.5-17/work/build-default-i686-pc-linux-gnu-nptl]> ./testrun.sh
nptl/tst-mutexpi5a
timedlock error != ETIMEDOUT: 35

[caglar@zangetsu]
[/var/pisi/glibc-2.5-17/work/build-default-i686-pc-linux-gnu-nptl]> ./testrun.sh
nptl/tst-mutexpi6
2nd mutex_lock returned
Expected signal 'Alarm clock' from child, got none

[caglar@zangetsu]
[/var/pisi/glibc-2.5-17/work/build-default-i686-pc-linux-gnu-nptl]> ./testrun.sh
nptl/tst-robustpi8
mutex_timedlock of 84 in thread 1 failed with 35
child did not die of a signal in round 1

[caglar@zangetsu]
[/var/pisi/glibc-2.5-17/work/build-default-i686-pc-linux-gnu-nptl]> ./testrun.sh
rt/tst-cpuclock1
clock_getcpuclockid on dead PID 19329 => Invalid argument
live PID 19330 clock fffda3ea resolution 0.000000001
live PID 19330 before sleep => 0.000000000
live PID 19330 after sleep => 0.199000000
dead PID 19330 => 0.300000000
clock_gettime on reaped PID 19330 clock fffda3ea => Invalid argument
clock_getres on reaped PID 19330 clock fffda3ea => Invalid argument

[1] http://lkml.org/lkml/2006/8/4/106
--
S.Çağlar Onur <[hidden email]>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

attachment0 (196 bytes) Download Attachment