Re: OMAP baseline test results for v4.1-rc5

2015-06-01 Thread Tero Kristo 

On 06/01/2015 08:49 AM, Paul Walmsley wrote:

+ Tero

Hello Jeroen,

On Mon, 1 Jun 2015, Jeroen Hofstee wrote:


On 30-05-15 17:56, Jeroen Hofstee wrote:

Hello Paul,

On 30-05-15 17:50, Paul Walmsley wrote:

Here are some basic OMAP test results for Linux v4.1-rc5.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v4.1-rc5/20150529162206/



The cmt3517 seems to have these some In-Band errors.
Do you happen to know where these are coming from?



git bisect + some workarounds seem to indicate:

d744ce37b721d6678f420ba0fb058f615eb015b6 is the first bad commit
commit d744ce37b721d6678f420ba0fb058f615eb015b6
Author: Tero Kristo t-kri...@ti.com
Date:   Tue Feb 24 16:22:45 2015 +0200

 ARM: dts: omap3: add minimal l4 bus layout with control module support

 This patch creates an l4_core interconnect for OMAP3, and moves some
 of the generic peripherals under it. System control module nodes are
 moved under this new interconnect also, and the SCM clock layout
 is changed to use the renamed SCM node as the clock provider.

 Signed-off-by: Tero Kristo t-kri...@ti.com
 Reported-by: Tony Lindgren t...@atomide.com

I haven't looked further into it yet,


Interesting; thanks for the bisect.  In the mainline kernel, this appears
to be commit b8845074cfbbd1d1b46720a1b563d7b4240dac21.

I took a quick look at the control module offsets in that patch, and they
appear to match what's in the SPRUGR0B PDF.  Will try a few test boots
here to confirm your findings.

Tero, care to take a look?


Yes, seems I have introduced a bug with this patch on am35xx only. I 
missed updating part of the am35xx related dts files.


Will post a fix in a bit.

-Tero
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v4.1-rc5

2015-05-31 Thread Jeroen Hofstee 

Hi,

On 30-05-15 17:56, Jeroen Hofstee wrote:

Hello Paul,

On 30-05-15 17:50, Paul Walmsley wrote:

Here are some basic OMAP test results for Linux v4.1-rc5.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v4.1-rc5/20150529162206/



The cmt3517 seems to have these some In-Band errors.
Do you happen to know where these are coming from?



git bisect + some workarounds seem to indicate:

d744ce37b721d6678f420ba0fb058f615eb015b6 is the first bad commit
commit d744ce37b721d6678f420ba0fb058f615eb015b6
Author: Tero Kristo t-kri...@ti.com
Date:   Tue Feb 24 16:22:45 2015 +0200

ARM: dts: omap3: add minimal l4 bus layout with control module support

This patch creates an l4_core interconnect for OMAP3, and moves some
of the generic peripherals under it. System control module nodes are
moved under this new interconnect also, and the SCM clock layout
is changed to use the renamed SCM node as the clock provider.

Signed-off-by: Tero Kristo t-kri...@ti.com
Reported-by: Tony Lindgren t...@atomide.com

I haven't looked further into it yet,

Regards, Jeroen
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v4.1-rc5

2015-05-31 Thread Paul Walmsley 
+ Tero

Hello Jeroen,

On Mon, 1 Jun 2015, Jeroen Hofstee wrote:

 On 30-05-15 17:56, Jeroen Hofstee wrote:
  Hello Paul,
  
  On 30-05-15 17:50, Paul Walmsley wrote:
   Here are some basic OMAP test results for Linux v4.1-rc5.
   Logs and other details at:
   
   http://www.pwsan.com/omap/testlogs/test_v4.1-rc5/20150529162206/
   
  
  The cmt3517 seems to have these some In-Band errors.
  Do you happen to know where these are coming from?
  
 
 git bisect + some workarounds seem to indicate:
 
 d744ce37b721d6678f420ba0fb058f615eb015b6 is the first bad commit
 commit d744ce37b721d6678f420ba0fb058f615eb015b6
 Author: Tero Kristo t-kri...@ti.com
 Date:   Tue Feb 24 16:22:45 2015 +0200
 
 ARM: dts: omap3: add minimal l4 bus layout with control module support
 
 This patch creates an l4_core interconnect for OMAP3, and moves some
 of the generic peripherals under it. System control module nodes are
 moved under this new interconnect also, and the SCM clock layout
 is changed to use the renamed SCM node as the clock provider.
 
 Signed-off-by: Tero Kristo t-kri...@ti.com
 Reported-by: Tony Lindgren t...@atomide.com
 
 I haven't looked further into it yet,

Interesting; thanks for the bisect.  In the mainline kernel, this appears 
to be commit b8845074cfbbd1d1b46720a1b563d7b4240dac21.

I took a quick look at the control module offsets in that patch, and they 
appear to match what's in the SPRUGR0B PDF.  Will try a few test boots 
here to confirm your findings.

Tero, care to take a look?

- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

OMAP baseline test results for v4.1-rc5

2015-05-30 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v4.1-rc5.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v4.1-rc5/20150529162206/


Test summary


Build: uImage:
Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,
  omap1_defconfig_5912osk_only

Build: uImage+dtb:
Pass (13/13): omap2plus_defconfig_am33xx_only/am335x-bone,
  omap2plus_defconfig/omap4-panda,
  omap2plus_defconfig/omap4-panda-es,
  omap2plus_defconfig/omap4-var-stk-om44,
  omap2plus_defconfig/omap3-evm-37xx,
  omap2plus_defconfig_n800_only_a/omap2420-n800,
  omap2plus_defconfig/omap2430-sdp,
  omap2plus_defconfig/am3517-evm,
  omap2plus_defconfig/omap3-beagle,
  omap2plus_defconfig/omap3-beagle-xm,
  omap2plus_defconfig/omap3-sbc-t3517,
  omap2plus_defconfig/omap5-uevm,
  omap2plus_defconfig/omap5-sbc-t54

Build: zImage:
Pass (17/17): omap2plus_defconfig, omap2plus_defconfig_am33xx_only,
  omap2plus_defconfig_n800_only_a,
  omap2plus_defconfig_n800_multi_omap2xxx,
  omap2plus_defconfig_2430sdp_only,
  omap2plus_defconfig_cpupm, omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  omap2plus_defconfig_omap5_only,
  omap2plus_defconfig_dra7xx_only,
  omap2plus_defconfig_am43xx_only,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap3430_ldp_allnoconfig,
  rmk_omap4430_sdp_oldconfig,
  rmk_omap4430_sdp_allnoconfig, multi_v7_defconfig

Build warnings from toolchain: uImage:
FAIL ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,
  omap1_defconfig_5912osk_only

Build warnings from toolchain: uImage+dtb:
(none)

Build warnings from toolchain: zImage:
FAIL (14/17): omap2plus_defconfig, omap2plus_defconfig_am33xx_only,
  omap2plus_defconfig_n800_only_a,
  omap2plus_defconfig_n800_multi_omap2xxx,
  omap2plus_defconfig_2430sdp_only,
  omap2plus_defconfig_cpupm, omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  omap2plus_defconfig_omap5_only,
  omap2plus_defconfig_dra7xx_only,
  omap2plus_defconfig_am43xx_only,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 2/17): 2430sdp, 5430es2sbct54
skip ( 2/17): 5912osk, 3517evm
Pass (13/17): am335xbonelt, am335xbone, 4430es2panda, 4460pandaes,
  4460varsomom, 37xxevm, 3530es3beagle, 3530es31beagle,
  3730beaglexm, 3730es12beaglexm, cmt3517, 5430es2uevm,
  2420n800

Kernel warnings during boot to userspace:
FAIL ( 2/17): 4430es2panda, cmt3517

PM: chip retention via suspend:
FAIL ( 6/12): am335xbonelt, 4430es2panda, 4460varsomom, 2430sdp,
  5430es2uevm, 5430es2sbct54
Pass ( 6/12): 4460pandaes, 37xxevm, 3530es3beagle, 3530es31beagle,
  3730beaglexm, 3730es12beaglexm

PM: chip retention via dynamic idle:
FAIL ( 6/12): am335xbonelt, 4430es2panda, 4460varsomom, 2430sdp,
  5430es2uevm, 5430es2sbct54
Pass ( 6/12): 4460pandaes, 37xxevm, 3530es3beagle, 3530es31beagle,
  3730beaglexm, 3730es12beaglexm

PM: chip off (except CORE, due to errata) via suspend:
Pass ( 1/ 1): 3730beaglexm

PM: chip off (except CORE, due to errata) via dynamic idle:
Pass ( 1/ 1): 3730beaglexm

PM: chip off via suspend:
Pass ( 4/ 4): 37xxevm, 3530es3beagle, 3530es31beagle,
  3730es12beaglexm

PM: chip off via dynamic idle:
Pass ( 4/ 4): 37xxevm, 3530es3beagle, 3530es31beagle,
  3730es12beaglexm

Kernel warnings during PM test:
FAIL ( 1/17): 4430es2panda

Obsolete Kconfig symbols:
FAIL ( 1/20): multi_v7_defconfig


vmlinux object size
(delta in bytes from test_v4.1-rc4 (e26081808edadfd257c6c9d81014e3b25e9a6118)):
   text data  bsstotal  kernel
  +165800+1658  omap1_defconfig
  +165800+1658  omap1_defconfig_1510innovator_only
  +165800+1658  omap1_defconfig_5912osk_only
 +28262   +529280   +81190  multi_v7_defconfig
  +267800+2678  omap2plus_defconfig
  +21300   -8+2122  omap2plus_defconfig_2430sdp_only
  +2550  +640+2614  omap2plus_defconfig_am33xx_only
  +255000+2550  omap2plus_defconfig_am43xx_only
  +267800+2678  omap2plus_defconfig_cpupm
  +261400+2614

Re: OMAP baseline test results for v4.1-rc5

2015-05-30 Thread Jeroen Hofstee 

Hello Paul,

On 30-05-15 17:50, Paul Walmsley wrote:

Here are some basic OMAP test results for Linux v4.1-rc5.
Logs and other details at:

 http://www.pwsan.com/omap/testlogs/test_v4.1-rc5/20150529162206/



The cmt3517 seems to have these some In-Band errors.
Do you happen to know where these are coming from?

Regards,
Jeroen

[0.476773] In-band Error seen by MPU  at address 0
[0.476802] [ cut here ]
[0.476848] WARNING: CPU: 0 PID: 1 at drivers/bus/omap_l3_smx.c:166 
omap3_l3_app_irq+0xcc/0x124()

[0.476865] Modules linked in:
[0.476899] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 
4.1.0-rc5-143184-gba155e2 #1

[0.476916] Hardware name: Generic AM3517 (Flattened Device Tree)
[0.476964] [c0016504] (unwind_backtrace) from [c0012a44] 
(show_stack+0x10/0x14)
[0.476997] [c0012a44] (show_stack) from [c05ddbd4] 
(dump_stack+0x80/0x9c)
[0.477028] [c05ddbd4] (dump_stack) from [c004000c] 
(warn_slowpath_common+0x78/0xb4)
[0.477056] [c004000c] (warn_slowpath_common) from [c0040064] 
(warn_slowpath_null+0x1c/0x24)
[0.477083] [c0040064] (warn_slowpath_null) from [c0370ed0] 
(omap3_l3_app_irq+0xcc/0x124)
[0.477121] [c0370ed0] (omap3_l3_app_irq) from [c009804c] 
(handle_irq_event_percpu+0x64/0x204)
[0.477150] [c009804c] (handle_irq_event_percpu) from [c0098228] 
(handle_irq_event+0x3c/0x5c)
[0.477181] [c0098228] (handle_irq_event) from [c009b09c] 
(handle_level_irq+0xb4/0x13c)
[0.477209] [c009b09c] (handle_level_irq) from [c00978f0] 
(generic_handle_irq+0x20/0x30)
[0.477235] [c00978f0] (generic_handle_irq) from [c0097a08] 
(__handle_domain_irq+0x68/0xdc)
[0.477263] [c0097a08] (__handle_domain_irq) from [c0009480] 
(omap_intc_handle_irq+0xb4/0xc4)
[0.477299] [c0009480] (omap_intc_handle_irq) from [c05e48a4] 
(__irq_svc+0x44/0x5c)

[0.477317] Exception stack(0xce0a3d00 to 0xce0a3d48)
[0.477342] 3d00: 0001 ce0a1138  ce0a0b80 6153 
ce013c60 ce013c60 
[0.477365] 3d20: 001a 6153 ce013c38   
ce0a3d48 c008dde8 c05e4424

[0.477382] 3d40: 2153 


--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html