RE: testsuits on IA64

RE: testsuits on IA64

[Keshavamurthy, Anil S]

[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]

Will, 
I am attaching log file. Your help is appreciated.

Thanks,
Anil Keshavamurthy

>-----Original Message-----
>From: systemtap-owner@sourceware.org 
>[mailto:systemtap-owner@sourceware.org] On Behalf Of William Cohen
>Sent: Friday, November 04, 2005 3:04 PM
>To: Keshavamurthy, Anil S
>Cc: Frank Ch. Eigler; systemtap@sources.redhat.com
>Subject: Re: testsuits on IA64
>
>Keshavamurthy Anil S wrote:
>> On Fri, Nov 04, 2005 at 02:00:15PM -0500, Frank Ch. Eigler wrote:
>> 
>>>Hi -
>>>
>>>
>>>>I am trying to run testsuits (dejagnu) on IA64 and most of the tests
>>>>fails on Ia64 with FAIL : timeout.
>>>>How do I increase the timeout value? 
>>>
>>>The dejagnu ".exp" files contain timeout overrides.  
>However, they are
>>>already fairly generous (30-60 seconds).  How long does it take on
>>>your machine to get one of these probes started?
>> 
>> 
>> Usually it is 6 to 10 seconds if I run the same test manually.
>> Currently I am just running "runtest" with no options.
>> 
>> Let me know if you need log file or any other details.
>> 
>> -Anil
>
>Could you send the systemtap.log file? Are you seeing the "systemtap 
>starting probe" and "systemtap test success" messages in the 
>systemtap.log?
>
>-Will
>

[-- Attachment #2: testrun.log --]
[-- Type: application/octet-stream, Size: 13204 bytes --]

Test Run By root on Fri Nov  4 01:51:22 2005
Native configuration is ia64-redhat-linux-gnu

		===  tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./systemtap/systemtap-run.exp ...
SystemTap translator/driver (version 0.4.1 built 2005-10-30)
Copyright (C) 2005 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
PASS: version check
testcase ./systemtap/systemtap-run.exp completed in 0 seconds
Running ./systemtap.base/add.exp ...
systemtap starting probe
PASS: ./systemtap.base/add.stp startup
PASS: ./systemtap.base/add.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/add.stp shutdown and output
testcase ./systemtap.base/add.exp completed in 4 seconds
Running ./systemtap.base/and.exp ...
systemtap starting probe
PASS: ./systemtap.base/and.stp startup
PASS: ./systemtap.base/and.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/and.stp shutdown and output
testcase ./systemtap.base/and.exp completed in 4 seconds
Running ./systemtap.base/dec.exp ...
systemtap starting probe
PASS: ./systemtap.base/dec.stp startup
PASS: ./systemtap.base/dec.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/dec.stp shutdown and output
testcase ./systemtap.base/dec.exp completed in 4 seconds
Running ./systemtap.base/div.exp ...
systemtap starting probe
PASS: ./systemtap.base/div.stp startup
PASS: ./systemtap.base/div.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/div.stp shutdown and output
testcase ./systemtap.base/div.exp completed in 3 seconds
Running ./systemtap.base/div0.exp ...
systemtap starting probe
PASS: ./systemtap.base/div0.stp startup
PASS: ./systemtap.base/div0.stp load generation
systemtap ending probe
ERROR: division by 0 near operator '/' at ./systemtap.base/div0.stp:21:10
PASS: ./systemtap.base/div0.stp shutdown and output
testcase ./systemtap.base/div0.exp completed in 4 seconds
Running ./systemtap.base/equal.exp ...
stap(9651): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9651): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9651): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(9651): unaligned access to 0x200000000311c071, ip=0x2000000000073190
systemtap starting probe
FAIL: ./systemtap.base/equal.stp startup (timeout)
testcase ./systemtap.base/equal.exp completed in 60 seconds
Running ./systemtap.base/finloop2.exp ...
stap(9758): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9758): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9758): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(9758): unaligned access to 0x200000000311c071, ip=0x2000000000073190
systemtap starting probe
FAIL: ./systemtap.base/finloop2.stp startup (timeout)
testcase ./systemtap.base/finloop2.exp completed in 60 seconds
Running ./systemtap.base/gt.exp ...
stap(9860): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9860): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9860): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(9860): unaligned access to 0x200000000311c071, ip=0x2000000000073190
systemtap starting probe
FAIL: ./systemtap.base/gt.stp startup (timeout)
testcase ./systemtap.base/gt.exp completed in 60 seconds
Running ./systemtap.base/gte.exp ...
stap(9962): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9962): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9962): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(9962): unaligned access to 0x200000000311c071, ip=0x2000000000073190
systemtap starting probe
FAIL: ./systemtap.base/gte.stp startup (timeout)
testcase ./systemtap.base/gte.exp completed in 60 seconds
Running ./systemtap.base/if.exp ...
systemtap starting probe
PASS: ./systemtap.base/if.stp startup
PASS: ./systemtap.base/if.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
PASS: ./systemtap.base/if.stp shutdown and output
testcase ./systemtap.base/if.exp completed in 4 seconds
Running ./systemtap.base/inc.exp ...
systemtap starting probe
PASS: ./systemtap.base/inc.stp startup
PASS: ./systemtap.base/inc.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/inc.stp shutdown and output
testcase ./systemtap.base/inc.exp completed in 4 seconds
Running ./systemtap.base/kfunct.exp ...
stap(10277): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(10277): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(10277): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(10277): unaligned access to 0x200000000311c071, ip=0x2000000000073190
systemtap starting probe
FAIL: ./systemtap.base/kfunct.stp startup (timeout)
testcase ./systemtap.base/kfunct.exp completed in 60 seconds
Running ./systemtap.base/kmodule.exp ...
semantic error: FAIL: ./systemtap.base/kmodule.stp compilation
testcase ./systemtap.base/kmodule.exp completed in 0 seconds
Running ./systemtap.base/logical_and.exp ...
systemtap starting probe
PASS: ./systemtap.base/logical_and.stp startup
PASS: ./systemtap.base/logical_and.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
systemtap test success
systemtap test success
PASS: ./systemtap.base/logical_and.stp shutdown and output
testcase ./systemtap.base/logical_and.exp completed in 4 seconds
Running ./systemtap.base/logical_not.exp ...
systemtap starting probe
PASS: ./systemtap.base/logical_not.stp startup
PASS: ./systemtap.base/logical_not.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
systemtap test success
PASS: ./systemtap.base/logical_not.stp shutdown and output
testcase ./systemtap.base/logical_not.exp completed in 4 seconds
Running ./systemtap.base/logical_or.exp ...
systemtap starting probe
PASS: ./systemtap.base/logical_or.stp startup
PASS: ./systemtap.base/logical_or.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
systemtap test success
systemtap test success
PASS: ./systemtap.base/logical_or.stp shutdown and output
testcase ./systemtap.base/logical_or.exp completed in 4 seconds
Running ./systemtap.base/lshift.exp ...
systemtap starting probe
PASS: ./systemtap.base/lshift.stp startup
PASS: ./systemtap.base/lshift.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/lshift.stp shutdown and output
testcase ./systemtap.base/lshift.exp completed in 4 seconds
Running ./systemtap.base/lt.exp ...
stap(10814): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(10814): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(10814): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(10814): unaligned access to 0x200000000311c071, ip=0x2000000000073190
systemtap starting probe
FAIL: ./systemtap.base/lt.stp startup (timeout)
testcase ./systemtap.base/lt.exp completed in 60 seconds
Running ./systemtap.base/lte.exp ...
stap(10928): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(10928): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(10928): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(10928): unaligned access to 0x200000000311c071, ip=0x2000000000073190
systemtap starting probe
FAIL: ./systemtap.base/lte.stp startup (timeout)
testcase ./systemtap.base/lte.exp completed in 60 seconds
Running ./systemtap.base/mod.exp ...
systemtap starting probe
PASS: ./systemtap.base/mod.stp startup
PASS: ./systemtap.base/mod.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/mod.stp shutdown and output
testcase ./systemtap.base/mod.exp completed in 4 seconds
Running ./systemtap.base/mult.exp ...
systemtap starting probe
PASS: ./systemtap.base/mult.stp startup
PASS: ./systemtap.base/mult.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/mult.stp shutdown and output
testcase ./systemtap.base/mult.exp completed in 4 seconds
Running ./systemtap.base/ne.exp ...
stap(11241): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(11241): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(11241): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(11241): unaligned access to 0x200000000311c071, ip=0x2000000000073190
systemtap starting probe
FAIL: ./systemtap.base/ne.stp startup (timeout)
testcase ./systemtap.base/ne.exp completed in 60 seconds
Running ./systemtap.base/neg.exp ...
systemtap starting probe
PASS: ./systemtap.base/neg.stp startup
PASS: ./systemtap.base/neg.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
PASS: ./systemtap.base/neg.stp shutdown and output
testcase ./systemtap.base/neg.exp completed in 4 seconds
Running ./systemtap.base/not.exp ...
systemtap starting probe
PASS: ./systemtap.base/not.stp startup
PASS: ./systemtap.base/not.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/not.stp shutdown and output
testcase ./systemtap.base/not.exp completed in 4 seconds
Running ./systemtap.base/or.exp ...
systemtap starting probe
PASS: ./systemtap.base/or.stp startup
PASS: ./systemtap.base/or.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/or.stp shutdown and output
testcase ./systemtap.base/or.exp completed in 4 seconds
Running ./systemtap.base/rshift.exp ...
systemtap starting probe
PASS: ./systemtap.base/rshift.stp startup
PASS: ./systemtap.base/rshift.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/rshift.stp shutdown and output
testcase ./systemtap.base/rshift.exp completed in 4 seconds
Running ./systemtap.base/simple.exp ...
FAIL: ./systemtap.base/simple.stp startup (timeout)
testcase ./systemtap.base/simple.exp completed in 60 seconds
Running ./systemtap.base/subtract.exp ...
FAIL: ./systemtap.base/subtract.stp startup (timeout)
testcase ./systemtap.base/subtract.exp completed in 60 seconds
Running ./systemtap.base/tri.exp ...
FAIL: ./systemtap.base/tri.stp startup (timeout)
testcase ./systemtap.base/tri.exp completed in 60 seconds
Running ./systemtap.base/xor.exp ...
FAIL: ./systemtap.base/xor.stp startup (timeout)
testcase ./systemtap.base/xor.exp completed in 60 seconds
Running ./systemtap.samples/arith.exp ...
FAIL: arith (timeout)
FAIL: arith
testcase ./systemtap.samples/arith.exp completed in 30 seconds
Running ./systemtap.samples/arith_limits.exp ...
FAIL: arith (timeout)
FAIL: arith
testcase ./systemtap.samples/arith_limits.exp completed in 30 seconds
Running ./systemtap.samples/control_limits.exp ...
FAIL: control_limits MAXNESTING (timeout)
FAIL: control_limits MAXNESTING (0)
FAIL: control_limits MAXACTION (timeout)
FAIL: control_limits MAXACTION (0)
FAIL: control_limits MAXSTRINGLEN small (timeout)
FAIL: control_limits MAXSTRINGLEN small (0)
FAIL: control_limits MAXSTRINGLEN large (timeout)
FAIL: control_limits MAXSTRINGLEN large (0)
testcase ./systemtap.samples/control_limits.exp completed in 240 seconds
Running ./systemtap.samples/pfaults.exp ...
FAIL: pfaults (timeout)
FAIL: pfaults (0)
testcase ./systemtap.samples/pfaults.exp completed in 30 seconds
Running ./systemtap.samples/primes.exp ...
FAIL: primes (timeout)
FAIL: primes
testcase ./systemtap.samples/primes.exp completed in 30 seconds
Running ./systemtap.samples/profile.exp ...
FAIL: profile (timeout)
FAIL: profile
testcase ./systemtap.samples/profile.exp completed in 30 seconds
Running ./systemtap.samples/symbols.exp ...
FAIL: symbols (timeout)
FAIL: symbols (0)
testcase ./systemtap.samples/symbols.exp completed in 30 seconds
Running ./systemtap.samples/syscalls1.exp ...
FAIL: syscalls-count (timeout)
FAIL: syscalls-count (0)
testcase ./systemtap.samples/syscalls1.exp completed in 30 seconds
Running ./systemtap.samples/syscalls2.exp ...
FAIL: syscalls-run (timeout)
FAIL: syscalls-run (0)
testcase ./systemtap.samples/syscalls2.exp completed in 60 seconds
Running ./systemtap.samples/sysopen.exp ...
FAIL: sysopen (timeout)
FAIL: sysopen (0)
testcase ./systemtap.samples/sysopen.exp completed in 60 seconds
Running ./systemtap.samples/transport.exp ...
FAIL: transport normal - procfs (timeout)
FAIL: transport normal - procfs (0)
FAIL: transport normal - relayfs (timeout)
FAIL: transport normal - relayfs (0)
FAIL: transport fill staging buffer - procfs (timeout)
FAIL: transport fill staging buffer - procfs (0)
FAIL: transport fill staging buffer - relayfs (timeout)
FAIL: transport fill staging buffer - relayfs (0)
testcase ./systemtap.samples/transport.exp completed in 240 seconds

		===  Summary ===

# of expected passes		52
# of unexpected failures	47
runtest completed at Fri Nov  4 02:17:59 2005

Re: testsuits on IA64

[Hien Nguyen]

It looks like memory alignment problem for some of the tests. Run
stap equal.stp

then look at your /var/log/messages
Hien.
Keshavamurthy, Anil S wrote:

>Will, 
>I am attaching log file. Your help is appreciated.
>
>Thanks,
>Anil Keshavamurthy
>
>  
>
>>-----Original Message-----
>>From: systemtap-owner@sourceware.org 
>>[mailto:systemtap-owner@sourceware.org] On Behalf Of William Cohen
>>Sent: Friday, November 04, 2005 3:04 PM
>>To: Keshavamurthy, Anil S
>>Cc: Frank Ch. Eigler; systemtap@sources.redhat.com
>>Subject: Re: testsuits on IA64
>>
>>Keshavamurthy Anil S wrote:
>>    
>>
>>>On Fri, Nov 04, 2005 at 02:00:15PM -0500, Frank Ch. Eigler wrote:
>>>
>>>      
>>>
>>>>Hi -
>>>>
>>>>
>>>>        
>>>>
>>>>>I am trying to run testsuits (dejagnu) on IA64 and most of the tests
>>>>>fails on Ia64 with FAIL : timeout.
>>>>>How do I increase the timeout value? 
>>>>>          
>>>>>
>>>>The dejagnu ".exp" files contain timeout overrides.  
>>>>        
>>>>
>>However, they are
>>    
>>
>>>>already fairly generous (30-60 seconds).  How long does it take on
>>>>your machine to get one of these probes started?
>>>>        
>>>>
>>>Usually it is 6 to 10 seconds if I run the same test manually.
>>>Currently I am just running "runtest" with no options.
>>>
>>>Let me know if you need log file or any other details.
>>>
>>>-Anil
>>>      
>>>
>>Could you send the systemtap.log file? Are you seeing the "systemtap 
>>starting probe" and "systemtap test success" messages in the 
>>systemtap.log?
>>
>>-Will
>>
>>    
>>

Re: testsuits on IA64

[William Cohen]

Keshavamurthy, Anil S wrote:
> Will, 
> I am attaching log file. Your help is appreciated.
> 
> Thanks,
> Anil Keshavamurthy

I took a look at the resulting test log.

Seeing unaligned accesses on ia64 like the following (from
equal.stp)for a number of the tests:

stap(9651): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9651): unaligned access to 0x200000000311c016, ip=0x2000000000070710
stap(9651): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
stap(9651): unaligned access to 0x200000000311c071, ip=0x2000000000073190

This appears to be in userspace. Which process and location does this 
map back to? Is this the systemtap daemon that is started when the
systemtap kernel module is loaded?

Could you run "stap -V -k ./systemtap.base/kmodule.stp" and send the 
output? The kmodule test failed and it would be good to know why.

Could you try to run ./systemtap.base/simple.stp by hand? It failed on
startup. Test after it also seem to fail startup. I am wondering if
that failure caused the other startup failures.



-Will

Re: testsuits on IA64

[William Cohen]

William Cohen wrote:

> Could you run "stap -V -k ./systemtap.base/kmodule.stp" and send the 
> output? The kmodule test failed and it would be good to know why.

wrong case for verbose.

stap -v -k ./systemtap.base/kmodule.stp

-Will

Re: testsuits on IA64

[Keshavamurthy Anil S]

[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]

On Tue, Nov 08, 2005 at 11:14:46AM -0500, William Cohen wrote:
> Seeing unaligned accesses on ia64 like the following (from
> equal.stp)for a number of the tests:
> 
> stap(9651): unaligned access to 0x200000000311c016, ip=0x2000000000070710
> stap(9651): unaligned access to 0x200000000311c016, ip=0x2000000000070710
> stap(9651): unaligned access to 0x200000000311c035, ip=0x2000000000070c10
> stap(9651): unaligned access to 0x200000000311c071, ip=0x2000000000073190
> 
> This appears to be in userspace. Which process and location does this 
> map back to? Is this the systemtap daemon that is started when the
> systemtap kernel module is loaded?
The above unaligned access got fixed when I upgraded elfutils to elfutils-0.116.
http://sourceware.org/bugzilla/show_bug.cgi?id=1340


> 
> Could you run "stap -V -k ./systemtap.base/kmodule.stp" and send the 
> output? The kmodule test failed and it would be good to know why.
Attaching the output. 

> 
> Could you try to run ./systemtap.base/simple.stp by hand? It failed on
> startup. Test after it also seem to fail startup. I am wondering if
> that failure caused the other startup failures.
Also when I run the individual test by hand i.e stap -v ./systemtap.base/test_name.stp
all the tests passes.

-Anil Keshavamurthy

[-- Attachment #2: kmodule_source.tgz --]
[-- Type: application/x-gzip, Size: 759908 bytes --]

Re: testsuits on IA64

[William Cohen]

Keshavamurthy Anil S wrote:

>>Could you run "stap -V -k ./systemtap.base/kmodule.stp" and send the 
>>output? The kmodule test failed and it would be good to know why.
> 
> Attaching the output. 

I don't have a ia64 machine handy to try things out on. Could you send 
me the output that comes on the console from "stap -v -k 
./systemtap.base/kmodule.stp"? I would like to see that error messages 
the compiler is producing when it attempts to produce the module.

-Will

Re: testsuits on IA64

[Keshavamurthy Anil S]

On Wed, Nov 09, 2005 at 10:07:52AM -0500, William Cohen wrote:
> Keshavamurthy Anil S wrote:
> 
> I don't have a ia64 machine handy to try things out on. Could you send 
> me the output that comes on the console from "stap -v -k 
> ./systemtap.base/kmodule.stp"? I would like to see that error messages 
> the compiler is producing when it attempts to produce the module.

Hi Will,
	Here goes the output you requested, as mentioned earlier I don't have any problems
running individual tap scripts manually. It is only when I run runtest I see timeouts.

Thanks,
Anil

[root@csdor-tiger1 testsuite]# stap -v -k systemtap.base/kmodule.stp
Created temporary directory "/tmp/stapLpQ3QC"
Searched '/usr/local/share/systemtap/tapset/2.6.9-22.10.EL/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/2.6.9/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/2.6/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/*.stp', match count 9
Pass 1: parsed user script and 9 library script(s).
parsed 'ext3_sync_file' -> func 'ext3_sync_file'
pattern 'ext3' matches module 'ext3'
focused on module 'ext3' = [a00000020014c000-a000000200192db8, bias 0]
pattern 'ext3_sync_file' matches function 'ext3_sync_file'
selected function ext3_sync_file
prologue disagreement: ext3_sync_file heur0=a000000200153981 heur1=a000000200153982
querying entrypc of function 'ext3_sync_file'
Pass 2: analyzed user script.  3 probe(s), 10 function(s), 1 global(s).
Running grep " [tT] " /proc/kallsyms | sort -k 1,16 -s -o /tmp/stapLpQ3QC/symbols.sorted
Pass 3: translated to C into "/tmp/stapLpQ3QC/stap_15614.c"
Running make -C "/lib/modules/2.6.9-22.10.EL/build" M="/tmp/stapLpQ3QC" modules
make: Entering directory `/usr/src/kernels/2.6.9-22.10.EL-ia64'
  CC [M]  /tmp/stapLpQ3QC/stap_15614.o
  Building modules, stage 2.
  MODPOST
  CC      /tmp/stapLpQ3QC/stap_15614.mod.o
  LD [M]  /tmp/stapLpQ3QC/stap_15614.ko
make: Leaving directory `/usr/src/kernels/2.6.9-22.10.EL-ia64'
Pass 4: compiled into "stap_15614.ko"
Running sudo /usr/local/libexec/systemtap/stpd -r /tmp/stapLpQ3QC/stap_15614.ko
systemtap starting probe

Re: testsuits on IA64

[William Cohen]

Keshavamurthy Anil S wrote:
> On Wed, Nov 09, 2005 at 10:07:52AM -0500, William Cohen wrote:
> 
>>Keshavamurthy Anil S wrote:
>>
>>I don't have a ia64 machine handy to try things out on. Could you send 
>>me the output that comes on the console from "stap -v -k 
>>./systemtap.base/kmodule.stp"? I would like to see that error messages 
>>the compiler is producing when it attempts to produce the module.
> 
> 
> Hi Will,
> 	Here goes the output you requested, as mentioned earlier I don't have any problems
> running individual tap scripts manually. It is only when I run runtest I see timeouts.

Hi Anil,

So the kmodule.stp test compiles and runs fine by itself? There was the 
following in the testrun.log:

Running ./systemtap.base/kmodule.exp ...
semantic error: FAIL: ./systemtap.base/kmodule.stp compilation

I assumed that there was a problem with the compilation. So the 
individual tests work when run, e.g. "runtest --tool=systemtap 
./systemtap.base/kmodule.exp"? What do the test results look with the 
newer version of elfutils? Still lots of failures?

-Will

Re: testsuits on IA64

[Keshavamurthy Anil S]

[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]

On Wed, Nov 09, 2005 at 02:26:05PM -0500, William Cohen wrote:
> Keshavamurthy Anil S wrote:
> > On Wed, Nov 09, 2005 at 10:07:52AM -0500, William Cohen wrote:
> > 
> >>Keshavamurthy Anil S wrote:
> >>
> >>I don't have a ia64 machine handy to try things out on. Could you send 
> >>me the output that comes on the console from "stap -v -k 
> >>./systemtap.base/kmodule.stp"? I would like to see that error messages 
> >>the compiler is producing when it attempts to produce the module.
> > 
> > 
> > Hi Will,
> > 	Here goes the output you requested, as mentioned earlier I don't have any problems
> > running individual tap scripts manually. It is only when I run runtest I see timeouts.
> 
> Hi Anil,
> 
> So the kmodule.stp test compiles and runs fine by itself? There was the 
> following in the testrun.log:
> 
> Running ./systemtap.base/kmodule.exp ...
> semantic error: FAIL: ./systemtap.base/kmodule.stp compilation
All the compile issues are gone(fixed) with elfutils-0.116.
Now I don;t have the above compile issues.
> 
> I assumed that there was a problem with the compilation. So the 
> individual tests work when run, e.g. "runtest --tool=systemtap 
> ./systemtap.base/kmodule.exp"? What do the test results look with the 
> newer version of elfutils? Still lots of failures?

With newer elfutils though I still see timeout(attaching testrun.log), it is
much better as I don't have any complile issues.

Also when I run the individual failed(timout test) as "runtest --tool=systemtap
./systemtap.base/simple.exp" i.e one test at a time, I don't have any issues.
The systemtap.sum and systemtap.log both will have results as PASS.
It would be better if we can root cause the timeout issue but not a burning 
issues at this point in time as compile issue is resolved and I know all the tests works :-)

-Anil







> 
> -Will

[-- Attachment #2: testrun.log --]
[-- Type: text/plain, Size: 12181 bytes --]

Test Run By root on Tue Nov  8 23:33:01 2005
Native configuration is ia64-redhat-linux-gnu

		===  tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./systemtap/systemtap-run.exp ...
SystemTap translator/driver (version 0.4.2 built 2005-11-08)
Copyright (C) 2005 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
PASS: version check
testcase ./systemtap/systemtap-run.exp completed in 0 seconds
Running ./systemtap.base/add.exp ...
systemtap starting probe
PASS: ./systemtap.base/add.stp startup
PASS: ./systemtap.base/add.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/add.stp shutdown and output
testcase ./systemtap.base/add.exp completed in 4 seconds
Running ./systemtap.base/and.exp ...
systemtap starting probe
PASS: ./systemtap.base/and.stp startup
PASS: ./systemtap.base/and.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/and.stp shutdown and output
testcase ./systemtap.base/and.exp completed in 3 seconds
Running ./systemtap.base/dec.exp ...
systemtap starting probe
PASS: ./systemtap.base/dec.stp startup
PASS: ./systemtap.base/dec.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/dec.stp shutdown and output
testcase ./systemtap.base/dec.exp completed in 3 seconds
Running ./systemtap.base/div.exp ...
systemtap starting probe
PASS: ./systemtap.base/div.stp startup
PASS: ./systemtap.base/div.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/div.stp shutdown and output
testcase ./systemtap.base/div.exp completed in 4 seconds
Running ./systemtap.base/div0.exp ...
systemtap starting probe
PASS: ./systemtap.base/div0.stp startup
PASS: ./systemtap.base/div0.stp load generation
systemtap ending probe
ERROR: division by 0 near operator '/' at ./systemtap.base/div0.stp:21:10
PASS: ./systemtap.base/div0.stp shutdown and output
testcase ./systemtap.base/div0.exp completed in 3 seconds
Running ./systemtap.base/equal.exp ...
systemtap starting probe
PASS: ./systemtap.base/equal.stp startup
PASS: ./systemtap.base/equal.stp load generation
systemtap ending probe
count = 4
count2 = 4
systemtap test success
PASS: ./systemtap.base/equal.stp shutdown and output
testcase ./systemtap.base/equal.exp completed in 4 seconds
Running ./systemtap.base/finloop2.exp ...
systemtap starting probe
PASS: ./systemtap.base/finloop2.stp startup
PASS: ./systemtap.base/finloop2.stp load generation
systemtap ending probe
count = 4
loop_count = 40
systemtap test success
PASS: ./systemtap.base/finloop2.stp shutdown and output
testcase ./systemtap.base/finloop2.exp completed in 4 seconds
Running ./systemtap.base/gt.exp ...
systemtap starting probe
PASS: ./systemtap.base/gt.stp startup
PASS: ./systemtap.base/gt.stp load generation
systemtap ending probe
count = 4
count2 = 4
systemtap test success
PASS: ./systemtap.base/gt.stp shutdown and output
testcase ./systemtap.base/gt.exp completed in 4 seconds
Running ./systemtap.base/gte.exp ...
systemtap starting probe
PASS: ./systemtap.base/gte.stp startup
PASS: ./systemtap.base/gte.stp load generation
systemtap ending probe
count = 5
count2 = 5
systemtap test success
PASS: ./systemtap.base/gte.stp shutdown and output
testcase ./systemtap.base/gte.exp completed in 4 seconds
Running ./systemtap.base/if.exp ...
systemtap starting probe
PASS: ./systemtap.base/if.stp startup
PASS: ./systemtap.base/if.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
PASS: ./systemtap.base/if.stp shutdown and output
testcase ./systemtap.base/if.exp completed in 3 seconds
Running ./systemtap.base/inc.exp ...
systemtap starting probe
PASS: ./systemtap.base/inc.stp startup
PASS: ./systemtap.base/inc.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/inc.stp shutdown and output
testcase ./systemtap.base/inc.exp completed in 3 seconds
Running ./systemtap.base/kfunct.exp ...
systemtap starting probe
PASS: ./systemtap.base/kfunct.stp startup
PASS: ./systemtap.base/kfunct.stp load generation
systemtap ending probe
count = 4
PASS: ./systemtap.base/kfunct.stp shutdown and output
testcase ./systemtap.base/kfunct.exp completed in 4 seconds
Running ./systemtap.base/kmodule.exp ...
systemtap starting probe
PASS: ./systemtap.base/kmodule.stp startup
PASS: ./systemtap.base/kmodule.stp load generation
systemtap ending probe
count = 0
PASS: ./systemtap.base/kmodule.stp shutdown and output
testcase ./systemtap.base/kmodule.exp completed in 4 seconds
Running ./systemtap.base/logical_and.exp ...
systemtap starting probe
PASS: ./systemtap.base/logical_and.stp startup
PASS: ./systemtap.base/logical_and.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
systemtap test success
systemtap test success
PASS: ./systemtap.base/logical_and.stp shutdown and output
testcase ./systemtap.base/logical_and.exp completed in 4 seconds
Running ./systemtap.base/logical_not.exp ...
systemtap starting probe
PASS: ./systemtap.base/logical_not.stp startup
PASS: ./systemtap.base/logical_not.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
systemtap test success
PASS: ./systemtap.base/logical_not.stp shutdown and output
testcase ./systemtap.base/logical_not.exp completed in 3 seconds
Running ./systemtap.base/logical_or.exp ...
systemtap starting probe
PASS: ./systemtap.base/logical_or.stp startup
PASS: ./systemtap.base/logical_or.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
systemtap test success
systemtap test success
PASS: ./systemtap.base/logical_or.stp shutdown and output
testcase ./systemtap.base/logical_or.exp completed in 4 seconds
Running ./systemtap.base/lshift.exp ...
systemtap starting probe
PASS: ./systemtap.base/lshift.stp startup
PASS: ./systemtap.base/lshift.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/lshift.stp shutdown and output
testcase ./systemtap.base/lshift.exp completed in 3 seconds
Running ./systemtap.base/lt.exp ...
systemtap starting probe
PASS: ./systemtap.base/lt.stp startup
PASS: ./systemtap.base/lt.stp load generation
systemtap ending probe
count = 4
count2 = 4
systemtap test success
PASS: ./systemtap.base/lt.stp shutdown and output
testcase ./systemtap.base/lt.exp completed in 4 seconds
Running ./systemtap.base/lte.exp ...
systemtap starting probe
PASS: ./systemtap.base/lte.stp startup
PASS: ./systemtap.base/lte.stp load generation
systemtap ending probe
count = 4
count2 = 4
systemtap test success
PASS: ./systemtap.base/lte.stp shutdown and output
testcase ./systemtap.base/lte.exp completed in 4 seconds
Running ./systemtap.base/mod.exp ...
systemtap starting probe
PASS: ./systemtap.base/mod.stp startup
PASS: ./systemtap.base/mod.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/mod.stp shutdown and output
testcase ./systemtap.base/mod.exp completed in 3 seconds
Running ./systemtap.base/mult.exp ...
systemtap starting probe
PASS: ./systemtap.base/mult.stp startup
PASS: ./systemtap.base/mult.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/mult.stp shutdown and output
testcase ./systemtap.base/mult.exp completed in 4 seconds
Running ./systemtap.base/ne.exp ...
systemtap starting probe
PASS: ./systemtap.base/ne.stp startup
PASS: ./systemtap.base/ne.stp load generation
systemtap ending probe
count = 3
count2 = 3
systemtap test success
PASS: ./systemtap.base/ne.stp shutdown and output
testcase ./systemtap.base/ne.exp completed in 3 seconds
Running ./systemtap.base/neg.exp ...
systemtap starting probe
PASS: ./systemtap.base/neg.stp startup
PASS: ./systemtap.base/neg.stp load generation
systemtap ending probe
systemtap test success
systemtap test success
PASS: ./systemtap.base/neg.stp shutdown and output
testcase ./systemtap.base/neg.exp completed in 4 seconds
Running ./systemtap.base/not.exp ...
systemtap starting probe
PASS: ./systemtap.base/not.stp startup
PASS: ./systemtap.base/not.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/not.stp shutdown and output
testcase ./systemtap.base/not.exp completed in 3 seconds
Running ./systemtap.base/or.exp ...
systemtap starting probe
PASS: ./systemtap.base/or.stp startup
PASS: ./systemtap.base/or.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/or.stp shutdown and output
testcase ./systemtap.base/or.exp completed in 4 seconds
Running ./systemtap.base/rshift.exp ...
systemtap starting probe
PASS: ./systemtap.base/rshift.stp startup
PASS: ./systemtap.base/rshift.stp load generation
systemtap ending probe
systemtap test success
PASS: ./systemtap.base/rshift.stp shutdown and output
testcase ./systemtap.base/rshift.exp completed in 3 seconds
Running ./systemtap.base/simple.exp ...
FAIL: ./systemtap.base/simple.stp startup (timeout)
testcase ./systemtap.base/simple.exp completed in 30 seconds
Running ./systemtap.base/subtract.exp ...
FAIL: ./systemtap.base/subtract.stp startup (timeout)
testcase ./systemtap.base/subtract.exp completed in 30 seconds
Running ./systemtap.base/tri.exp ...
FAIL: ./systemtap.base/tri.stp startup (timeout)
testcase ./systemtap.base/tri.exp completed in 30 seconds
Running ./systemtap.base/xor.exp ...
FAIL: ./systemtap.base/xor.stp startup (timeout)
testcase ./systemtap.base/xor.exp completed in 30 seconds
Running ./systemtap.samples/arith.exp ...
FAIL: arith (timeout)
FAIL: arith
testcase ./systemtap.samples/arith.exp completed in 30 seconds
Running ./systemtap.samples/arith_limits.exp ...
FAIL: arith (timeout)
FAIL: arith
testcase ./systemtap.samples/arith_limits.exp completed in 30 seconds
Running ./systemtap.samples/control_limits.exp ...
FAIL: control_limits MAXNESTING (timeout)
FAIL: control_limits MAXNESTING (0)
FAIL: control_limits MAXACTION (timeout)
FAIL: control_limits MAXACTION (0)
FAIL: control_limits MAXSTRINGLEN small (timeout)
FAIL: control_limits MAXSTRINGLEN small (0)
FAIL: control_limits MAXSTRINGLEN large (timeout)
FAIL: control_limits MAXSTRINGLEN large (0)
testcase ./systemtap.samples/control_limits.exp completed in 240 seconds
Running ./systemtap.samples/pfaults.exp ...
FAIL: pfaults (timeout)
FAIL: pfaults (0)
testcase ./systemtap.samples/pfaults.exp completed in 30 seconds
Running ./systemtap.samples/primes.exp ...
FAIL: primes (timeout)
FAIL: primes
testcase ./systemtap.samples/primes.exp completed in 30 seconds
Running ./systemtap.samples/profile.exp ...
FAIL: profile (timeout)
FAIL: profile
testcase ./systemtap.samples/profile.exp completed in 30 seconds
Running ./systemtap.samples/symbols.exp ...
FAIL: symbols (timeout)
FAIL: symbols (0)
testcase ./systemtap.samples/symbols.exp completed in 30 seconds
Running ./systemtap.samples/syscalls1.exp ...
FAIL: syscalls-count (timeout)
FAIL: syscalls-count (0)
testcase ./systemtap.samples/syscalls1.exp completed in 30 seconds
Running ./systemtap.samples/syscalls2.exp ...
FAIL: syscalls-run (timeout)
FAIL: syscalls-run (0)
testcase ./systemtap.samples/syscalls2.exp completed in 60 seconds
Running ./systemtap.samples/sysopen.exp ...
FAIL: sysopen (timeout)
FAIL: sysopen (0)
testcase ./systemtap.samples/sysopen.exp completed in 60 seconds
Running ./systemtap.samples/transport.exp ...
FAIL: transport normal - procfs (timeout)
FAIL: transport normal - procfs (0)
FAIL: transport normal - relayfs (timeout)
FAIL: transport normal - relayfs (0)
FAIL: transport fill staging buffer - procfs (timeout)
FAIL: transport fill staging buffer - procfs (0)
FAIL: transport fill staging buffer - relayfs (timeout)
FAIL: transport fill staging buffer - relayfs (0)
testcase ./systemtap.samples/transport.exp completed in 240 seconds

		===  Summary ===

# of expected passes		79
# of unexpected failures	38
runtest completed at Tue Nov  8 23:50:04 2005

RE: testsuits on IA64

[Mao, Bibo]

The same phenomenon exists on EM64T, when I enter "runtest" command, and in another console enter "ps -aux", there will be many defunct processes like:
root     20648  0.3  0.0     0    0 ?      Zs   09:54   0:00 [stap] <defunct>
root     20755  0.3  0.0     0    0 ?      Zs   09:54   0:00 [stap] <defunct>
root     20861  0.3  0.0     0    0 ?      Zs   09:55   0:00 [stap] <defunct>
root     20972  0.3  0.0     0    0 ?      Zs   09:55   0:00 [stap] <defunct>
root     21075  0.3  0.0     0    0 ?      Zs   09:55   0:00 [stap] <defunct>
root     21181  0.3  0.0     0    0 ?      Zs   09:55   0:00 [stap] <defunct>

But if I divided systemtap.base directory into two parts: systemtap1 and systemtap2, and test it by "runtest -di systemtap1" and "runtest -di systemtap2". It will run well.


>-----Original Message-----
>From: systemtap-owner@sourceware.org [mailto:systemtap-owner@sourceware.org]
>On Behalf Of Hien Nguyen
>Sent: 2005年11月5日 7:47
>To: Keshavamurthy, Anil S
>Cc: William Cohen; Frank Ch. Eigler; systemtap@sources.redhat.com
>Subject: Re: testsuits on IA64
>
>It looks like memory alignment problem for some of the tests. Run
>stap equal.stp
>
>then look at your /var/log/messages
>Hien.
>Keshavamurthy, Anil S wrote:
>
>>Will,
>>I am attaching log file. Your help is appreciated.
>>
>>Thanks,
>>Anil Keshavamurthy
>>
>>
>>
>>>-----Original Message-----
>>>From: systemtap-owner@sourceware.org
>>>[mailto:systemtap-owner@sourceware.org] On Behalf Of William Cohen
>>>Sent: Friday, November 04, 2005 3:04 PM
>>>To: Keshavamurthy, Anil S
>>>Cc: Frank Ch. Eigler; systemtap@sources.redhat.com
>>>Subject: Re: testsuits on IA64
>>>
>>>Keshavamurthy Anil S wrote:
>>>
>>>
>>>>On Fri, Nov 04, 2005 at 02:00:15PM -0500, Frank Ch. Eigler wrote:
>>>>
>>>>
>>>>
>>>>>Hi -
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>I am trying to run testsuits (dejagnu) on IA64 and most of the tests
>>>>>>fails on Ia64 with FAIL : timeout.
>>>>>>How do I increase the timeout value?
>>>>>>
>>>>>>
>>>>>The dejagnu ".exp" files contain timeout overrides.
>>>>>
>>>>>
>>>However, they are
>>>
>>>
>>>>>already fairly generous (30-60 seconds).  How long does it take on
>>>>>your machine to get one of these probes started?
>>>>>
>>>>>
>>>>Usually it is 6 to 10 seconds if I run the same test manually.
>>>>Currently I am just running "runtest" with no options.
>>>>
>>>>Let me know if you need log file or any other details.
>>>>
>>>>-Anil
>>>>
>>>>
>>>Could you send the systemtap.log file? Are you seeing the "systemtap
>>>starting probe" and "systemtap test success" messages in the
>>>systemtap.log?
>>>
>>>-Will
>>>
>>>
>>>

Re: testsuits on IA64

[William Cohen]

Keshavamurthy Anil S wrote:
> On Fri, Nov 04, 2005 at 02:00:15PM -0500, Frank Ch. Eigler wrote:
> 
>>Hi -
>>
>>
>>>I am trying to run testsuits (dejagnu) on IA64 and most of the tests
>>>fails on Ia64 with FAIL : timeout.
>>>How do I increase the timeout value? 
>>
>>The dejagnu ".exp" files contain timeout overrides.  However, they are
>>already fairly generous (30-60 seconds).  How long does it take on
>>your machine to get one of these probes started?
> 
> 
> Usually it is 6 to 10 seconds if I run the same test manually.
> Currently I am just running "runtest" with no options.
> 
> Let me know if you need log file or any other details.
> 
> -Anil

Could you send the systemtap.log file? Are you seeing the "systemtap 
starting probe" and "systemtap test success" messages in the systemtap.log?

-Will

Re: testsuits on IA64

[Frank Ch. Eigler]

Hi -

> > [...]  How long does it take on
> > your machine to get one of these probes started?
> 
> Usually it is 6 to 10 seconds if I run the same test manually.
> Currently I am just running "runtest" with no options. [...]

OK, that suggests that it's not an ordinary timeout problem.  I have
encountered your symptoms on an ordinary machine, when I started the
test suite from a user unprivileged to do prompt-less sudo.  Then the
"sudo stpd" child of systemtap would wait for a password, and never
get it (since dejagnu/expect never sends one).

- FChE

Re: testsuits on IA64

[Keshavamurthy Anil S]

On Fri, Nov 04, 2005 at 02:00:15PM -0500, Frank Ch. Eigler wrote:
> Hi -
> 
> > I am trying to run testsuits (dejagnu) on IA64 and most of the tests
> > fails on Ia64 with FAIL : timeout.
> > How do I increase the timeout value? 
> 
> The dejagnu ".exp" files contain timeout overrides.  However, they are
> already fairly generous (30-60 seconds).  How long does it take on
> your machine to get one of these probes started?

Usually it is 6 to 10 seconds if I run the same test manually.
Currently I am just running "runtest" with no options.

Let me know if you need log file or any other details.

-Anil

Re: testsuits on IA64

[Frank Ch. Eigler]

Hi -

> I am trying to run testsuits (dejagnu) on IA64 and most of the tests
> fails on Ia64 with FAIL : timeout.
> How do I increase the timeout value? 

The dejagnu ".exp" files contain timeout overrides.  However, they are
already fairly generous (30-60 seconds).  How long does it take on
your machine to get one of these probes started?

- FChE

testsuits on IA64

[Keshavamurthy, Anil S]

I am trying to run testsuits (dejagnu) on IA64 and most of the tests
fails on Ia64 with FAIL : timeout.
How do I  increase the timeout value? 

Thanks,

-Anil Keshavamurthy
Sr. Software Engineer
Open Source Technology Center/SSG
Intel Corp.
(w) 503-712-4476