RE: regression with 2.6.12 kernel

Confirming I also see these on a 2.6.12 kernel, in
my case on x86_64.

>I'm seeing 12 new failures with a 2.6.12 kernel:
>
>/tset/LSB.os/procprim/exec_L/T.execl_L 7 FAIL
>/tset/LSB.os/procprim/exec_L/T.execle_L 7 FAIL
>/tset/LSB.os/procprim/exec_L/T.execlp_L 7 FAIL
>/tset/LSB.os/procprim/exec_L/T.execv_L 7 FAIL
>/tset/LSB.os/procprim/exec_L/T.execve_L 7 FAIL
>/tset/LSB.os/procprim/exec_L/T.execvp_L 7 FAIL
>/tset/POSIX.os/procprim/exec/T.execl 30 FAIL
>/tset/POSIX.os/procprim/exec/T.execle 30 FAIL
>/tset/POSIX.os/procprim/exec/T.execlp 30 FAIL
>/tset/POSIX.os/procprim/exec/T.execv 30 FAIL
>/tset/POSIX.os/procprim/exec/T.execve 30 FAIL
>/tset/POSIX.os/procprim/exec/T.execvp 30 FAIL
>
>The "7" tests all return:
>
>For ITIMER_REAL: it_value.tv_sec reset incorrectly by exec:
>expected value 0; observed value 0

This is a real failure, but a bogus diagnostic.  The code
checks if tv_sec is 0 and treats that as failure, indicating
the timer value has been cleared.  When it goes to print a
message, it has a hardcoded the value '0' instead of printing 
what it expects - a bug is being filed on that, but that has
nothing to do with why this new failure has cropped up.