* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-10 7:22 ` Paul Walmsley
0 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-10 7:22 UTC (permalink / raw)
To: linux-omap; +Cc: linux-arm-kernel
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
- 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 <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-10 7:22 ` Paul Walmsley
0 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-10 7:22 UTC (permalink / raw)
To: linux-arm-kernel
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
- 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 <paul@pwsan.com>
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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-10 7:22 ` Paul Walmsley
@ 2013-06-10 13:13 ` Lokesh Vutla
-1 siblings, 0 replies; 22+ messages in thread
From: Lokesh Vutla @ 2013-06-10 13:13 UTC (permalink / raw)
To: Paul Walmsley; +Cc: linux-omap, linux-arm-kernel
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 <paul@pwsan.com>
> To: linux-omap@vger.kernel.org
> Cc: linux-arm-kernel@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@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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-10 13:13 ` Lokesh Vutla
0 siblings, 0 replies; 22+ messages in thread
From: Lokesh Vutla @ 2013-06-10 13:13 UTC (permalink / raw)
To: linux-arm-kernel
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 <paul@pwsan.com>
> 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
>
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-10 7:22 ` Paul Walmsley
@ 2013-06-11 7:47 ` Peter Ujfalusi
-1 siblings, 0 replies; 22+ messages in thread
From: Peter Ujfalusi @ 2013-06-11 7:47 UTC (permalink / raw)
To: Paul Walmsley; +Cc: linux-omap, linux-arm-kernel
Hi Paul,
On 06/10/2013 09:22 AM, 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:
>
> * 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
I will send a patch soon to fix these. Need to test the patch(es) first. I
think they surfaced because I have enabled the audio support in
omap2plus_defconfig for OMAP4 and 5 - which require McPDM and DMIC.
Just couple of minutes, and I'll have the fix.
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-11 7:47 ` Peter Ujfalusi
0 siblings, 0 replies; 22+ messages in thread
From: Peter Ujfalusi @ 2013-06-11 7:47 UTC (permalink / raw)
To: linux-arm-kernel
Hi Paul,
On 06/10/2013 09:22 AM, 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:
>
> * 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
I will send a patch soon to fix these. Need to test the patch(es) first. I
think they surfaced because I have enabled the audio support in
omap2plus_defconfig for OMAP4 and 5 - which require McPDM and DMIC.
Just couple of minutes, and I'll have the fix.
--
P?ter
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-10 7:22 ` Paul Walmsley
@ 2013-06-12 17:48 ` Tony Lindgren
-1 siblings, 0 replies; 22+ messages in thread
From: Tony Lindgren @ 2013-06-12 17:48 UTC (permalink / raw)
To: Paul Walmsley; +Cc: linux-omap, linux-arm-kernel
* Paul Walmsley <paul@pwsan.com> [130610 00:27]:
>
> 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
This one is probably because of broken GPIO numbering in
the board file that uses hardcoded GPIOs for what are probably
twl GPIOs.
Does commenting out omap3_evm_display_init() in the board file
fix the booting for you?
If so, we should probably mark omap3_evm_display_init() with
CONFIG_BROKEN for now rather than add more late init callback
functions for the twl code.
Regards,
Tony
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-12 17:48 ` Tony Lindgren
0 siblings, 0 replies; 22+ messages in thread
From: Tony Lindgren @ 2013-06-12 17:48 UTC (permalink / raw)
To: linux-arm-kernel
* Paul Walmsley <paul@pwsan.com> [130610 00:27]:
>
> 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
This one is probably because of broken GPIO numbering in
the board file that uses hardcoded GPIOs for what are probably
twl GPIOs.
Does commenting out omap3_evm_display_init() in the board file
fix the booting for you?
If so, we should probably mark omap3_evm_display_init() with
CONFIG_BROKEN for now rather than add more late init callback
functions for the twl code.
Regards,
Tony
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-12 17:48 ` Tony Lindgren
@ 2013-06-13 10:55 ` Lokesh Vutla
-1 siblings, 0 replies; 22+ messages in thread
From: Lokesh Vutla @ 2013-06-13 10:55 UTC (permalink / raw)
To: Tony Lindgren; +Cc: Paul Walmsley, linux-omap, linux-arm-kernel
Hi Tony,
On Wednesday 12 June 2013 11:18 PM, Tony Lindgren wrote:
> * Paul Walmsley <paul@pwsan.com> [130610 00:27]:
>>
>> 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
>
> This one is probably because of broken GPIO numbering in
> the board file that uses hardcoded GPIOs for what are probably
> twl GPIOs.
>
> Does commenting out omap3_evm_display_init() in the board file
> fix the booting for you?
Yes by commenting out omap3_evm_display_init() fixes the booting.
>
> If so, we should probably mark omap3_evm_display_init() with
> CONFIG_BROKEN for now rather than add more late init callback
> functions for the twl code.
As per your suggestion I have sent a patch for marking
omap3_evm_display_init()
with CONFIG_BROKEN.
Thanks,
Lokesh
>
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-13 10:55 ` Lokesh Vutla
0 siblings, 0 replies; 22+ messages in thread
From: Lokesh Vutla @ 2013-06-13 10:55 UTC (permalink / raw)
To: linux-arm-kernel
Hi Tony,
On Wednesday 12 June 2013 11:18 PM, Tony Lindgren wrote:
> * Paul Walmsley <paul@pwsan.com> [130610 00:27]:
>>
>> 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
>
> This one is probably because of broken GPIO numbering in
> the board file that uses hardcoded GPIOs for what are probably
> twl GPIOs.
>
> Does commenting out omap3_evm_display_init() in the board file
> fix the booting for you?
Yes by commenting out omap3_evm_display_init() fixes the booting.
>
> If so, we should probably mark omap3_evm_display_init() with
> CONFIG_BROKEN for now rather than add more late init callback
> functions for the twl code.
As per your suggestion I have sent a patch for marking
omap3_evm_display_init()
with CONFIG_BROKEN.
Thanks,
Lokesh
>
> Regards,
>
> Tony
> --
> 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
>
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-13 10:55 ` Lokesh Vutla
@ 2013-06-13 11:08 ` Tony Lindgren
-1 siblings, 0 replies; 22+ messages in thread
From: Tony Lindgren @ 2013-06-13 11:08 UTC (permalink / raw)
To: Lokesh Vutla; +Cc: Paul Walmsley, linux-omap, linux-arm-kernel
* Lokesh Vutla <lokeshvutla@ti.com> [130613 04:01]:
> Hi Tony,
> On Wednesday 12 June 2013 11:18 PM, Tony Lindgren wrote:
> >* Paul Walmsley <paul@pwsan.com> [130610 00:27]:
> >>
> >>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
> >
> >This one is probably because of broken GPIO numbering in
> >the board file that uses hardcoded GPIOs for what are probably
> >twl GPIOs.
> >
> >Does commenting out omap3_evm_display_init() in the board file
> >fix the booting for you?
> Yes by commenting out omap3_evm_display_init() fixes the booting.
> >
> >If so, we should probably mark omap3_evm_display_init() with
> >CONFIG_BROKEN for now rather than add more late init callback
> >functions for the twl code.
> As per your suggestion I have sent a patch for marking
> omap3_evm_display_init()
> with CONFIG_BROKEN.
OK thanks.
Tony
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-13 11:08 ` Tony Lindgren
0 siblings, 0 replies; 22+ messages in thread
From: Tony Lindgren @ 2013-06-13 11:08 UTC (permalink / raw)
To: linux-arm-kernel
* Lokesh Vutla <lokeshvutla@ti.com> [130613 04:01]:
> Hi Tony,
> On Wednesday 12 June 2013 11:18 PM, Tony Lindgren wrote:
> >* Paul Walmsley <paul@pwsan.com> [130610 00:27]:
> >>
> >>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
> >
> >This one is probably because of broken GPIO numbering in
> >the board file that uses hardcoded GPIOs for what are probably
> >twl GPIOs.
> >
> >Does commenting out omap3_evm_display_init() in the board file
> >fix the booting for you?
> Yes by commenting out omap3_evm_display_init() fixes the booting.
> >
> >If so, we should probably mark omap3_evm_display_init() with
> >CONFIG_BROKEN for now rather than add more late init callback
> >functions for the twl code.
> As per your suggestion I have sent a patch for marking
> omap3_evm_display_init()
> with CONFIG_BROKEN.
OK thanks.
Tony
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-11 7:47 ` Peter Ujfalusi
@ 2013-06-14 2:47 ` Paul Walmsley
-1 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-14 2:47 UTC (permalink / raw)
To: Peter Ujfalusi; +Cc: linux-omap, linux-arm-kernel
[-- Attachment #1: Type: TEXT/PLAIN, Size: 368 bytes --]
Hi Péter,
On Tue, 11 Jun 2013, Peter Ujfalusi wrote:
> I will send a patch soon to fix these. Need to test the patch(es) first. I
> think they surfaced because I have enabled the audio support in
> omap2plus_defconfig for OMAP4 and 5 - which require McPDM and DMIC.
> Just couple of minutes, and I'll have the fix.
Thanks for the fast fixes :-)
- Paul
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-14 2:47 ` Paul Walmsley
0 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-14 2:47 UTC (permalink / raw)
To: linux-arm-kernel
Hi P?ter,
On Tue, 11 Jun 2013, Peter Ujfalusi wrote:
> I will send a patch soon to fix these. Need to test the patch(es) first. I
> think they surfaced because I have enabled the audio support in
> omap2plus_defconfig for OMAP4 and 5 - which require McPDM and DMIC.
> Just couple of minutes, and I'll have the fix.
Thanks for the fast fixes :-)
- Paul
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-12 17:48 ` Tony Lindgren
@ 2013-06-14 2:57 ` Paul Walmsley
-1 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-14 2:57 UTC (permalink / raw)
To: Tony Lindgren; +Cc: linux-omap, linux-arm-kernel
On Wed, 12 Jun 2013, Tony Lindgren wrote:
> * Paul Walmsley <paul@pwsan.com> [130610 00:27]:
>
> > * 37xx EVM: boot fails
> > - as of v3.10-rc1
> > - Cause unknown
>
> This one is probably because of broken GPIO numbering in
> the board file that uses hardcoded GPIOs for what are probably
> twl GPIOs.
>
> Does commenting out omap3_evm_display_init() in the board file
> fix the booting for you?
Lokesh's patch fixes it here.
- Paul
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-14 2:57 ` Paul Walmsley
0 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-14 2:57 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, 12 Jun 2013, Tony Lindgren wrote:
> * Paul Walmsley <paul@pwsan.com> [130610 00:27]:
>
> > * 37xx EVM: boot fails
> > - as of v3.10-rc1
> > - Cause unknown
>
> This one is probably because of broken GPIO numbering in
> the board file that uses hardcoded GPIOs for what are probably
> twl GPIOs.
>
> Does commenting out omap3_evm_display_init() in the board file
> fix the booting for you?
Lokesh's patch fixes it here.
- Paul
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-10 7:22 ` Paul Walmsley
@ 2013-06-14 12:38 ` Lokesh Vutla
-1 siblings, 0 replies; 22+ messages in thread
From: Lokesh Vutla @ 2013-06-14 12:38 UTC (permalink / raw)
To: Paul Walmsley; +Cc: linux-omap, linux-arm-kernel
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
> - Cause unknown
I am able to reproduce this issue on 37xx EVM using non-dt boot (dt boot
doesn't throw this error). But this is not started with v3.10-rc, it has
been present on older kernels also( I verified on 3.9 kernel).
This is because that for all instances of uart, serial driver expects a
pad with default
mode which is not the case for uart4 in 37xx EVM.
Correct me if I am wrong.
Thanks and regards,
Lokesh
>
> (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 <paul@pwsan.com>
> To: linux-omap@vger.kernel.org
> Cc: linux-arm-kernel@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@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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-14 12:38 ` Lokesh Vutla
0 siblings, 0 replies; 22+ messages in thread
From: Lokesh Vutla @ 2013-06-14 12:38 UTC (permalink / raw)
To: linux-arm-kernel
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
> - Cause unknown
I am able to reproduce this issue on 37xx EVM using non-dt boot (dt boot
doesn't throw this error). But this is not started with v3.10-rc, it has
been present on older kernels also( I verified on 3.9 kernel).
This is because that for all instances of uart, serial driver expects a
pad with default
mode which is not the case for uart4 in 37xx EVM.
Correct me if I am wrong.
Thanks and regards,
Lokesh
>
> (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 <paul@pwsan.com>
> 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
>
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-10 13:13 ` Lokesh Vutla
@ 2013-06-17 4:38 ` Paul Walmsley
-1 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-17 4:38 UTC (permalink / raw)
To: Lokesh Vutla; +Cc: linux-omap, linux-arm-kernel
On Mon, 10 Jun 2013, Lokesh Vutla wrote:
> On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
>
> > * 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.
It must be a typo, since am335xbone hasn't booted here since v3.7. Thanks
for pointing it out.
- Paul
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-17 4:38 ` Paul Walmsley
0 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-17 4:38 UTC (permalink / raw)
To: linux-arm-kernel
On Mon, 10 Jun 2013, Lokesh Vutla wrote:
> On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
>
> > * 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.
It must be a typo, since am335xbone hasn't booted here since v3.7. Thanks
for pointing it out.
- Paul
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: OMAP v3.10-rc regressions that no one's fixed
2013-06-14 12:38 ` Lokesh Vutla
@ 2013-06-17 4:41 ` Paul Walmsley
-1 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-17 4:41 UTC (permalink / raw)
To: Lokesh Vutla; +Cc: linux-omap, linux-arm-kernel
On Fri, 14 Jun 2013, Lokesh Vutla wrote:
> On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
>
> > * 3730 Beagle XM, am335xbone, CM-T3517: uart4_rx.uart4_rx mux failure
> > - Cause unknown
> I am able to reproduce this issue on 37xx EVM using non-dt boot (dt boot
> doesn't throw this error). But this is not started with v3.10-rc, it has been
> present on older kernels also( I verified on 3.9 kernel).
Digging through my logs here, the message actually goes back to v3.5 at
least. Thanks for pointing this out.
> This is because that for all instances of uart, serial driver expects a
> pad with default mode which is not the case for uart4 in 37xx EVM.
I haven't looked into the issue. Is it something that's easy to fix? If
so please send a patch.
- Paul
^ permalink raw reply [flat|nested] 22+ messages in thread
* OMAP v3.10-rc regressions that no one's fixed
@ 2013-06-17 4:41 ` Paul Walmsley
0 siblings, 0 replies; 22+ messages in thread
From: Paul Walmsley @ 2013-06-17 4:41 UTC (permalink / raw)
To: linux-arm-kernel
On Fri, 14 Jun 2013, Lokesh Vutla wrote:
> On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
>
> > * 3730 Beagle XM, am335xbone, CM-T3517: uart4_rx.uart4_rx mux failure
> > - Cause unknown
> I am able to reproduce this issue on 37xx EVM using non-dt boot (dt boot
> doesn't throw this error). But this is not started with v3.10-rc, it has been
> present on older kernels also( I verified on 3.9 kernel).
Digging through my logs here, the message actually goes back to v3.5 at
least. Thanks for pointing this out.
> This is because that for all instances of uart, serial driver expects a
> pad with default mode which is not the case for uart4 in 37xx EVM.
I haven't looked into the issue. Is it something that's easy to fix? If
so please send a patch.
- Paul
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2013-06-17 4:41 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-10 7:22 OMAP v3.10-rc regressions that no one's fixed Paul Walmsley
2013-06-10 7:22 ` Paul Walmsley
2013-06-10 13:13 ` Lokesh Vutla
2013-06-10 13:13 ` Lokesh Vutla
2013-06-17 4:38 ` Paul Walmsley
2013-06-17 4:38 ` Paul Walmsley
2013-06-11 7:47 ` Peter Ujfalusi
2013-06-11 7:47 ` Peter Ujfalusi
2013-06-14 2:47 ` Paul Walmsley
2013-06-14 2:47 ` Paul Walmsley
2013-06-12 17:48 ` Tony Lindgren
2013-06-12 17:48 ` Tony Lindgren
2013-06-13 10:55 ` Lokesh Vutla
2013-06-13 10:55 ` Lokesh Vutla
2013-06-13 11:08 ` Tony Lindgren
2013-06-13 11:08 ` Tony Lindgren
2013-06-14 2:57 ` Paul Walmsley
2013-06-14 2:57 ` Paul Walmsley
2013-06-14 12:38 ` Lokesh Vutla
2013-06-14 12:38 ` Lokesh Vutla
2013-06-17 4:41 ` Paul Walmsley
2013-06-17 4:41 ` Paul Walmsley
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.