Subject: OMAP v3.10-rc regressions that no one's fixed

From: [email-masked] (Lokesh Vutla)
Date: Mon, 10 Jun 2013 18:43:41 +0530

Hi Paul,
On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
>
> Hi folks -- particularly TIers working on mainline,
>
> There are several regressions that started with v3.10-rc that no one's
> fixed for over a month.  Some of them should be quite easy:
>
> * 37xx EVM: boot fails
>    - as of v3.10-rc1
>    - Cause unknown
>
> * 2420N800, 2430sdp: failed to get counter_32k resource
>    - "omap2_sync32k_clocksource_init: failed to get counter_32k resource"
>    - Cause unknown
>
> * 2430SDP, 3730 Beagle XM, 3530 Beagle, 3517EVM, CM-T3517: {dmic,mcpdm} lookup failure
>    - Cause unknown
>    - These IP blocks don't exist on OMAP3xxx/AM35xx chips
>
> * 3730 Beagle XM, am335xbone, CM-T3517: uart4_rx.uart4_rx mux failure
Just booted up my BeagleBone. I didn't see any error for uart4_rx in my 
boot log.
Since I don't have other boards, I wanted to reproduce this on my 
BeagelBone.
Please let me know if I am missing something.

Thanks and regards,
Lokesh

>    - Cause unknown
>
> (For more details, see the logs at the link below.)
>
> It would be good if people could step up to fix these before v3.10 comes
> out.
>
>
> - Paul
>
> ---------- Forwarded message ----------
> Date: Mon, 10 Jun 2013 02:00:50 +0000 (UTC)
> From: Paul Walmsley <[email-masked]>
> To: linux-omap at vger.kernel.org
> Cc: linux-arm-kernel at lists.infradead.org
> Subject: OMAP baseline test results for v3.10-rc5
>
>
> Here are some basic OMAP test results for Linux v3.10-rc5.
> Logs and other details at:
>
>      http://www.pwsan.com/omap/testlogs/test_v3.10-rc5/20130609031534/
>
>
> Test summary
> ------------
>
> Build: uImage:
>      Pass (16/16): am33xx_only, n800_multi_omap2xxx, n800_only_a,
>                    omap1_defconfig, omap1_defconfig_1510innovator_only,
>                    omap1_defconfig_5912osk_only, omap2plus_defconfig,
>                    omap2plus_defconfig_2430sdp_only
>                    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
>
> Build: zImage:
>      Pass ( 1/ 1): omap2plus_defconfig
>
> Boot to userspace:
>      FAIL ( 3/12): 37xxevm, am335xbone, am335xbonelt
>      Pass ( 9/12): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
>                    3730beaglexm, 4430es2panda, 4460pandaes, 5912osk,
>                    cmt3517
>
> PM: chip retention via suspend:
>      FAIL ( 3/ 6): 2430sdp, 37xxevm, 4430es2panda
>      Pass ( 3/ 6): 3530es3beagle, 3730beaglexm, 4460pandaes
>
> PM: chip retention via dynamic idle:
>      FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
>      Pass ( 2/ 6): 3530es3beagle, 3730beaglexm
>
> PM: chip off except CORE via suspend:
>      Pass ( 1/ 1): 3730beaglexm
>
> PM: chip off except CORE via dynamic idle:
>      Pass ( 1/ 1): 3730beaglexm
>
> PM: chip off via suspend:
>      FAIL ( 3/ 4): 37xxevm, 4430es2panda, 4460pandaes
>      Pass ( 1/ 4): 3530es3beagle
>
> PM: chip off via dynamic idle:
>      FAIL ( 3/ 4): 37xxevm, 4430es2panda, 4460pandaes
>      Pass ( 1/ 4): 3530es3beagle
>
>
> Failing tests: fixed by posted patches
> --------------------------------------
>
> (none)
>
>
> Failing tests: needing investigation
> ------------------------------------
>
> Boot tests:
>
> * 3517EVM & CM-T3517: boot hangs with NFS root
>    - Likely some Kconfig, board file, and PM issues with EMAC
>    - Longstanding bug
>    - Not currently part of the automated test suite
>
> * 37xx EVM: boot fails
>    - as of v3.10-rc1
>    - Cause unknown
>
> Boot warnings:
>
> * 2420N800, 2430sdp: failed to get counter_32k resource
>    - "omap2_sync32k_clocksource_init: failed to get counter_32k resource"
>    - Cause unknown
>
> * 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
>
> * 2430SDP, 3730 Beagle XM, 3530 Beagle, 3517EVM, CM-T3517: {dmic,mcpdm} lookup failure
>    - Cause unknown
>    - These IP blocks don't exist on OMAP3xxx/AM35xx chips
>
> * 3730 Beagle XM, am335xbone, CM-T3517: uart4_rx.uart4_rx mux failure
>    - Cause unknown
>
> PM tests:
>
> * 2430sdp: power domains not entering retention
>    - Cause unknown
>
> * 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
>
> * 4430es2panda: pwrdm state mismatch on CAM, DSS
>
> * 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
>    - http://marc.info/?l=linux-arm-kernel&m=136432340618226&w=2
>
> * 4430es2panda: MPU, ABE didn't enter target state
>    - New for v3.10-rc
>
> * 4460pandaes: pwrdm state mismatch on DSS, ABE, IVAHD, TESLA
>
> * 4460pandaes: chip not entering retention in dynamic idle
>    - Presumably 4430es2panda also fails this
>    - Suspend-to-RAM enters full chip retention
>
> Other:
>
> * 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 and Santosh Shilimkar report this does not appear with
>      the same X-loader/bootloader on his 4430ES2.3 Panda, so could be
>      ES-level dependent
>
>
> Failing tests: reported by others
> ---------------------------------
>
> - RTC wakeup from suspend broken on 3730beaglexm
>    - as of v3.10-rc1
>    - discussion here: http://marc.info/?l=linux-omap&m=136915841625434&w=2
>
>
>
> vmlinux object size
> (delta in bytes from test_v3.10-rc4
> (d683b96b072dc4680fc74964eca77e6a23d1fa6e)):
>     text     data      bss    total  kernel
>     +287       +8        0     +295  am33xx_only
>     +786       +8        0     +794  n800_multi_omap2xxx
>     +818       +8        0     +826  n800_only_a
>    +1207      +16        0    +1223  omap1_defconfig
>    +1207      +56        0    +1263  omap1_defconfig_1510innovator_only
>    +1239      -16        0    +1223  omap1_defconfig_5912osk_only
>    +4451       +8        0    +4459  omap2plus_defconfig
>    +1123       +8        0    +1131  omap2plus_defconfig_2430sdp_only
>     +355       +8        0     +363  omap2plus_defconfig_cpupm
>     +423      +72        0     +495  omap2plus_defconfig_no_pm
>     +355       +8        0     +363  omap2plus_defconfig_omap2_4_only
>     +355       +8        0     +363  omap2plus_defconfig_omap3_4_only
>     +192        0        0     +192  rmk_omap3430_ldp_allnoconfig
>     +443      -24        0     +419  rmk_omap3430_ldp_oldconfig
>     +192        0        0     +192  rmk_omap4430_sdp_allnoconfig
>     +722      +16        0     +738  rmk_omap4430_sdp_oldconfig
>
>
> Boot-time memory difference
> (delta in bytes from test_v3.10-rc4
> (d683b96b072dc4680fc74964eca77e6a23d1fa6e))
>    avail  rsrvd   high  freed  board          kconfig
>       8k    -8k      .      .  2420n800       n800_only_a
>      -8k     8k      .      .  2430sdp        omap2plus_defconfig
>      -8k     8k      .      .  3517evm        omap2plus_defconfig
>      -8k     8k      .      .  3530es3beagle  omap2plus_defconfig
>      -8k     8k      .      .  3730beaglexm   omap2plus_defconfig
>      -8k     8k      .      .  4430es2panda   omap2plus_defconfig
>      -8k     8k      .      .  4460pandaes    omap2plus_defconfig
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>