LFS 6.5 6.9. Glibc-2.10.1 test error
The system is a AMD phenom II 820 X4 Quad core with 8 GB ram Host is Slackware 12.2 - only sees 4 GB Ram non pae kernel Is this ok? gcc tst-cpuclock2.c -c -std=gnu99 -fgnu89-inline -O2 -O3 -Wall -Winline -Wwrite-strings -fmerge-all-constants -g -march=i486 -mtune=native -pipe -Wstrict-prototypes -mpreferred-stack-boundary=2 -I../include -I/Build/glibc-build/rt -I/Build/glibc-build -I../sysdeps/i386/elf -I../nptl/sysdeps/unix/sysv/linux/i386/i686 -I../nptl/sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux/i386 -I../nptl/sysdeps/unix/sysv/linux -I../nptl/sysdeps/pthread -I../sysdeps/pthread -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../nptl/sysdeps/unix/sysv -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../nptl/sysdeps/unix -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../nptl/sysdeps/i386/i686 -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../nptl/sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../nptl/sysdeps/i386 -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -I../nptl -I.. -I../libio -I. -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DNOT_IN_libc=1-o /Build/glibc-build/rt/tst-cpuclock2.o -MD -MP -MF /Build/glibc-build/rt/tst-cpuclock2.o.dt -MT /Build/glibc-build/rt/tst-cpuclock2.o gcc -nostdlib -nostartfiles -o /Build/glibc-build/rt/tst-cpuclock2 -Wl,-dynamic-linker=/lib/ld-linux.so.2 -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both /Build/glibc-build/csu/crt1.o /Build/glibc-build/csu/crti.o `gcc --print-file-name=crtbegin.o` /Build/glibc-build/rt/tst-cpuclock2.o /Build/glibc-build/rt/librt.so /Build/glibc-build/nptl/libpthread_nonshared.a /Build/glibc-build/nptl/libpthread.so -Wl,-rpath-link=/Build/glibc-build:/Build/glibc-build/math:/Build/glibc-build/elf:/Build/glibc-build/dlfcn:/Build/glibc-build/nss:/Build/glibc-build/nis:/Build/glibc-build/rt:/Build/glibc-build/resolv:/Build/glibc-build/crypt:/Build/glibc-build/nptl /Build/glibc-build/libc.so.6 /Build/glibc-build/libc_nonshared.a -lgcc -Wl,--as-needed -lgcc_s -Wl,--no-as-needed `gcc --print-file-name=crtend.o` /Build/glibc-build/csu/crtn.o GCONV_PATH=/Build/glibc-build/iconvdata LC_ALL=C /Build/glibc-build/elf/ld-linux.so.2 --library-path /Build/glibc-build:/Build/glibc-build/math:/Build/glibc-build/elf:/Build/glibc-build/dlfcn:/Build/glibc-build/nss:/Build/glibc-build/nis:/Build/glibc-build/rt:/Build/glibc-build/resolv:/Build/glibc-build/crypt:/Build/glibc-build/nptl /Build/glibc-build/rt/tst-cpuclock2 > /Build/glibc-build/rt/tst-cpuclock2.out make[4]: *** [/Build/glibc-build/rt/tst-cpuclock2.out] Error 1 The tst-cpuclock1.o was fine Chapter 5 was fine, I ran the test and did not see any problems there. Did some searching on the web and I believe it is not a problem, am I correct? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 6.9. Glibc-2.10.1 test error
Baho Utot wrote: > The system is a AMD phenom II 820 X4 Quad core with 8 GB ram > Host is Slackware 12.2 - only sees 4 GB Ram non pae kernel > > Is this ok? > > /Build/glibc-build/rt/tst-cpuclock2 > > /Build/glibc-build/rt/tst-cpuclock2.out > make[4]: *** [/Build/glibc-build/rt/tst-cpuclock2.out] Error 1 > The tst-cpuclock1.o was fine > > Chapter 5 was fine, I ran the test and did not see any problems there. > > Did some searching on the web and I believe it is not a problem, am I > correct? Probably. What aare the contents of your /Build/glibc-build/rt/tst-cpuclock2.out file. It should be only one or two lines. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 6.9. Glibc-2.10.1 test error
Bruce Dubbs wrote: > Baho Utot wrote: > >> The system is a AMD phenom II 820 X4 Quad core with 8 GB ram >> Host is Slackware 12.2 - only sees 4 GB Ram non pae kernel >> >> Is this ok? >> >> /Build/glibc-build/rt/tst-cpuclock2 > >> /Build/glibc-build/rt/tst-cpuclock2.out >> make[4]: *** [/Build/glibc-build/rt/tst-cpuclock2.out] Error 1 >> > > >> The tst-cpuclock1.o was fine >> >> Chapter 5 was fine, I ran the test and did not see any problems there. >> >> Did some searching on the web and I believe it is not a problem, am I >> correct? >> > > Probably. What aare the contents of your > /Build/glibc-build/rt/tst-cpuclock2.out file. It should be only one or > two lines. > >-- Bruce > > cat /mnt/lfs/Build/glibc-build/rt/tst-cpuclock2.out live thread clock fffdd58e resolution 0.1 live thread before sleep => 0.53078 self thread before sleep => 0.000169320 live thread after sleep => 0.501525776 self thread after sleep => 0.000186263 process before - after 500355090 outside reasonable range (501472698) Then make bails make[4]: [/Build/glibc-build/posix/annexc.out] Error 1 (ignored) make[4]: *** [/Build/glibc-build/rt/tst-cpuclock2.out] Error 1 make[3]: *** [rt/tests] Error 2 make[2]: *** [check] Error 2 I ran this compile with -j4, I have tried w/o -jx and various CFLAGS, always result is the same How do I know if all the tests completed (even if some failed) and it did not bail early? Thanks -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 6.9. Glibc-2.10.1 test error
On Wed, Feb 17, 2010 at 9:16 AM, Baho Utot wrote: > The system is a AMD phenom II 820 X4 Quad core with 8 GB ram This seems to be a common Phenom II problem, as Trac user ringlis got the same error, albeit with LFS 6.6-rc1 and Glibc-2.11.1. Of cource, it could be heavy system load or for other reasons, but other than that, I can't confirm this, as I don't have a Phenom II, but I would love a Phenom II 3.4GHZ, but when I do get one, I'll try it out. -- William Immendorf The ultimate in free computing. Messages in plain text, please, no HTML. -- "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman PS: You can get the processor that I mentioned here: http://www.newegg.com/Product/Product.aspx?Item=N82E16819103727 -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 6.9. Glibc-2.10.1 test error
William Immendorf wrote: > On Wed, Feb 17, 2010 at 9:16 AM, Baho Utot wrote: > >> The system is a AMD phenom II 820 X4 Quad core with 8 GB ram >> > This seems to be a common Phenom II problem, as Trac user ringlis got > the same error, albeit with LFS 6.6-rc1 and Glibc-2.11.1. Of cource, > it could be heavy system load or for other reasons, but other than > that, I can't confirm this, as I don't have a Phenom II, but I would > love a Phenom II 3.4GHZ, but when I do get one, I'll try it out. > > I don't understand how a quad core would be "under heavy system load", I suppose it is possible, I just haven't seen it. I haven't seen mine with all 4 cores maxed out. Even when I do a make -j4 it still is at about 20%-30% idle ( using top 1) on all 4 cores. When using cpu scaling and I have is set to run the core at 800 MHz I still have plenty of power as it never hits full rated speed, except on a build and then is goes full speed and back to idle (800 MHz) very fast. Typical on the system with i686 system: KDE 3.5.10 with thunderbird, konqueror ( 6 windows ) and knode running is: top - 15:31:19 up 9 min, 8 users, load average: 0.08, 0.12, 0.10 Tasks: 129 total, 1 running, 128 sleeping, 0 stopped, 0 zombie Cpu0 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu1 : 0.3%us, 0.0%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu2 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu3 : 2.0%us, 0.0%sy, 0.0%ni, 97.7%id, 0.0%wa, 0.3%hi, 0.0%si, 0.0%st Mem: 3372656k total, 506432k used, 2866224k free, 1672k buffers Swap: 1517752k total,0k used, 1517752k free, 251308k cached Running Slamd64 (multi-lib) is about the same except it's using all 8 GB ram. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 6.9. Glibc-2.10.1 test error
Baho Utot wrote:
> cat /mnt/lfs/Build/glibc-build/rt/tst-cpuclock2.out
> live thread clock fffdd58e resolution 0.1
> live thread before sleep => 0.53078
> self thread before sleep => 0.000169320
> live thread after sleep => 0.501525776
> self thread after sleep => 0.000186263
> process before - after 500355090 outside reasonable range (501472698)
What this test is doing is checking the difference between thread times
and process times. The values above are nanoseconds. It's saying that
the process time is shorter than the thread time (by slightly more than
one millisecond). This is a breakdown of the code:
clock_gettime (process_clock, &process_before)
clock_gettime (th_clock, &before)
clock_gettime (my_thread_clock, &me_before)
struct timespec sleeptime = { .tv_nsec = 5 };
nanosleep (&sleeptime, NULL)
clock_gettime (th_clock, &after)
clock_gettime (process_clock, &process_after)
clock_gettime (my_thread_clock, &me_after)
What appears to be happening is that the main process sleeps while the
thread doesn't. The thread time is thus 501525775 ns, The limits here
are 1 to 6 ( .1 to .6 seconds) and it passes.
The time for the my_thread_clock should be less than 0.1 second and that
passes. No data is given about that though. I added a printout and it
was generally about 12000 ns.
Google suggests that being in chroot may be a factor.
To check that out, I rebuilt glibc on my system outside of chroot. I
was able to duplicate the error.
live thread before sleep => 0.57951
self thread before sleep => 0.000168869
live thread after sleep => 0.500118785
self thread after sleep => 0.000180958
process before - after 499973217 outside reasonable range (500060834)
And on other runs, I get:
live thread clock fffc65f6 resolution 0.1
live thread before sleep => 0.30323
self thread before sleep => 0.000120303
live thread after sleep => 0.500091485
self thread after sleep => 0.000130988
process before - after 499295588 outside reasonable range (500061162)
bdu...@core2-64 [ /mnt/lfs/sources/glibc-build ]$ rt/tst-cpuclock2
live thread clock fffc65de resolution 0.1
live thread before sleep => 0.04984
self thread before sleep => 0.000112728
live thread after sleep => 0.500025515
self thread after sleep => 0.000122332
So it is intermittent timing error. Here is another failure after I
modified the test to print out more data:
process before sleep => 0.000141026
live thread before sleep => 0.34383
self thread before sleep => 0.000118320
live thread after sleep => 0.500092632
process after sleep => 0.500097116
self thread after sleep => 0.000130039
process before - after 499956090 outside reasonable range (500058249)
thread before - after 500058249
process before - after 499956090
my_diff before - after 11719
In this case, the timers say that the process was 102159 ns or about
1/1000 second faster than the thread. This may have some implications
in certain real time applications, but I don't see an issue for LFS.
A pass looks like:
thread before - after 505293557
process before - after 505305328
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: LFS 6.5 6.9. Glibc-2.10.1 test error
Baho Utot wrote: > I don't understand how a quad core would be "under heavy system load", You're right. I've done a bit of research and testing today and I'm rewriting the error sections. "The nptl/tst-clock2, nptl/tst-attr3, and rt/tst-cpuclock2 tests have been known to fail. The reason is not completely understood, but indications are that minor timing issues can trigger these failures." -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 6.9. Glibc-2.10.1 test error
Bruce Dubbs wrote:
> Baho Utot wrote:
>
>
>> cat /mnt/lfs/Build/glibc-build/rt/tst-cpuclock2.out
>> live thread clock fffdd58e resolution 0.1
>>
>
>
>> live thread before sleep => 0.53078
>> self thread before sleep => 0.000169320
>> live thread after sleep => 0.501525776
>> self thread after sleep => 0.000186263
>>
>
>
>> process before - after 500355090 outside reasonable range (501472698)
>>
>
> What this test is doing is checking the difference between thread times
> and process times. The values above are nanoseconds. It's saying that
> the process time is shorter than the thread time (by slightly more than
> one millisecond). This is a breakdown of the code:
>
> clock_gettime (process_clock, &process_before)
> clock_gettime (th_clock, &before)
> clock_gettime (my_thread_clock, &me_before)
>
> struct timespec sleeptime = { .tv_nsec = 5 };
> nanosleep (&sleeptime, NULL)
>
> clock_gettime (th_clock, &after)
> clock_gettime (process_clock, &process_after)
> clock_gettime (my_thread_clock, &me_after)
>
>
> What appears to be happening is that the main process sleeps while the
> thread doesn't. The thread time is thus 501525775 ns, The limits here
> are 1 to 6 ( .1 to .6 seconds) and it passes.
>
> The time for the my_thread_clock should be less than 0.1 second and that
> passes. No data is given about that though. I added a printout and it
> was generally about 12000 ns.
>
> Google suggests that being in chroot may be a factor.
>
> To check that out, I rebuilt glibc on my system outside of chroot. I
> was able to duplicate the error.
>
> live thread before sleep => 0.57951
> self thread before sleep => 0.000168869
> live thread after sleep => 0.500118785
> self thread after sleep => 0.000180958
> process before - after 499973217 outside reasonable range (500060834)
>
> And on other runs, I get:
>
> live thread clock fffc65f6 resolution 0.1
> live thread before sleep => 0.30323
> self thread before sleep => 0.000120303
> live thread after sleep => 0.500091485
> self thread after sleep => 0.000130988
> process before - after 499295588 outside reasonable range (500061162)
>
> bdu...@core2-64 [ /mnt/lfs/sources/glibc-build ]$ rt/tst-cpuclock2
> live thread clock fffc65de resolution 0.1
> live thread before sleep => 0.04984
> self thread before sleep => 0.000112728
> live thread after sleep => 0.500025515
> self thread after sleep => 0.000122332
>
> So it is intermittent timing error. Here is another failure after I
> modified the test to print out more data:
>
> process before sleep => 0.000141026
> live thread before sleep => 0.34383
> self thread before sleep => 0.000118320
> live thread after sleep => 0.500092632
> process after sleep => 0.500097116
> self thread after sleep => 0.000130039
> process before - after 499956090 outside reasonable range (500058249)
> thread before - after 500058249
> process before - after 499956090
> my_diff before - after 11719
>
> In this case, the timers say that the process was 102159 ns or about
> 1/1000 second faster than the thread. This may have some implications
> in certain real time applications, but I don't see an issue for LFS.
>
> A pass looks like:
>
> thread before - after 505293557
> process before - after 505305328
>
>-- Bruce
>
Thanks for taking the time to check this out.
I have looked at CLFS glibc build and builds from arch linux and tried
various CFLAGS to no CFLAGS and nothing seems to change the out come
always get the same results.
So I believe it could possibly be due to the hardware?
Any way I have went ahead and installed 6.9 glibc and it came back with:
CC="gcc" /usr/bin/perl scripts/test-installation.pl /Build/glibc-build/
Your new glibc installation seems to be ok.
make[2]: Leaving directory `/Build/glibc-2.10.1'
make[1]: Leaving directory `/Build/glibc-build'
So I am thinking the build is fine.
I'll keep a look out for strange happenings later in the builds ;-)
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: LFS 6.5 6.9. Glibc-2.10.1 test error
Bruce Dubbs wrote: > Baho Utot wrote: > > >> I don't understand how a quad core would be "under heavy system load", >> > > You're right. I've done a bit of research and testing today and I'm > rewriting the error sections. > > "The nptl/tst-clock2, nptl/tst-attr3, and rt/tst-cpuclock2 > tests have been known to fail. The reason is not completely understood, > but indications are that minor timing issues can trigger these failures." > >-- Bruce > > Wow... a light came on nptl - threads rt- real time Any way Thanks -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
