Here are some basic OMAP test results for Linux v3.19-rc1. Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.19-rc1/20150102151849/
Test summary ------------
Build: uImage: Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only, omap1_defconfig_5912osk_only
Build: uImage+dtb: Pass (13/13): omap2plus_defconfig_am33xx_only/am335x-bone, omap2plus_defconfig/omap4-panda, omap2plus_defconfig/omap4-panda-es, omap2plus_defconfig/omap4-var-som, omap2plus_defconfig/omap3-evm-37xx, omap2plus_defconfig_n800_only_a/omap2420-n800, omap2plus_defconfig/omap2430-sdp, omap2plus_defconfig/am3517-evm, omap2plus_defconfig/omap3-beagle, omap2plus_defconfig/omap3-beagle-xm, omap2plus_defconfig/omap3-sbc-t3517, omap2plus_defconfig/omap5-uevm, omap2plus_defconfig/omap5-sbc-t54
Build: zImage: Pass (17/17): omap2plus_defconfig, omap2plus_defconfig_am33xx_only, omap2plus_defconfig_n800_only_a, omap2plus_defconfig_n800_multi_omap2xxx, omap2plus_defconfig_2430sdp_only, omap2plus_defconfig_cpupm, omap2plus_defconfig_no_pm, omap2plus_defconfig_omap2_4_only, omap2plus_defconfig_omap3_4_only, omap2plus_defconfig_omap5_only, omap2plus_defconfig_dra7xx_only, omap2plus_defconfig_am43xx_only, rmk_omap3430_ldp_oldconfig, rmk_omap3430_ldp_allnoconfig, rmk_omap4430_sdp_oldconfig, rmk_omap4430_sdp_allnoconfig, multi_v7_defconfig
Boot to userspace: FAIL ( 2/17): 2430sdp, 2420n800 skip ( 2/17): 5912osk, 3517evm Pass (13/17): am335xbonelt, am335xbone, 4430es2panda, 4460pandaes, 4460varsomom, 37xxevm, 3530es3beagle, 3530es31beagle, 3730beaglexm, 3730es12beaglexm, cmt3517, 5430es2uevm, 5430es2sbct54
PM: chip retention via suspend: FAIL ( 6/12): am335xbonelt, 4430es2panda, 4460varsomom, 2430sdp, 5430es2uevm, 5430es2sbct54 Pass ( 6/12): 4460pandaes, 37xxevm, 3530es3beagle, 3530es31beagle, 3730beaglexm, 3730es12beaglexm
PM: chip retention via dynamic idle: FAIL ( 7/12): am335xbonelt, 4430es2panda, 4460pandaes, 4460varsomom, 2430sdp, 5430es2uevm, 5430es2sbct54 Pass ( 5/12): 37xxevm, 3530es3beagle, 3530es31beagle, 3730beaglexm, 3730es12beaglexm
PM: chip off (except CORE, due to errata) via suspend: Pass ( 1/ 1): 3730beaglexm
PM: chip off (except CORE, due to errata) via dynamic idle: Pass ( 1/ 1): 3730beaglexm
PM: chip off via suspend: Pass ( 4/ 4): 37xxevm, 3530es3beagle, 3530es31beagle, 3730es12beaglexm
PM: chip off via dynamic idle: Pass ( 4/ 4): 37xxevm, 3530es3beagle, 3530es31beagle, 3730es12beaglexm
Kernel warnings during boot to userspace: FAIL ( 3/17): 4430es2panda, 4460varsomom, cmt3517 skip ( 2/17): 5912osk, 3517evm Pass (12/17): am335xbonelt, am335xbone, 4460pandaes, 37xxevm, 2430sdp, 3530es3beagle, 3530es31beagle, 3730beaglexm, 3730es12beaglexm, 5430es2uevm, 5430es2sbct54, 2420n800
Kernel warnings during PM test: FAIL ( 7/17): 4430es2panda, 4460varsomom, 37xxevm, 3530es3beagle, 3530es31beagle, 3730beaglexm, 3730es12beaglexm skip ( 6/17): 5912osk, 3517evm, am335xbonelt/am335x-boneblack, am335xbone, cmt3517, 2420n800 Pass ( 4/17): 4460pandaes, 2430sdp, 5430es2uevm, 5430es2sbct54
vmlinux object size (delta in bytes from test_v3.18 (b2776bf7149bddd1f4161f14f79520f17fc1d71d)): text data bss total kernel +100107 +3648 -6248 +97507 omap1_defconfig +101103 +2800 -6248 +97655 omap1_defconfig_1510innovator_only +101099 +2816 -6184 +97731 omap1_defconfig_5912osk_only +883783 +15784 -2432 +897135 multi_v7_defconfig +297698 +9648 -4528 +302818 omap2plus_defconfig +280493 +10720 -1824 +289389 omap2plus_defconfig_2430sdp_only +297806 +10696 -4592 +303910 omap2plus_defconfig_am33xx_only +327814 +11784 -4400 +335198 omap2plus_defconfig_am43xx_only +293602 +9664 -4528 +298738 omap2plus_defconfig_cpupm +324078 +12384 -4400 +332062 omap2plus_defconfig_dra7xx_only +216837 +8480 -4600 +220717 omap2plus_defconfig_n800_multi_omap2xxx +213429 +8432 -4632 +217229 omap2plus_defconfig_n800_only_a +291026 +9864 -4656 +296234 omap2plus_defconfig_no_pm +330978 +11696 -4464 +338210 omap2plus_defconfig_omap2_4_only +315374 +7280 -4528 +318126 omap2plus_defconfig_omap3_4_only +327978 +11464 -4400 +335042 omap2plus_defconfig_omap5_only +31708 -1336 -6644 +23728 rmk_omap3430_ldp_allnoconfig +59907 -2672 -6520 +50715 rmk_omap3430_ldp_oldconfig +35652 +1548 -7308 +29892 rmk_omap4430_sdp_allnoconfig +83106 +1824 -6272 +78658 rmk_omap4430_sdp_oldconfig
Boot-time memory difference (delta in bytes from test_v3.18 (b2776bf7149bddd1f4161f14f79520f17fc1d71d)) avail rsrvd high freed board kconfig -117380k -13692k . -164k 2420n800 omap2plus_defconfig_n800_only_a -160k 160k . . 2430sdp omap2plus_defconfig -32k 32k . 12k 3530es31beagle omap2plus_defconfig -32k 32k . 12k 3530es3beagle omap2plus_defconfig 224k -224k . 12k 3730beaglexm omap2plus_defconfig 224k -224k . 12k 3730es12beaglexmomap2plus_defconfig -32k 32k . 12k 37xxevm omap2plus_defconfig 224k -224k . 12k 4430es2panda omap2plus_defconfig 740k -740k . 12k 4460pandaes omap2plus_defconfig 740k -740k . 12k 4460varsomom omap2plus_defconfig 1760k -1760k . 12k 5430es2sbct54 omap2plus_defconfig 1748k -1748k . 12k 5430es2uevm omap2plus_defconfig -172k 172k . 20k am335xbone omap2plus_defconfig_am33xx_only 144k -144k . 12k am335xbonelt omap2plus_defconfig
The N800 didn't boot because the kernel has once again gotten too big for NOLO's size limits. Looking into it.
Another ~300KB kernel object size increase for omap2plus_defconfig kernels.
The test report system is now searching through the boot & PM transcripts for formal kernel warnings ("WARNING: CPU: \d+ PID: \d+") in the "Kernel warnings" sections, and indicating failure when warnings are found.
The memory reporting line logged during kernel boot has changed again, to split out CMA reserved memory from other reserved memory. It's all lumped back together in these test reports.
Hi,
On Sat, Jan 03, 2015 at 01:51:53PM +0100, Arnd Bergmann wrote:
On Saturday 03 January 2015 07:21:49 Paul Walmsley wrote:
Another ~300KB kernel object size increase for omap2plus_defconfig kernels.
300kb seems like a lot for a single release. Have you looked into where this is coming from?
In 3.19-rc1, all initrd decompressors are by default enabled...
CONFIG_RD_GZIP=y -# CONFIG_RD_BZIP2 is not set -# CONFIG_RD_LZMA is not set -# CONFIG_RD_XZ is not set -# CONFIG_RD_LZO is not set -# CONFIG_RD_LZ4 is not set +CONFIG_RD_BZIP2=y +CONFIG_RD_LZMA=y +CONFIG_RD_XZ=y +CONFIG_RD_LZO=y +CONFIG_RD_LZ4=y
A.
On Saturday 03 January 2015 15:44:38 Aaro Koskinen wrote:
On Sat, Jan 03, 2015 at 01:51:53PM +0100, Arnd Bergmann wrote:
On Saturday 03 January 2015 07:21:49 Paul Walmsley wrote:
Another ~300KB kernel object size increase for omap2plus_defconfig kernels.
300kb seems like a lot for a single release. Have you looked into where this is coming from?
In 3.19-rc1, all initrd decompressors are by default enabled...
CONFIG_RD_GZIP=y -# CONFIG_RD_BZIP2 is not set -# CONFIG_RD_LZMA is not set -# CONFIG_RD_XZ is not set -# CONFIG_RD_LZO is not set -# CONFIG_RD_LZ4 is not set +CONFIG_RD_BZIP2=y +CONFIG_RD_LZMA=y +CONFIG_RD_XZ=y +CONFIG_RD_LZO=y +CONFIG_RD_LZ4=y
Interesting, this seems to be the opposite of the intention of the change that caused it, which tried to let you disable the algorithms without selecting CONFIG_EXPERT. For some reason that is impossible to know now, they already defaulted to 'n' when EXPERT was set, but now they default to 'y'.
Does this indeed cause the entire change in size?
Arnd
Hi,
On Sun, Jan 04, 2015 at 05:46:31PM +0100, Arnd Bergmann wrote:
On Saturday 03 January 2015 15:44:38 Aaro Koskinen wrote:
On Sat, Jan 03, 2015 at 01:51:53PM +0100, Arnd Bergmann wrote:
On Saturday 03 January 2015 07:21:49 Paul Walmsley wrote:
Another ~300KB kernel object size increase for omap2plus_defconfig kernels.
300kb seems like a lot for a single release. Have you looked into where this is coming from?
In 3.19-rc1, all initrd decompressors are by default enabled...
Interesting, this seems to be the opposite of the intention of the change that caused it, which tried to let you disable the algorithms without selecting CONFIG_EXPERT. For some reason that is impossible to know now, they already defaulted to 'n' when EXPERT was set, but now they default to 'y'.
Does this indeed cause the entire change in size?
Actually, no. It seems a bigger contributor is enabling SATA in omap2plus_defconfig. But there still something else... Below is some data based on quick checks.
v3.18 / omap2plus_defconfig:
text data bss dec hex filename 8811980 790500 8423536 18026016 1130e20 vmlinux
v3.19-rc1 / omap2plus_defconfig:
text data bss dec hex filename 9093858 800316 8419072 18313246 117701e vmlinux
v3.19-rc1 / omap2plus_defconfig + revert ec72c666fb34 ("usr/Kconfig: make initrd compression algorithm selection not expert"):
text data bss dec hex filename 9070939 800260 8419072 18290271 117165f vmlinux
v3.19-rc1 / omap2plus_defconfig + revert 661ea91b676b ("ARM: omap2plus_defconfig: Enable AHCI_PLATFORM driver"):
text data bss dec hex filename 8928148 792700 8414784 18135632 114ba50 vmlinux
v3.19-rc1 / omap2plus_defconfig + revert ec72c666fb34 & 661ea91b676b:
text data bss dec hex filename 8901129 792644 8414784 18108557 114508d vmlinux
A.
On Sat, 3 Jan 2015, Arnd Bergmann wrote:
On Saturday 03 January 2015 07:21:49 Paul Walmsley wrote:
Another ~300KB kernel object size increase for omap2plus_defconfig kernels.
300kb seems like a lot for a single release.
+300KB is high, but not exceptionally so.
The data, since I started keeping track of it, is below. The last numeric column represents the total kernel object size delta in bytes.
Have you looked into where this is coming from?
I have not.
- Paul
http://www.pwsan.com/omap/testlogs/
test_v3.7-rc1/20121017205513/build/size.txt:+128332 -67728 +2144 +62748 omap2plus_defconfig test_v3.8-rc1/20121228031713/build/size.txt:+168843 +25288 +900 +195031 omap2plus_defconfig test_v3.9-rc1/20130312100243/build/size.txt:+195310 +37968 +1364 +234642 omap2plus_defconfig test_v3.10-rc1/20130518212204/build/size.txt: -59854 -98552 +37136 -121270 omap2plus_defconfig test_v3.11-rc1/20130721020309/build/size.txt:+159173 -2456 +1680 +158397 omap2plus_defconfig test_v3.12-rc1/20130922202452/build_z/size.txt:+237402 +47344 +760 +285506 omap2plus_defconfig test_v3.13-rc1/20131208173326/build_z/size.txt:-276029 -5584 +5008 -276605 omap2plus_defconfig test_v3.14-rc1/20140210035354/build_z/size.txt: +94801 -17448 -9016 +68337 omap2plus_defconfig test_v3.15-rc1/20140421113253/build_z/size.txt: +30722 +11392 +4312 +46426 omap2plus_defconfig test_v3.16-rc1/20140629224344/build_z/size.txt:+133191 +20776 +2750728 +2904695 omap2plus_defconfig test_v3.17-rc1/20140821122707/build_z/size.txt: +54469 -34424 +1728 +21773 omap2plus_defconfig test_v3.18-rc1/20141020095901/build_z/size.txt:+677950 +32008 +54408 +764366 omap2plus_defconfig test_v3.19-rc1/20150102151849/build_z/size.txt:+297698 +9648 -4528 +302818 omap2plus_defconfig
On Saturday 03 January 2015 20:28:28 Paul Walmsley wrote:
On Sat, 3 Jan 2015, Arnd Bergmann wrote:
On Saturday 03 January 2015 07:21:49 Paul Walmsley wrote:
Another ~300KB kernel object size increase for omap2plus_defconfig kernels.
300kb seems like a lot for a single release.
+300KB is high, but not exceptionally so.
The data, since I started keeping track of it, is below. The last numeric column represents the total kernel object size delta in bytes.
I see.
http://www.pwsan.com/omap/testlogs/
test_v3.7-rc1/20121017205513/build/size.txt:+128332 -67728 +2144 +62748 omap2plus_defconfig test_v3.8-rc1/20121228031713/build/size.txt:+168843 +25288 +900 +195031 omap2plus_defconfig test_v3.9-rc1/20130312100243/build/size.txt:+195310 +37968 +1364 +234642 omap2plus_defconfig test_v3.10-rc1/20130518212204/build/size.txt: -59854 -98552 +37136 -121270 omap2plus_defconfig test_v3.11-rc1/20130721020309/build/size.txt:+159173 -2456 +1680 +158397 omap2plus_defconfig test_v3.12-rc1/20130922202452/build_z/size.txt:+237402 +47344 +760 +285506 omap2plus_defconfig test_v3.13-rc1/20131208173326/build_z/size.txt:-276029 -5584 +5008 -276605 omap2plus_defconfig test_v3.14-rc1/20140210035354/build_z/size.txt: +94801 -17448 -9016 +68337 omap2plus_defconfig test_v3.15-rc1/20140421113253/build_z/size.txt: +30722 +11392 +4312 +46426 omap2plus_defconfig test_v3.16-rc1/20140629224344/build_z/size.txt:+133191 +20776 +2750728 +2904695 omap2plus_defconfig test_v3.17-rc1/20140821122707/build_z/size.txt: +54469 -34424 +1728 +21773 omap2plus_defconfig test_v3.18-rc1/20141020095901/build_z/size.txt:+677950 +32008 +54408 +764366 omap2plus_defconfig test_v3.19-rc1/20150102151849/build_z/size.txt:+297698 +9648 -4528 +302818 omap2plus_defconfig
So 3.16 was by far the largest increase, almost 10x bigger than the 3.19 increase, but others are quite big as well.
Do you know what happened in 3.16?
Arnd
On Sun, 4 Jan 2015, Arnd Bergmann wrote:
So 3.16 was by far the largest increase, almost 10x bigger than the 3.19 increase, but others are quite big as well.
Do you know what happened in 3.16?
It was commit 1413c03893332366e5b4d1e26f942ada25f3e82a ("lockdep: Increase static allocations").
- Paul
commit 1413c03893332366e5b4d1e26f942ada25f3e82a Author: Sasha Levin sasha.levin@oracle.com Date: Wed Jan 8 14:21:46 2014 -0500
lockdep: Increase static allocations
Fuzzing a recent kernel with a large configuration hits the static allocation limits and disables lockdep.
This patch doubles the limits.
Signed-off-by: Sasha Levin sasha.levin@oracle.com Signed-off-by: Peter Zijlstra peterz@infradead.org Link: http://lkml.kernel.org/r/1389208906-24338-1-git-send-email-sasha.levin@oracl... Cc: linux-kernel@vger.kernel.org Signed-off-by: Ingo Molnar mingo@kernel.org
kernel-build-reports@lists.linaro.org
-
Aaro Koskinen -
Arnd Bergmann -
Paul Walmsley