pete Spam-Avoider wrote: > The following line appeared on virtual console 1 during > testing of glic-2.13 in BK6.8_Ch6.9.1: > > [ 5525.196801] Maximum lock depth 1024 reached task: ld-linux.so.2 (8378) > > The line was also visible as the last line produced by 'dmesg'. > > The line did not appear in virtual console 4 in which the > glibc-2.13 was being tested. > > Using 'grep Error glibc-check-log' from Ch.6.9.1 produced only > the "posix/annexc.out" error. > > Can i ignore the above line and install glibc-2.13?
Yes. It was probably testing the lock depth. On my system, I regularly get several messages like this on the console: [80858.346532] ld-linux-x86-64[28543] trap invalid opcode ip:7fa048add799 sp:7fff8da9f238 error:0 in ld.so[7fa048aca000+1f000] [81017.700718] ld-linux-x86-64[13712] trap invalid opcode ip:2ad6a370cbce sp:7fff0fc7d6a8 error:0 in tst-auditmod4b.so[2ad6a370c000+2000] [81017.833858] ld-linux-x86-64[13736] trap invalid opcode ip:2b3786686b7e sp:7fffd9fbc1e8 error:0 in tst-auditmod6b.so[2b3786686000+2000] [81017.901918] ld-linux-x86-64[13748] trap invalid opcode ip:2b62d2424b61 sp:7fffec1b55a8 error:0 in tst-auditmod7b.so[2b62d2424000+2000] [94923.977423] make[11892]: segfault at 133c ip 00007f488f2acc0b sp 00007fff063f73f0 error 4 in ld-2.13.so (deleted)[7f488f2a4000+1f000] It's just testing AFAICT or bugs in the tests. These lines don't appear outside of the tests. You can also see them in dmesg. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
