Here are some basic OMAP test results for Linux v3.14. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/
Test summary ------------
Build: uImage: Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only, omap1_defconfig_5912osk_only
Build: uImage+dtb: Pass ( 9/ 9): omap2plus_defconfig_am33xx_only/am335x-bone, omap2plus_defconfig/omap4-panda, omap2plus_defconfig/omap4-panda-es, omap2plus_defconfig/am3517-evm, omap2plus_defconfig/omap2430-sdp, omap2plus_defconfig/omap3-beagle, omap2plus_defconfig/omap3-beagle-xm, omap2plus_defconfig/omap3-evm-37xx, omap2plus_defconfig/omap4-var-som
Build: zImage: Pass (14/14): multi_v7_defconfig, omap2plus_defconfig, omap2plus_defconfig_am33xx_only, omap2plus_defconfig_2430sdp_only, omap2plus_defconfig_cpupm, omap2plus_defconfig_no_pm, omap2plus_defconfig_n800_only_a, omap2plus_defconfig_n800_multi_omap2xxx, 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 ( 1/12): 2430sdp skip ( 2/12): 5912osk, cmt3517 Pass ( 9/12): 3517evm, 3530es3beagle, 3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes, am335xbone, am335xbonelt, 4460varsomom
PM: chip retention via suspend: FAIL ( 3/ 7): 2430sdp, 4430es2panda, 4460varsomom Pass ( 4/ 7): 3530es3beagle, 3730beaglexm, 37xxevm, 4460pandaes
PM: chip retention via dynamic idle: FAIL ( 7/ 7): 2430sdp, 3530es3beagle, 3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes, 4460varsomom
PM: chip off except CORE via suspend: FAIL ( 1/ 1): 3730beaglexm
PM: chip off except CORE via dynamic idle: FAIL ( 1/ 1): 3730beaglexm
PM: chip off via suspend: FAIL ( 5/ 5): 3530es3beagle, 37xxevm, 4430es2panda, 4460pandaes, 4460varsomom
PM: chip off via dynamic idle: FAIL ( 5/ 5): 3530es3beagle, 37xxevm, 4430es2panda, 4460pandaes, 4460varsomom
vmlinux object size (delta in bytes from test_v3.14-rc8 (b098d6726bbfb94c06d6e1097466187afddae61f)): text data bss total kernel +1160 +88 +8 +1256 omap1_defconfig +1160 +88 +8 +1256 omap1_defconfig_1510innovator_only +1128 +88 +8 +1224 omap1_defconfig_5912osk_only +520 +136 0 +656 multi_v7_defconfig +720 +64 0 +784 omap2plus_defconfig +592 +96 +32 +720 omap2plus_defconfig_2430sdp_only +676 +56 0 +732 omap2plus_defconfig_am33xx_only +648 +72 0 +720 omap2plus_defconfig_am43xx_only +720 +128 0 +848 omap2plus_defconfig_cpupm +720 +64 0 +784 omap2plus_defconfig_dra7xx_only +416 +88 0 +504 omap2plus_defconfig_n800_multi_omap2xxx +384 +24 0 +408 omap2plus_defconfig_n800_only_a +656 +72 0 +728 omap2plus_defconfig_no_pm +656 +72 0 +728 omap2plus_defconfig_omap2_4_only +720 +64 0 +784 omap2plus_defconfig_omap3_4_only +656 +64 0 +720 omap2plus_defconfig_omap5_only +424 +72 -100 +396 rmk_omap3430_ldp_allnoconfig +480 +88 0 +568 rmk_omap3430_ldp_oldconfig +464 +76 -108 +432 rmk_omap4430_sdp_allnoconfig +480 +56 0 +536 rmk_omap4430_sdp_oldconfig
Boot-time memory difference (delta in bytes from test_v3.14-rc8 (b098d6726bbfb94c06d6e1097466187afddae61f)) avail rsrvd high freed board kconfig (no differences)
* Paul Walmsley paul@pwsan.com [140402 09:07]:
Here are some basic OMAP test results for Linux v3.14. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/Boot to userspace: FAIL ( 1/12): 2430sdp
Is this a new regression with MMC? Looks like your boot log for this ends with "Waiting for root device /dev/mmcblk0p1...".
Regards,
Tony
On Wed, Apr 02, 2014 at 09:21:03AM -0700, Tony Lindgren wrote:
- Paul Walmsley paul@pwsan.com [140402 09:07]:
Here are some basic OMAP test results for Linux v3.14. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/Boot to userspace: FAIL ( 1/12): 2430sdp
Is this a new regression with MMC? Looks like your boot log for this ends with "Waiting for root device /dev/mmcblk0p1...".
Nishanth already posted about this a few days ago, see [1]
[1] http://marc.info/?l=linux-omap&m=139637044425644&w=2
* Felipe Balbi balbi@ti.com [140402 09:27]:
On Wed, Apr 02, 2014 at 09:21:03AM -0700, Tony Lindgren wrote:
- Paul Walmsley paul@pwsan.com [140402 09:07]:
Here are some basic OMAP test results for Linux v3.14. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/Boot to userspace: FAIL ( 1/12): 2430sdp
Is this a new regression with MMC? Looks like your boot log for this ends with "Waiting for root device /dev/mmcblk0p1...".
Nishanth already posted about this a few days ago, see [1]
OK thanks.
Tony
On Wed, 2 Apr 2014, Tony Lindgren wrote:
- Paul Walmsley paul@pwsan.com [140402 09:07]:
Here are some basic OMAP test results for Linux v3.14. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/Boot to userspace: FAIL ( 1/12): 2430sdp
Is this a new regression with MMC? Looks like your boot log for this ends with "Waiting for root device /dev/mmcblk0p1...".
It's new since v3.14-rc1:
http://www.spinics.net/lists/arm-kernel/msg306448.html
http://www.spinics.net/lists/arm-kernel/msg306454.html
http://www.spinics.net/lists/arm-kernel/msg306455.html
- Paul
* Paul Walmsley paul@pwsan.com [140402 09:36]:
On Wed, 2 Apr 2014, Tony Lindgren wrote:
- Paul Walmsley paul@pwsan.com [140402 09:07]:
Here are some basic OMAP test results for Linux v3.14. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/Boot to userspace: FAIL ( 1/12): 2430sdp
Is this a new regression with MMC? Looks like your boot log for this ends with "Waiting for root device /dev/mmcblk0p1...".
It's new since v3.14-rc1:
http://www.spinics.net/lists/arm-kernel/msg306448.html
OK looks like I never noticed that one before. Probably because of NFSroot.
Tony
On Wed, Apr 2, 2014 at 11:35 AM, Tony Lindgren tony@atomide.com wrote:
- Paul Walmsley paul@pwsan.com [140402 09:36]:
On Wed, 2 Apr 2014, Tony Lindgren wrote:
- Paul Walmsley paul@pwsan.com [140402 09:07]:
Here are some basic OMAP test results for Linux v3.14. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/Boot to userspace: FAIL ( 1/12): 2430sdp
Is this a new regression with MMC? Looks like your boot log for this ends with "Waiting for root device /dev/mmcblk0p1...".
It's new since v3.14-rc1:
http://www.spinics.net/lists/arm-kernel/msg306448.html
OK looks like I never noticed that one before. Probably because of NFSroot.
Paul uses MMC filesystem, I use NFS. As Felipe Pointed out as well, I did rootcause MMC filesystem mount issue here: http://marc.info/?l=linux-omap&m=139637044425644&w=2
NFS does work for me on 3.14 tag http://slexy.org/raw/s20plaLoaT (on SDP2430)
Regards, Nishanth Menon
* menon.nishanth@gmail.com menon.nishanth@gmail.com [140402 10:03]:
On Wed, Apr 2, 2014 at 11:35 AM, Tony Lindgren tony@atomide.com wrote:
- Paul Walmsley paul@pwsan.com [140402 09:36]:
On Wed, 2 Apr 2014, Tony Lindgren wrote:
- Paul Walmsley paul@pwsan.com [140402 09:07]:
Here are some basic OMAP test results for Linux v3.14. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/Boot to userspace: FAIL ( 1/12): 2430sdp
Is this a new regression with MMC? Looks like your boot log for this ends with "Waiting for root device /dev/mmcblk0p1...".
It's new since v3.14-rc1:
http://www.spinics.net/lists/arm-kernel/msg306448.html
OK looks like I never noticed that one before. Probably because of NFSroot.
Paul uses MMC filesystem, I use NFS. As Felipe Pointed out as well, I did rootcause MMC filesystem mount issue here: http://marc.info/?l=linux-omap&m=139637044425644&w=2
Balaji, care to take a look at the issue for MMC? It may be already fixed in next with the PBIAS handling?
NFS does work for me on 3.14 tag http://slexy.org/raw/s20plaLoaT (on SDP2430)
Yes that's good.
Tony
On Wed, Apr 02, 2014 at 10:15:13AM -0700, Tony Lindgren wrote:
Paul uses MMC filesystem, I use NFS. As Felipe Pointed out as well, I did rootcause MMC filesystem mount issue here: http://marc.info/?l=linux-omap&m=139637044425644&w=2
Balaji, care to take a look at the issue for MMC? It may be already fixed in next with the PBIAS handling?
it may be related (or not), but i'm experiencing reboot issues with 3.13/.14 on omap4 (panda), and after a bisection i found out that reverting
commit e002264f7e45d7661b237045577052fd0b40f89c Author: Balaji T K <balajitk <at> ti.com> Date: Mon Oct 21 00:25:18 2013 +0530
mmc: omap_hsmmc: Fix pbias_disable for omap4
pbias_disable is set to protect the mmc pbias i/o cells in DT boot by preventing voltage switch. Currently pbias_disable is enabled only for omap3 and not for omap4 due to reg_offset difference of 0x100. Enable pbias_disable for omap4+ too by using res->start which does not include the reg_offset.
Signed-off-by: Balaji T K <balajitk <at> ti.com> Signed-off-by: Chris Ball <cjb <at> laptop.org>
made it go away: can you point me to those pbias handling patches (i guess something about dt-booting handling pbias correctly now)?
Root on mmc in my case.
On Thursday 03 April 2014 07:02 PM, Paolo Pisati wrote:
On Wed, Apr 02, 2014 at 10:15:13AM -0700, Tony Lindgren wrote:
Paul uses MMC filesystem, I use NFS. As Felipe Pointed out as well, I did rootcause MMC filesystem mount issue here: http://marc.info/?l=linux-omap&m=139637044425644&w=2
Balaji, care to take a look at the issue for MMC? It may be already fixed in next with the PBIAS handling?
it may be related (or not), but i'm experiencing reboot issues with 3.13/.14 on omap4 (panda), and after a bisection i found out that reverting
Do you have any logs for it ?
commit e002264f7e45d7661b237045577052fd0b40f89c Author: Balaji T K <balajitk <at> ti.com> Date: Mon Oct 21 00:25:18 2013 +0530
mmc: omap_hsmmc: Fix pbias_disable for omap4 pbias_disable is set to protect the mmc pbias i/o cells in DT boot by preventing voltage switch. Currently pbias_disable is enabled only for omap3 and not for omap4 due to reg_offset difference of 0x100. Enable pbias_disable for omap4+ too by using res->start which does not include the reg_offset. Signed-off-by: Balaji T K <balajitk <at> ti.com> Signed-off-by: Chris Ball <cjb <at> laptop.org>made it go away: can you point me to those pbias handling patches (i guess something about dt-booting handling pbias correctly now)?
It is avaliable in linux-next /mmc-next [1]
[1] http://git.kernel.org/cgit/linux/kernel/git/cjb/mmc.git/log/?id=refs/heads/m...
mmc: omap_hsmmc: remove pbias workaround ARM: OMAP: enable SYSCON and REGULATOR_PBIAS in omap2plus_defconfig ARM: dts: add pbias dt node mmc: omap_hsmmc: adapt hsmmc to use pbias regulator regulator: add pbias regulator support mmc: omap_hsmmc: handle vcc and vcc_aux independently mmc: omap_hsmmc: use devm_regulator API
Thanks and Regards, Balaji T K
kernel-build-reports@lists.linaro.org
-
Balaji T K -
Felipe Balbi -
menon.nishanth＠gmail.com -
Paolo Pisati -
Paul Walmsley -
Tony Lindgren