Re: powerpc: step-jump-cont failure (Was: [PATCH] utrace: don't set -ops = utrace_detached_ops lockless)
Thanks for pointing out. Sorry for the false alarm.
Re: Tests Failures on PPC64
I bet it fails without utrace too? (please don't tell it doesn't ;) Yes. Did you see it fails on other ppc64 machines? No. Ah. I didn't notice you did biarch-check, not check. Will take a look later... Thanks in advance, CAI Qian
Re: [PATCH] utrace: don't set -ops = utrace_detached_ops lockless
Could you please confirm that if you revert this [PATCH] utrace: don't set -ops = utrace_detached_ops lockless change the kernel passes the test? This is just impossible that this patch could make any difference for this test-case. No, it is the same. It is true also for kernels turned off CONFIG_UTRACE. Unfortunately, I can't extend the reservation. RHTS had an outage yesterday, and now seems back to normal. Did you change anything else (except kernel) on this machine? Not I am aware of. I will re-install this machine to have a probably clearer environment, and let you know the outcome shortly. Thanks, CAI Qian
Re: [PATCH] utrace: don't set -ops = utrace_detached_ops lockless
I was going to try again, but noticed you already recompiled and booted the kernel. I see ./test is running and there is nothing bad in dmesg ;) Yes, it looks good so far. Ptrace tests also does not show any regression. I kicked off a few tests on other platform, so hopefully have more information shortly.
Re: step-into-handler.c compilation failure on ppc64
How about this? Thanks. Fixed.
ptrace tests failed to compile on i686
+ make check make[1]: Entering directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests' Making check in tests make[2]: Entering directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests/tests' gcc -m64 -DPACKAGE_NAME=\ptrace\ regression\ test\ suite\ -DPACKAGE_TARNAME=\ptrace-tests\ -DPACKAGE_VERSION=\0.1\ -DPACKAGE_STRING=\ptrace\ regression\ test\ suite\ 0.1\ -DPACKAGE_BUGREPORT=\utrace-de...@redhat.com\ -DPACKAGE=\ptrace-tests\ -DVERSION=\0.1\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -D_FILE_OFFSET_BITS=64 -I. \ -std=gnu99 -Wall -Werror -g -O2 -o erestartsys-debuggee erestartsys-debuggee.c erestartsys-debuggee.c:1: sorry, unimplemented: 64-bit mode not compiled in make[2]: *** [erestartsys-debuggee] Error 1 make[2]: Leaving directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests' + '[' i386 = x86_64 ']' + '[' i386 = ppc64 ']' + tee -a /tmp/tmp.yicBDv + echo '* run the crasher.' * run the crasher. + tee -a /tmp/tmp.yicBDv + make xcheck make[1]: Entering directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests' make[2]: Entering directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests' Making check in tests make[3]: Entering directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests/tests' gcc -m64 -DPACKAGE_NAME=\ptrace\ regression\ test\ suite\ -DPACKAGE_TARNAME=\ptrace-tests\ -DPACKAGE_VERSION=\0.1\ -DPACKAGE_STRING=\ptrace\ regression\ test\ suite\ 0.1\ -DPACKAGE_BUGREPORT=\utrace-de...@redhat.com\ -DPACKAGE=\ptrace-tests\ -DVERSION=\0.1\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -D_FILE_OFFSET_BITS=64 -I. \ -std=gnu99 -Wall -Werror -g -O2 -o erestartsys-debuggee erestartsys-debuggee.c erestartsys-debuggee.c:1: sorry, unimplemented: 64-bit mode not compiled in make[3]: *** [erestartsys-debuggee] Error 1 make[3]: Leaving directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests/tests' make[2]: *** [check-recursive] Error 1 make[1]: *** [xcheck] Error 2 make[2]: Leaving directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests' make[1]: Leaving directory `/mnt/tests/kernel/misc/ptrace-testsuite/ptrace-tests'
Re: ptrace tests failed to compile on i686
OK, I think I should not use ./configure --with-biarch on i686. Sorry for the noise.
Re: utrace-ptrace gdb testsuite tesults
Followed the differences found by Qian and verified none of them (did not verify the ppc suspicious one) has any regression in GDB testsuite. I did not reproduce the original possible regression seen on ppc64 RHEL6 systems. The kernel was build directly from roland's git tree with and without CONFIG_UTRACE. $ diff -u noutrace/gdb-64.sum utrace/gdb-64.sum --- noutrace/gdb-64.sum 2009-11-30 16:29:16.793769391 +0800 +++ utrace/gdb-64.sum 2009-11-30 16:28:06.249892712 +0800 @@ -1,4 +1,4 @@ -Test Run By root on Mon Nov 30 02:27:53 2009 +Test Run By root on Mon Nov 30 02:27:59 2009 Native configuration is powerpc64-unknown-linux-gnu === gdb tests === @@ -4046,7 +4046,7 @@ PASS: gdb.base/foll-fork.exp: default parent follow, no catchpoints PASS: gdb.base/foll-fork.exp: set follow parent PASS: gdb.base/foll-fork.exp: explicit show parent follow, no catchpoints -PASS: gdb.base/foll-fork.exp: explicit parent follow, no catchpoints +FAIL: gdb.base/foll-fork.exp: (timeout) explicit parent follow, no catchpoints PASS: gdb.base/foll-fork.exp: set follow child PASS: gdb.base/foll-fork.exp: explicit show child follow, no catchpoints PASS: gdb.base/foll-fork.exp: explicit child follow, no catchpoints @@ -14764,7 +14764,7 @@ PASS: gdb.threads/attach-stopped.exp: threaded: set file, before attach1 to stopped process (re-read) PASS: gdb.threads/attach-stopped.exp: threaded: attach1 to stopped, after setting file PASS: gdb.threads/attach-stopped.exp: threaded: attach1 to stopped bt -FAIL: gdb.threads/attach-stopped.exp: threaded: attach1, exit leaves process stopped +PASS: gdb.threads/attach-stopped.exp: threaded: attach1, exit leaves process stopped PASS: gdb.threads/attach-stopped.exp: threaded: attach2 to stopped, after setting file PASS: gdb.threads/attach-stopped.exp: threaded: attach2 to stopped bt PASS: gdb.threads/attach-stopped.exp: continue (threaded: attach2 continue) I'll try to schedule it on a few other ppc64 systems to see if make any difference. CAI Qian
