Perf test giving strange results

2013-06-26 Thread Andy Green
Hi -

Trying perf test on llct-based 3.10-rc6 isn't entirely happy.

root@aa9-eb:~# perf test
 1: vmlinux symtab matches kallsyms: FAILED!
 2: detect open syscall event  : Ok
 3: detect open syscall event on all cpus  : Ok
 4: read samples using the mmap interface  : Ok
 5: parse events tests :  Warning:
function sizeof not defined
  Warning: function sizeof not defined
  Warning: function scsi_trace_parse_cdb not defined
  Warning: function scsi_trace_parse_cdb not defined
  Warning: function scsi_trace_parse_cdb not defined
  Warning: function scsi_trace_parse_cdb not defined
  Warning: function jiffies_to_msecs not defined
  Warning: function jiffies_to_msecs not defined
  Warning: bad op token {
  Warning: bad op token {
  Warning: bad op token {
  Warning: Error: expected type 4 but read 0
  Warning: bad op token {
  Warning: Error: expected type 4 but read 0
  Warning: bad op token {
  Warning: bad op token {
  Warning: bad op token {
  Warning: bad op token {
  Warning: bad op token {
  Warning: unknown op '{'
  Warning: unknown op '{'
 Ok
 6: Validate PERF_RECORD_* events & perf_sample fields : FAILED!
 7: Test perf pmu format parsing   : Ok
 8: Test dso data interface: Ok
 9: roundtrip evsel->name check: Ok
10: Check parsing of sched tracepoints fields  : FAILED!
11: Generate and check syscalls:sys_enter_open event fields: Ok
12: struct perf_event_attr setup   : (omitted) Ok
13: Test matching and linking mutliple hists   : Ok
14: Try 'use perf' in python, checking link problems   : FAILED!
15: Test breakpoint overflow signal handler: FAILED!
16: Test breakpoint overflow sampling  : FAILED!
17: Test number of exit event of a simple workload : FAILED!
18: Test software clock events have valid period values: Ok


I started tracing the first failure... it stops because it can't find
"_stext" in /proc/kallsyms.  But it is there

root@aa9-eb:~# cat /proc/kallsyms | grep _stext
800081c0 T _stext

test 5 (parse event tests) seems to be badly broken.

Is this just our problem or is it broken for everyone?

-Andy

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


[meta-linaro-toolchain][PATCH] external-linaro-toolchain-versions: Fix NameError: global name 'CmdError' is not defined

2013-06-26 Thread Martin Jansa
* fails with:
  ERROR: Execution of event handler 'external_linaro_toolchain_version_handler' 
failed
  Traceback (most recent call last):
File "external_linaro_toolchain_version_handler(e)", line 12, in 
external_linaro_toolchain_version_handler(e=)
File "external-linaro-toolchain-versions.inc", line 4, in 
elt_get_gdb_version(d=)
  NameError: global name 'CmdError' is not defined

Signed-off-by: Martin Jansa 
---
 .../conf/distro/include/external-linaro-toolchain-versions.inc  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
 
b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
index 92862af..0254895 100644
--- 
a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
+++ 
b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
@@ -86,7 +86,7 @@ def elt_get_kernel_version(d):
 def elt_get_gdb_version(d):
try:
stdout, stderr = elt_run(d, 'gdb', '-v')
-   except CmdError:
+   except bb.process.CmdError:
return 'UNKNOWN'
else:
first_line = stdout.splitlines()[0]
-- 
1.8.2.1


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


[meta-linaro-toolchain][dylan][PATCH] external-linaro-toolchain-versions: Fix NameError: global name 'CmdError' is not defined

2013-06-26 Thread Martin Jansa
* fails with:
  ERROR: Execution of event handler 'external_linaro_toolchain_version_handler' 
failed
  Traceback (most recent call last):
File "external_linaro_toolchain_version_handler(e)", line 12, in 
external_linaro_toolchain_version_handler(e=)
File "external-linaro-toolchain-versions.inc", line 4, in 
elt_get_gdb_version(d=)
  NameError: global name 'CmdError' is not defined

Signed-off-by: Martin Jansa 
---
 .../conf/distro/include/external-linaro-toolchain-versions.inc  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
 
b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
index 92862af..0254895 100644
--- 
a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
+++ 
b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
@@ -86,7 +86,7 @@ def elt_get_kernel_version(d):
 def elt_get_gdb_version(d):
try:
stdout, stderr = elt_run(d, 'gdb', '-v')
-   except CmdError:
+   except bb.process.CmdError:
return 'UNKNOWN'
else:
first_line = stdout.splitlines()[0]
-- 
1.8.2.1


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: [meta-linaro-toolchain][PATCH] external-linaro-toolchain-versions: Fix NameError: global name 'CmdError' is not defined

2013-06-26 Thread Fathi Boudra
Thanks. Applied.

On 26 June 2013 10:50, Martin Jansa  wrote:
> * fails with:
>   ERROR: Execution of event handler 
> 'external_linaro_toolchain_version_handler' failed
>   Traceback (most recent call last):
> File "external_linaro_toolchain_version_handler(e)", line 12, in 
> external_linaro_toolchain_version_handler(e= 0x7759a50>)
> File "external-linaro-toolchain-versions.inc", line 4, in 
> elt_get_gdb_version(d=)
>   NameError: global name 'CmdError' is not defined
>
> Signed-off-by: Martin Jansa 
> ---
>  .../conf/distro/include/external-linaro-toolchain-versions.inc  | 2 
> +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git 
> a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
>  
> b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
> index 92862af..0254895 100644
> --- 
> a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
> +++ 
> b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
> @@ -86,7 +86,7 @@ def elt_get_kernel_version(d):
>  def elt_get_gdb_version(d):
> try:
> stdout, stderr = elt_run(d, 'gdb', '-v')
> -   except CmdError:
> +   except bb.process.CmdError:
> return 'UNKNOWN'
> else:
> first_line = stdout.splitlines()[0]
> --
> 1.8.2.1
>
>
> ___
> linaro-dev mailing list
> linaro-dev@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev



-- 
Fathi Boudra
Builds and Baselines Manager | Release Manager
Linaro.org | Open source software for ARM SoCs

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: Perf test giving strange results

2013-06-26 Thread Milosz Wasilewski
On 26 June 2013 09:16, Andy Green  wrote:
> test 5 (parse event tests) seems to be badly broken.
>
> Is this just our problem or is it broken for everyone?

I'm not sure if the reason is the same but this test was broken in
LAVA for some time now. The latest result on 3.10.0-1-linaro-omap
kernel looks like this:

perf test - parse events tests
:Can't open event dir : No such file or directory
Can't open event dir : No such file or directory
Warning : function scsi_trace_parse_cdb not defined
Warning : function scsi_trace_parse_cdb not defined
Warning : function scsi_trace_parse_cdb not defined
Warning : function scsi_trace_parse_cdb not defined
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : function jiffies_to_msecs not defined
Warning : function jiffies_to_msecs not defined
Warning : bad op token {
Warning : bad op token {
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : Error : expected type 4 but read 0
Warning : bad op token {
Warning : bad op token {
Warning : bad op token {
Warning : bad op token {
Warning : bad op token {
Warning : unknown op '{'
Warning : unknown op '{'
FAIL

milosz

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: Perf test giving strange results

2013-06-26 Thread Andy Green
On 26 June 2013 17:57, Milosz Wasilewski  wrote:
> On 26 June 2013 09:16, Andy Green  wrote:

Hi Milosz -

>> test 5 (parse event tests) seems to be badly broken.
>>
>> Is this just our problem or is it broken for everyone?
>
> I'm not sure if the reason is the same but this test was broken in
> LAVA for some time now. The latest result on 3.10.0-1-linaro-omap
> kernel looks like this:
>
> perf test - parse events tests
> :Can't open event dir : No such file or directory
> Can't open event dir : No such file or directory
> Warning : function scsi_trace_parse_cdb not defined
> Warning : function scsi_trace_parse_cdb not defined
> Warning : function scsi_trace_parse_cdb not defined
> Warning : function scsi_trace_parse_cdb not defined
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : function jiffies_to_msecs not defined
> Warning : function jiffies_to_msecs not defined
> Warning : bad op token {
> Warning : bad op token {
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : Error : expected type 4 but read 0
> Warning : bad op token {
> Warning : bad op token {
> Warning : bad op token {
> Warning : bad op token {
> Warning : bad op token {
> Warning : unknown op '{'
> Warning : unknown op '{'
> FAIL

Thanks.

I guess it is simply broken upstream, or we missed a point somewhere.

Llct does have one patch compared to vanilla 3.10-rc6 but that's it

diff --git a/tools/perf/config/utilities.mak b/tools/perf/config/utilities.mak
index 8ef3bd3..3e89719 100644
--- a/tools/perf/config/utilities.mak
+++ b/tools/perf/config/utilities.mak
@@ -173,7 +173,7 @@ _ge-abspath = $(if $(is-executable),$(1))
 # Usage: absolute-executable-path-or-empty = $(call
get-executable-or-default,variable,default)
 #
 define get-executable-or-default
-$(if $($(1)),$(call _ge_attempt,$($(1)),$(1)),$(call _ge_attempt,$(2),$(1)))
+$(if $($(1)),$(call _ge_attempt,$($(1)),$(1)),$(call _ge_attempt,$(2)))
 endef
 _ge_attempt = $(if
$(get-executable),$(get-executable),$(_gea_warn)$(call _gea_err,$(2)))
 _gea_warn = $(warning The path '$(1)' is not executable.)


What's the plan for tests that are in Lava that are themselves
partially broken?  We should snip or force the results, patch to turn
off those tests?

-Andy

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: [meta-linaro-toolchain][PATCH] external-linaro-toolchain-versions: Fix NameError: global name 'CmdError' is not defined

2013-06-26 Thread Martin Jansa
Great, can you apply it also to dylan branch? Thanks


On Wed, Jun 26, 2013 at 11:43 AM, Fathi Boudra wrote:

> Thanks. Applied.
>
> On 26 June 2013 10:50, Martin Jansa  wrote:
> > * fails with:
> >   ERROR: Execution of event handler
> 'external_linaro_toolchain_version_handler' failed
> >   Traceback (most recent call last):
> > File "external_linaro_toolchain_version_handler(e)", line 12, in
> external_linaro_toolchain_version_handler(e= at 0x7759a50>)
> > File "external-linaro-toolchain-versions.inc", line 4, in
> elt_get_gdb_version(d=)
> >   NameError: global name 'CmdError' is not defined
> >
> > Signed-off-by: Martin Jansa 
> > ---
> >  .../conf/distro/include/external-linaro-toolchain-versions.inc
>  | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git
> a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
> b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
> > index 92862af..0254895 100644
> > ---
> a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
> > +++
> b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
> > @@ -86,7 +86,7 @@ def elt_get_kernel_version(d):
> >  def elt_get_gdb_version(d):
> > try:
> > stdout, stderr = elt_run(d, 'gdb', '-v')
> > -   except CmdError:
> > +   except bb.process.CmdError:
> > return 'UNKNOWN'
> > else:
> > first_line = stdout.splitlines()[0]
> > --
> > 1.8.2.1
> >
> >
> > ___
> > linaro-dev mailing list
> > linaro-dev@lists.linaro.org
> > http://lists.linaro.org/mailman/listinfo/linaro-dev
>
>
>
> --
> Fathi Boudra
> Builds and Baselines Manager | Release Manager
> Linaro.org | Open source software for ARM SoCs
>
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: [meta-linaro-toolchain][PATCH] external-linaro-toolchain-versions: Fix NameError: global name 'CmdError' is not defined

2013-06-26 Thread Fathi Boudra
On 26 June 2013 15:37, Martin Jansa  wrote:
> Great, can you apply it also to dylan branch? Thanks

Done.

> On Wed, Jun 26, 2013 at 11:43 AM, Fathi Boudra 
> wrote:
>>
>> Thanks. Applied.
>>
>> On 26 June 2013 10:50, Martin Jansa  wrote:
>> > * fails with:
>> >   ERROR: Execution of event handler
>> > 'external_linaro_toolchain_version_handler' failed
>> >   Traceback (most recent call last):
>> > File "external_linaro_toolchain_version_handler(e)", line 12, in
>> > external_linaro_toolchain_version_handler(e=> > at
>> > 0x7759a50>)
>> > File "external-linaro-toolchain-versions.inc", line 4, in
>> > elt_get_gdb_version(d=)
>> >   NameError: global name 'CmdError' is not defined
>> >
>> > Signed-off-by: Martin Jansa 
>> > ---
>> >  .../conf/distro/include/external-linaro-toolchain-versions.inc
>> > | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git
>> > a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
>> > b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
>> > index 92862af..0254895 100644
>> > ---
>> > a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
>> > +++
>> > b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc
>> > @@ -86,7 +86,7 @@ def elt_get_kernel_version(d):
>> >  def elt_get_gdb_version(d):
>> > try:
>> > stdout, stderr = elt_run(d, 'gdb', '-v')
>> > -   except CmdError:
>> > +   except bb.process.CmdError:
>> > return 'UNKNOWN'
>> > else:
>> > first_line = stdout.splitlines()[0]
>> > --
>> > 1.8.2.1
>> >
>> >
>> > ___
>> > linaro-dev mailing list
>> > linaro-dev@lists.linaro.org
>> > http://lists.linaro.org/mailman/listinfo/linaro-dev
>>
>>
>>
>> --
>> Fathi Boudra
>> Builds and Baselines Manager | Release Manager
>> Linaro.org | Open source software for ARM SoCs
>
>



--
Fathi Boudra
Builds and Baselines Manager | Release Manager
Linaro.org | Open source software for ARM SoCs

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Muti touch device android failed to recognise

2013-06-26 Thread dani maoz
Hi
I have created a virtual multi touch virtual driver,
I see that Event hub Detect the device but when i transmit events , no
movement occurred on the screen (No X or Y changed) I tried to use protocol
A pr Protocol B same result. why the events not transmitted to
framework Any Idea


See below the logs
(Pandaboard Linaro 4.1.2)

EventHub

/EventHub( 1775): New device: id=7, fd=195, path='/dev/input/event3',
name='test_mt_touch', classes=0x14, configuration='', keyLayout='',
keyCharacterMap='', builtinKeyboard=false, usingSuspendBlockIoctl=false,
usingClockIoctl=false
I/InputReader( 1775): Device reconfigured: id=7, name='test_mt_touch', size
1280x720, orientation 0, mode 3, display id 0
I/InputReader( 1775): Device added: id=7, name='test_mt_touch',
sources=0x2002

Event transmitted  from driver using getevent -lt /dev/input/event3
[3859.719026] EV_ABS   ABS_MT_POSITION_X00c8
[3859.719056] EV_ABS   ABS_MT_POSITION_Y00c8
[3859.719056] EV_ABS   ABS_MT_WIDTH_MAJOR   002c
[3859.719056] EV_ABS   ABS_MT_TOUCH_MAJOR   
[3859.719056] EV_SYN   SYN_MT_REPORT
[3859.722932] EV_SYN   SYN_REPORT   
[3863.303383] EV_ABS   ABS_MT_POSITION_X00c8
[3863.303383] EV_ABS   ABS_MT_POSITION_Y00c8
[3863.303414] EV_ABS   ABS_MT_WIDTH_MAJOR   002c
[3863.303414] EV_ABS   ABS_MT_TOUCH_MAJOR   0028
[3863.303414] EV_SYN   SYN_MT_REPORT
[3863.303475] EV_SYN   SYN_REPORT   
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


[no subject]

2013-06-26 Thread Harigopal Gollamudi
-- 
Thanks and Regards,
HariGopal G
Android Engineer
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev