ubench hang on IA64 HPUX box

[I_M]

Hi

When I run ubench(PA binary) on HP-UX 11.22(1.6),then it never ends.

When I run ubench(IA binary) on HP-UX 11.22(1.6), then it finished about 3min.

Has anyone tried this before?
http://www.phystech.com/download/ubench.html

Regards,

[Dietmar Konermann]

Hi!

Is PHSS_27292 installed? Maybe the SIGALRM is not delivered to the process. Sounds like Aries bug JAGae34834:

Aries does not correctly deliver signals to exec'ed process.

Regards...
Dietmar.

[I_M]

Hello
Thanks for the reply

I have installed the patch that Dietmar mentioned and run the ubench again. Still PA binary never stop .
I wonder still something wrong with "Aries".

Regards,

[Dietmar Konermann]

Wow... not an easy one.

I duplicated the problem on our system and indeed, I _believe_ we are hitting a new Aries problem.

The ubench sets an alarm() (180 seconds) and starts the cpu test. When it is signaled by SIGALRM, then a 2nd alarm() is set and the memory test starts. This second alarm never reaches the process.

The problem can be duplicated using this small example:

#include
#include
#include
#include

jmp_buf env;

void sigHandler(sig)
int sig;
{
siglongjmp(env,sig);
}


main()
{
int i;
struct sigaction action;
action.sa_handler= &sigHandler;
action.sa_flags = 0;
sigaction(SIGINT,&action,NULL);

if ( (i=sigsetjmp(env,0xffff)) ) {
printf ("Signal %d\n", i);
}

while (1);
}


When you run it then "Signal 2" should be printed each time you hit Ctrl-C. This usually works fine, unless you compile it as 64bit (+DD64) and run this under Aries. Here we get only a single SIGINT for the 1st Ctrl-C! No more.

So I assume there is still a signal handling problem with Aries, 64bit only. I will raise a Change Request to get this addressed.

In the meantime you can run ubench using the -c and -m options separately.

Best regards...
Dietmar.

[I_M]

Hi

Thanks for the support :)
I hope HP will fix this problem.

Regards,

[Dietmar Konermann]

I received this morning a confirmation that this is problem (JAGae51381) will be fixed with the next Aries cumulative patch (and in 11.23 also, of course).

Best regards...
Dietmar.