RE: OMAP baseline test results for v3.9-rc1

2013-03-26 Thread Paul Walmsley 
Hi,

On Thu, 14 Mar 2013, Hiremath, Vaibhav wrote:

> > -Original Message-
> > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> > ow...@vger.kernel.org] On Behalf Of Paul Walmsley
> > Sent: Tuesday, March 12, 2013 10:10 PM
> > To: linux-omap@vger.kernel.org
> > Cc: linux-arm-ker...@lists.infradead.org
> > Subject: OMAP baseline test results for v3.9-rc1
> > 
> > 
> > Here are some basic OMAP test results for Linux v3.9-rc1.
> > Logs and other details at:
> > 
> > http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
> > 
> > 
> > Test summary
> > 
> > 
> > Build:
> > FAIL ( 4/16): am33xx_only, omap1_defconfig,
> This requires some cleanup in Makefile and Kconfig handling,
> 
> Either you disable SMP support for non-SMP devices like AM33xx 
> 
> OR
> 
> Fix the Makefile to resolve the build dependencies (may not be trivial)
> 
> OR
> 
> Make functions __weak so that build will go through.
> 
> 
> 
> I have created below patch, if it is ok with you then I can
> Submit patch for the same (build tested with am33xx_only and 
> omap2plus_defconfig).

Santosh's suggestion seems the right way to go.  Care to implement a patch 
for #2 above?


- 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

Re: OMAP baseline test results for v3.9-rc1

2013-03-18 Thread Paul Walmsley 
Hi,

here's the restated delta from v3.8 -> v3.9-rc1, after some script bug 
fixes.

On Tue, 12 Mar 2013, Paul Walmsley wrote:

> vmlinux object size
> (delta in bytes from test_v3.8 (19f949f52599ba7c3f67a5897ac6be14bfcb1200)):
>text data  bsstotal  kernel
> +195310   +37968+1364  +234642  omap2plus_defconfig
> +185362   +37128+1364  +223854  omap2plus_defconfig_cpupm
> +186719   +31416+1300  +219435  omap2plus_defconfig_omap2_4_only
> +181125   +41432+1300  +223857  omap2plus_defconfig_omap3_4_only
>  +10460   +10272+1184   +21916  rmk_omap3430_ldp_allnoconfig
>  +40867   +14672 +972   +56511  rmk_omap4430_sdp_oldconfig
> 
> Looks like v3.9 is well on target to exceed even the previous 
> per-release bloat records.
> 
> There are some entries missing from the above table; this is probably due 
> to some bug in my scripts that needs to be dealt with.

And here's the correct results.

vmlinux object size
(delta in bytes from test_v3.8 
(19f949f52599ba7c3f67a5897ac6be14bfcb1200)):
   text data  bsstotal  kernel
-557629   +23472-9252  -543409  n800_multi_omap2xxx
-557204   +26680-9280  -539804  n800_only_a
 +49056+2992 +424   +52472  omap1_defconfig_1510innovator_only
+195310   +37968+1364  +234642  omap2plus_defconfig
+185362   +37128+1364  +223854  omap2plus_defconfig_cpupm
+192610   +36304+1364  +230278  omap2plus_defconfig_no_pm
+186719   +31416+1300  +219435  omap2plus_defconfig_omap2_4_only
+181125   +41432+1300  +223857  omap2plus_defconfig_omap3_4_only
 +10460   +10272+1184   +21916  rmk_omap3430_ldp_allnoconfig
 +40004   +27640 +788   +68432  rmk_omap3430_ldp_oldconfig
 +10348   +10272+1296   +21916  rmk_omap4430_sdp_allnoconfig
 +40867   +14672 +972   +56511  rmk_omap4430_sdp_oldconfig

The massive decrease in N800 kernel size is a result of an all-out attempt 
to keep the kernel booting on N800, which has a 2MB kernel size limitation 
in the bootloader.

Same crazy bloat in the OMAP2+ kernels, and it's probably due to the 
CONFIG_ARCH_MULTIPLATFORM changes.  Hey, at least we don't have to worry 
about supporting embedded use-cases any more on ARM ;-)


- 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

Re: OMAP baseline test results for v3.9-rc1

2013-03-14 Thread Paul Walmsley 
Hi Aaro,

On Tue, 12 Mar 2013, Aaro Koskinen wrote:

> On Tue, Mar 12, 2013 at 04:40:19PM +, Paul Walmsley wrote:
> > * 2420N800: powers down 30 seconds after boot
> >   - Presumably due to missing CBUS patches for watchdog control
> >   - http://lkml.org/lkml/2012/9/3/265
> >   - http://marc.info/?l=linux-omap&m=135274739624125&w=2
> >   - http://marc.info/?l=linux-omap&m=135664195831104&w=2
> >   - Should be working in v3.9-rc1 when CONFIG_RETU_WATCHDOG=y ?
> 
> Yes, you need also CONFIG_I2C_CBUS_GPIO and CONFIG_MFD_RETU.

Just enabled these two, and finally the N800 doesn't power down!  Nice 
work!  Amazing how exciting something like this can be :-)

This will be reflected in the v3.9-rc2 test log & the v3.9-rc1 log has now 
been fixed on the web.


- 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

Re: OMAP baseline test results for v3.9-rc1

2013-03-14 Thread Santosh Shilimkar 
On Thursday 14 March 2013 04:59 PM, Hiremath, Vaibhav wrote:
> 
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of Paul Walmsley
>> Sent: Tuesday, March 12, 2013 10:10 PM
>> To: linux-omap@vger.kernel.org
>> Cc: linux-arm-ker...@lists.infradead.org
>> Subject: OMAP baseline test results for v3.9-rc1
>>
>>
>> Here are some basic OMAP test results for Linux v3.9-rc1.
>> Logs and other details at:
>>
>> http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
>>
>>
>> Test summary
>> 
>>
>> Build:
>> FAIL ( 4/16): am33xx_only, omap1_defconfig,
> This requires some cleanup in Makefile and Kconfig handling,
> 
> Either you disable SMP support for non-SMP devices like AM33xx 
> 
> OR
> 
> Fix the Makefile to resolve the build dependencies (may not be trivial)
> 
This one... Better things is not to build the OMAP4 files for AM33XX only build.
Even if it is not trivial, its right way of fixing the issue.

Regards,
Santosh
--
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 v3.9-rc1

2013-03-14 Thread Hiremath, Vaibhav 

> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Paul Walmsley
> Sent: Tuesday, March 12, 2013 10:10 PM
> To: linux-omap@vger.kernel.org
> Cc: linux-arm-ker...@lists.infradead.org
> Subject: OMAP baseline test results for v3.9-rc1
> 
> 
> Here are some basic OMAP test results for Linux v3.9-rc1.
> Logs and other details at:
> 
> http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
> 
> 
> Test summary
> 
> 
> Build:
> FAIL ( 4/16): am33xx_only, omap1_defconfig,
This requires some cleanup in Makefile and Kconfig handling,

Either you disable SMP support for non-SMP devices like AM33xx 

OR

Fix the Makefile to resolve the build dependencies (may not be trivial)

OR

Make functions __weak so that build will go through.



I have created below patch, if it is ok with you then I can
Submit patch for the same (build tested with am33xx_only and 
omap2plus_defconfig).




diff --git a/arch/arm/mach-omap2/common.h b/arch/arm/mach-omap2/common.h
index 0a6b9c7..cb0d55d 100644
--- a/arch/arm/mach-omap2/common.h
+++ b/arch/arm/mach-omap2/common.h
@@ -233,9 +233,9 @@ extern void omap_do_wfi(void);
 /* Needed for secondary core boot */
 extern void omap_secondary_startup(void);
 extern void omap_secondary_startup_4460(void);
-extern u32 omap_modify_auxcoreboot0(u32 set_mask, u32 clear_mask);
-extern void omap_auxcoreboot_addr(u32 cpu_addr);
-extern u32 omap_read_auxcoreboot0(void);
+extern u32 __weak omap_modify_auxcoreboot0(u32 set_mask, u32 clear_mask);
+extern void __weak omap_auxcoreboot_addr(u32 cpu_addr);
+extern u32 __weak omap_read_auxcoreboot0(void);

 extern void omap4_cpu_die(unsigned int cpu);

@@ -249,7 +249,7 @@ extern int omap4_mpuss_init(void);
 extern int omap4_enter_lowpower(unsigned int cpu, unsigned int power_state);
 extern int omap4_finish_suspend(unsigned long cpu_state);
 extern void omap4_cpu_resume(void);
-extern int omap4_hotplug_cpu(unsigned int cpu, unsigned int power_state);
+extern int __weak omap4_hotplug_cpu(unsigned int cpu, unsigned int 
power_state);
 extern u32 omap4_mpuss_read_prev_context_state(void);
 #else
 static inline int omap4_enter_lowpower(unsigned int cpu,
diff --git a/arch/arm/mach-omap2/omap-wakeupgen.h 
b/arch/arm/mach-omap2/omap-wakeupgen.h
index b0fd16f..94f5281 100644
--- a/arch/arm/mach-omap2/omap-wakeupgen.h
+++ b/arch/arm/mach-omap2/omap-wakeupgen.h
@@ -33,6 +33,6 @@
 #define OMAP_TIMESTAMPCYCLEHI  0xc0c

 extern int __init omap_wakeupgen_init(void);
-extern void __iomem *omap_get_wakeupgen_base(void);
-extern int omap_secure_apis_support(void);
+extern void __weak __iomem *omap_get_wakeupgen_base(void);
+extern int __weak omap_secure_apis_support(void);
 #endif



Thanks,
Vaibhav
--
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 v3.9-rc1

2013-03-13 Thread Paul Walmsley 
Hi Igor,

On Wed, 13 Mar 2013, Igor Grinberg wrote:

> This should have been fixed by:
> ff95793 (ARM: OMAP3: cm-t3517: add MMC support)
> 
> I also can't find the MMC rootfs boot log on your website.

Hmm, I thought I had switched the CM-T3517 over to use MMC booting, but 
looks like it's still trying to use nfsroot.  Thanks for letting me know.  
Will switch to MMC and try again.


- 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

Re: OMAP baseline test results for v3.9-rc1

2013-03-13 Thread Paul Walmsley 
Hi Aaro,

On Tue, 12 Mar 2013, Aaro Koskinen wrote:

> On Tue, Mar 12, 2013 at 04:40:19PM +, Paul Walmsley wrote:
> > * 2420N800: powers down 30 seconds after boot
> >   - Presumably due to missing CBUS patches for watchdog control
> >   - http://lkml.org/lkml/2012/9/3/265
> >   - http://marc.info/?l=linux-omap&m=135274739624125&w=2
> >   - http://marc.info/?l=linux-omap&m=135664195831104&w=2
> >   - Should be working in v3.9-rc1 when CONFIG_RETU_WATCHDOG=y ?
> 
> Yes, you need also CONFIG_I2C_CBUS_GPIO and CONFIG_MFD_RETU.

OK thanks, will add that in for the v3.9-rc2 test.

Would it make sense to add those dependencies to the Kconfig file for 
CONFIG_RETU_WATCHDOG?


- 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

Re: OMAP baseline test results for v3.9-rc1

2013-03-13 Thread Igor Grinberg 
On 03/12/13 18:40, Paul Walmsley wrote:
> 
> Here are some basic OMAP test results for Linux v3.9-rc1.
> Logs and other details at:
> 
> http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/

[...]

> Failing tests: needing investigation
> 

[...]

> * CM-T3517: boot hangs with MMC root
>   - Due to missing MMC setup in board file
>   - http://www.spinics.net/lists/arm-kernel/msg211471.html
>   - Longstanding bug

This should have been fixed by:
ff95793 (ARM: OMAP3: cm-t3517: add MMC support)

I also can't find the MMC rootfs boot log on your website.


-- 
Regards,
Igor.
--
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 v3.9-rc1

2013-03-12 Thread Aaro Koskinen 
Hi,

On Tue, Mar 12, 2013 at 04:40:19PM +, Paul Walmsley wrote:
> * 2420N800: powers down 30 seconds after boot
>   - Presumably due to missing CBUS patches for watchdog control
>   - http://lkml.org/lkml/2012/9/3/265
>   - http://marc.info/?l=linux-omap&m=135274739624125&w=2
>   - http://marc.info/?l=linux-omap&m=135664195831104&w=2
>   - Should be working in v3.9-rc1 when CONFIG_RETU_WATCHDOG=y ?

Yes, you need also CONFIG_I2C_CBUS_GPIO and CONFIG_MFD_RETU.

A.
--
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 v3.9-rc1

2013-03-12 Thread Paul Walmsley 
On Tue, 12 Mar 2013, Paul Walmsley wrote:

> Here are some basic OMAP test results for Linux v3.9-rc1.
> Logs and other details at:
> 
> http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/

...

> Boot to userspace:
> FAIL ( 4/11): 2430sdp, 37xxevm, am335xbone, cmt3517
> Pass ( 7/11): 2420n800, 3517evm, 3530es3beagle,
> 3730beaglexm, 4430es2panda, 5912osk,
> 4460pandaes

It's not correct that 5912osk booted to userspace, given that the kernel 
didn't build.  Looking at the testlogs, it seems to have inadvertently 
booted a 3.8 kernel.  Something else to fix in the scripts.

This has been fixed in the README copy on the web.


- 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 v3.9-rc1

2013-03-12 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9-rc1.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/


Test summary


Build:
FAIL ( 4/16): am33xx_only, omap1_defconfig,
  omap1_defconfig_5912osk_only,
  omap2plus_defconfig_2430sdp_only
Pass (12/16): n800_multi_omap2xxx, n800_only_a,
  omap1_defconfig_1510innovator_only, 
  omap2plus_defconfig, omap2plus_defconfig_cpupm,
  omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  rmk_omap3430_ldp_allnoconfig,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap4430_sdp_allnoconfig
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 4/11): 2430sdp, 37xxevm, am335xbone, cmt3517
Pass ( 7/11): 2420n800, 3517evm, 3530es3beagle,
  3730beaglexm, 4430es2panda, 5912osk,
  4460pandaes
  
PM ret, suspend:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM ret, dynamic idle:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM off, suspend:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm

PM off, dynamic idle:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm


Failing tests: fixed by posted patches
--

Build:

* omap1_defconfig: several problems with mach-omap1/board-h2.c
  - Fixed by Tony: http://www.spinics.net/lists/arm-kernel/msg224133.html

* omap1_defconfig_5912osk_only: implicit declaration of function 
'cpu_is_omap15xx'
  - Fixed by Aaro: http://www.spinics.net/lists/linux-omap/msg87523.html


Failing tests: needing investigation


Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors

Boot tests:

* 2430sdp & 37xxevm: hang during MMC partition probe
  - Cause unknown

* 3517EVM & CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug

* CM-T3517: boot hangs with MMC root
  - Due to missing MMC setup in board file
  - http://www.spinics.net/lists/arm-kernel/msg211471.html
  - Longstanding bug

Boot warnings:

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omap&m=134833869730129&w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
  - need to doublecheck wakeup dependencies
  - (am assuming it's still there; does not boot to userspace)

* 2430sdp: power domains not entering retention
  - Cause unknown
  - (am assuming it's still there; does not boot to userspace)

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79

* 4460pandaes: CORE, L3INIT didn't enter target state
  - Cause unknown; appeared with v3.9-rc1

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate ("debug ignore_loglevel")
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 2420N800: powers down 30 seconds after boot
  - Presumably due to missing CBUS patches for watchdog control
  - http://lkml.org/lkml/2012/9/3/265
  - http://marc.info/?l=linux-omap&m=135274739624125&w=2
  - http://marc.info/?l=linux-omap&m=135664195831104&w=2
  - Should be working in v3.9-rc1 when CONFIG_RETU_WATCHDOG=y ?

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent



vmlinux object size
(delta in bytes from test_v3.8 (19f949f52599ba7c3f67a5897ac6be14bfcb1200)):
   text data  bsstotal  kernel
+195310   +37968+1364  +234642  omap2plus_defconfig
+185362   +37128+1364  +223854  omap2plus_defconfig_cpupm
+186719   +31416+1300  +219435  omap2plus_defconfig_omap2_4_only
+181125   +41432+1300  +223857  omap2plus_defconfig_omap3_4_only
 +10460   +10272+1184   +21916  rmk_omap3430_ldp_allnoconfig
 +40867   +146