Re: OMAP baseline test results for v3.7-rc5
On 16.11.2012 12:56, Igor Mazanov wrote:
> Yegor Yefremov wrote:
>>> Boot tests:
>>>
>>> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot
>>> - May be fixed now, pending retest:
>>> - http://marc.info/?l=linux-omap&m=135082257727502&w=2
>>> - Not yet part of the automated test suite
>>> * May be due to an old U-boot with FDT support problems used here?
>>> Pending local investigation and re-test
>>
>> I'm also trying to boot 3.7-rc5, but my board has console on ttyO3. So I
>> took arch/arm/boot/dts/am335x-evm.dts and replaced uart definition to
>>
>> uart4: serial@481a6000 {
>> status = "okay";
>> };
>>
>> is it sufficient?
>>
>> In u-boot
>> commit 59852d03867108217fe88e3bfc3e1e9cedfe63c5
>> Merge: 22b6fcb b3e5cd1
>> Author: Tom Rini
>> Date: Fri Nov 9 08:47:25 2012 -0700
>>
>> Merge branch 'master' of git://www.denx.de/git/u-boot-microblaze
>>
>> I use following commands and get following output:
>>
>> U-Boot# mmc rescan ; fatload mmc 0 8200 uImage;fatload mmc 0 8000
>> am335x-evm.dtb
>> reading uImage
>> 4222584 bytes read
>> reading am335x-evm.dtb
>> 5172 bytes read
>> U-Boot# fdt addr 8000; fdt resize; bootm 8200 - 8000
>> ## Booting kernel from Legacy Image at 8200 ...
>>Image Name: Linux-3.7.0-rc5-00028-g79e979e
>>Image Type: ARM Linux Kernel Image (uncompressed)
>>Data Size:4222520 Bytes = 4 MiB
>>Load Address: 80008000
>>Entry Point: 80008000
>>Verifying Checksum ... OK
>> ## Flattened Device Tree blob at 8000
>>Booting using the fdt blob at 0x8000
>>Loading Kernel Image ... OK
>> OK
>>reserving fdt memory region: addr=8000 size=2000
>>Loading Device Tree to 8fe64000, end 8fe68fff ... OK
>>
>> Starting kernel ...
>>
>> I force kernel to use default params, so I don't specify them in u-boot. Any
>> idea?
>
> Did you try to set console=ttyO3,115200 in u-boot bootargs settings?
>
Got the stuff working by just invoking make omap2plus_config once again.
Perhaps I changed something viable and didn't notice that. Now waiting for MMC
device tree support ;-)
Thanks.
Yegor
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
Yegor Yefremov wrote:
Boot tests:
* AM335x Beaglebone: omap2plus_defconfig kernels don't boot
- May be fixed now, pending retest:
- http://marc.info/?l=linux-omap&m=135082257727502&w=2
- Not yet part of the automated test suite
* May be due to an old U-boot with FDT support problems used here?
Pending local investigation and re-test
I'm also trying to boot 3.7-rc5, but my board has console on ttyO3. So I took
arch/arm/boot/dts/am335x-evm.dts and replaced uart definition to
uart4: serial@481a6000 {
status = "okay";
};
is it sufficient?
In u-boot
commit 59852d03867108217fe88e3bfc3e1e9cedfe63c5
Merge: 22b6fcb b3e5cd1
Author: Tom Rini
Date: Fri Nov 9 08:47:25 2012 -0700
Merge branch 'master' of git://www.denx.de/git/u-boot-microblaze
I use following commands and get following output:
U-Boot# mmc rescan ; fatload mmc 0 8200 uImage;fatload mmc 0 8000
am335x-evm.dtb
reading uImage
4222584 bytes read
reading am335x-evm.dtb
5172 bytes read
U-Boot# fdt addr 8000; fdt resize; bootm 8200 - 8000
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.7.0-rc5-00028-g79e979e
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4222520 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 8000
Booting using the fdt blob at 0x8000
Loading Kernel Image ... OK
OK
reserving fdt memory region: addr=8000 size=2000
Loading Device Tree to 8fe64000, end 8fe68fff ... OK
Starting kernel ...
I force kernel to use default params, so I don't specify them in u-boot. Any
idea?
Did you try to set console=ttyO3,115200 in u-boot bootargs settings?
Best regards,
Yegor
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
On Fri, Nov 16, 2012 at 11:47 AM, Richard Cochran wrote: > On Tue, Nov 13, 2012 at 08:05:26PM +0400, Igor Mazanov wrote: >> Paul Walmsley wrote: >> > >> >* AM335x Beaglebone: omap2plus_defconfig kernels don't boot >> > - May be fixed now, pending retest: >> >- http://marc.info/?l=linux-omap&m=135082257727502&w=2 >> > - Not yet part of the automated test suite >> > * May be due to an old U-boot with FDT support problems used here? >> >Pending local investigation and re-test >> >> I have the same result with omap2plus_defconfig and kernel 3.7.0-rc5. I >> dumped >> the kernel log buffer via JTAG and can send this log if it could be useful. > > I just got my BeagleBone replaced via RMA, and so I could try a fresh > build of 3.7.0-rc5 with omap2plus_defconfig. It works just fine for me. > > A few details: > > U-Boot SPL 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20) > U-Boot 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20) > > setenv ipaddr 192.168.0.77 > setenv serverip 192.168.0.12 > setenv netmask 255.255.255.0 > setenv bootargs console=ttyO0,115200n8 mem=256M root=/dev/ram rw > initrd=0x8200,16MB ramdisk_size=16384 earlyprintk=serial > tftp 8100 uImage > tftp 8200 beaglebone-initrd.gz > tftp 8000 am335x-bone.dtb > bootm 8100 - 8000 > > So I guess just using a recent u-boot will fix whatever issues you are > seeing. I have a quite new u-boot, exactly U-Boot 2012.10-02160-gc4d22de (Oct 24 2012 - 18:25:04). The problem was in some inconsistency with clock names during changes in the AM33xx clock subsystem, see http://marc.info/?l=linux-omap&m=135299082705058&w=2 For now Beaglebone boots with current git kernel. Regards, Igor. > > Thanks, > Richard > > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
> Boot tests:
>
> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot
> - May be fixed now, pending retest:
> - http://marc.info/?l=linux-omap&m=135082257727502&w=2
> - Not yet part of the automated test suite
> * May be due to an old U-boot with FDT support problems used here?
> Pending local investigation and re-test
I'm also trying to boot 3.7-rc5, but my board has console on ttyO3. So I took
arch/arm/boot/dts/am335x-evm.dts and replaced uart definition to
uart4: serial@481a6000 {
status = "okay";
};
is it sufficient?
In u-boot
commit 59852d03867108217fe88e3bfc3e1e9cedfe63c5
Merge: 22b6fcb b3e5cd1
Author: Tom Rini
Date: Fri Nov 9 08:47:25 2012 -0700
Merge branch 'master' of git://www.denx.de/git/u-boot-microblaze
I use following commands and get following output:
U-Boot# mmc rescan ; fatload mmc 0 8200 uImage;fatload mmc 0 8000
am335x-evm.dtb
reading uImage
4222584 bytes read
reading am335x-evm.dtb
5172 bytes read
U-Boot# fdt addr 8000; fdt resize; bootm 8200 - 8000
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.7.0-rc5-00028-g79e979e
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4222520 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 8000
Booting using the fdt blob at 0x8000
Loading Kernel Image ... OK
OK
reserving fdt memory region: addr=8000 size=2000
Loading Device Tree to 8fe64000, end 8fe68fff ... OK
Starting kernel ...
I force kernel to use default params, so I don't specify them in u-boot. Any
idea?
Best regards,
Yegor
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
On Tue, Nov 13, 2012 at 08:05:26PM +0400, Igor Mazanov wrote: > Paul Walmsley wrote: > > > >* AM335x Beaglebone: omap2plus_defconfig kernels don't boot > > - May be fixed now, pending retest: > >- http://marc.info/?l=linux-omap&m=135082257727502&w=2 > > - Not yet part of the automated test suite > > * May be due to an old U-boot with FDT support problems used here? > >Pending local investigation and re-test > > I have the same result with omap2plus_defconfig and kernel 3.7.0-rc5. I dumped > the kernel log buffer via JTAG and can send this log if it could be useful. I just got my BeagleBone replaced via RMA, and so I could try a fresh build of 3.7.0-rc5 with omap2plus_defconfig. It works just fine for me. A few details: U-Boot SPL 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20) U-Boot 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20) setenv ipaddr 192.168.0.77 setenv serverip 192.168.0.12 setenv netmask 255.255.255.0 setenv bootargs console=ttyO0,115200n8 mem=256M root=/dev/ram rw initrd=0x8200,16MB ramdisk_size=16384 earlyprintk=serial tftp 8100 uImage tftp 8200 beaglebone-initrd.gz tftp 8000 am335x-bone.dtb bootm 8100 - 8000 So I guess just using a recent u-boot will fix whatever issues you are seeing. Thanks, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
* Kevin Hilman [121113 17:09]: > Tony Lindgren writes: > > > > Here's one more booting issue I recently ran into: > > > > - If DEBUG_LL and earlyprintk are enabled, and omap-serial.c > > is compiled as a module, the kernel boot hangs early as the > > clocks for serial port are cut while earlyprintk still uses > > the port. This might be regression from v3.6. > > > > Can you test if the patch below[1] helps? With that, it seems to finish > booting for me (based solely on a ping test.) > > The problem is a race between the late_initcall for omap_device (which > idles devices that have no drivers) and the late_initcall in > kernel/printk.c which turns off the earlyconsole. Any printks > that happen between this omap_device late initcall and the earlyconsole > late initcall will crash when accessing the UART. Yeh that fixes it for me: Tested-by: Tony Lindgren > Kevin > > [1] > > diff --git a/arch/arm/plat-omap/omap_device.c > b/arch/arm/plat-omap/omap_device.c > index 7a7d1f2..138114a 100644 > --- a/arch/arm/plat-omap/omap_device.c > +++ b/arch/arm/plat-omap/omap_device.c > @@ -1275,4 +1275,4 @@ static int __init omap_device_late_init(void) > bus_for_each_dev(&platform_bus_type, NULL, NULL, omap_device_late_idle); > return 0; > } > -late_initcall(omap_device_late_init); > +late_initcall_sync(omap_device_late_init); -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
Tony Lindgren writes: > * Paul Walmsley [121112 11:33]: >> >> Here are some basic OMAP test results for Linux v3.7-rc5. >> Logs and other details at: >> >> http://www.pwsan.com/omap/testlogs/test_v3.7-rc5/2012081034/ >> >> >> Passing tests >> - >> >> Boot to userspace (9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle, >> 3730beaglexm, 37xxevm, 4430es2panda, 5912osk, am335xbone >> >> PM ret/off, suspend + dynamic idle (2/4): 3730beaglexm, 37xxevm >> >> >> Failing tests: fixed by posted patches >> -- >> >> Boot tests: >> >> * 3530ES3 Beagle: I2C timeouts during userspace init >> - Intermittent, appears on 5 out of 6 boots here >> - Aaro Koskinen observes this also on N900 >> - Appears to be caused by commit 3db11feffc1ad2ab9dea27789e6b5b3032827adc >> - http://marc.info/?l=linux-arm-kernel&m=135071372426971&w=2 >> - http://marc.info/?l=linux-omap&m=135197877112220&w=2 >> - Revert posted, pending I2C maintainers: >> - http://marc.info/?l=linux-arm-kernel&m=135221953727077&w=2 > > Here's one more booting issue I recently ran into: > > - If DEBUG_LL and earlyprintk are enabled, and omap-serial.c > is compiled as a module, the kernel boot hangs early as the > clocks for serial port are cut while earlyprintk still uses > the port. This might be regression from v3.6. > Can you test if the patch below[1] helps? With that, it seems to finish booting for me (based solely on a ping test.) The problem is a race between the late_initcall for omap_device (which idles devices that have no drivers) and the late_initcall in kernel/printk.c which turns off the earlyconsole. Any printks that happen between this omap_device late initcall and the earlyconsole late initcall will crash when accessing the UART. Kevin [1] diff --git a/arch/arm/plat-omap/omap_device.c b/arch/arm/plat-omap/omap_device.c index 7a7d1f2..138114a 100644 --- a/arch/arm/plat-omap/omap_device.c +++ b/arch/arm/plat-omap/omap_device.c @@ -1275,4 +1275,4 @@ static int __init omap_device_late_init(void) bus_for_each_dev(&platform_bus_type, NULL, NULL, omap_device_late_idle); return 0; } -late_initcall(omap_device_late_init); +late_initcall_sync(omap_device_late_init); -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc5.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.7-rc5/2012081034/
Passing tests
-
Boot to userspace (9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
3730beaglexm, 37xxevm, 4430es2panda, 5912osk, am335xbone
PM ret/off, suspend + dynamic idle (2/4): 3730beaglexm, 37xxevm
Failing tests: fixed by posted patches
--
Boot tests:
* 3530ES3 Beagle: I2C timeouts during userspace init
- Intermittent, appears on 5 out of 6 boots here
- Aaro Koskinen observes this also on N900
- Appears to be caused by commit 3db11feffc1ad2ab9dea27789e6b5b3032827adc
- http://marc.info/?l=linux-arm-kernel&m=135071372426971&w=2
- http://marc.info/?l=linux-omap&m=135197877112220&w=2
- Revert posted, pending I2C maintainers:
- http://marc.info/?l=linux-arm-kernel&m=135221953727077&w=2
PM tests:
* 3530es3beagle: hangs during off-mode dynamic idle test
- Appears to be caused by commit 6c31b2150ff96755d24e0ab6d6fea08a7bf5c44c:
- http://marc.info/?l=linux-omap&m=135075364705188&w=2
- Fixed by http://www.spinics.net/lists/arm-kernel/msg202116.html
Other:
* 2420N800: powers down 30 seconds after boot
- Presumably due to missing CBUS patches for watchdog control
- http://lkml.org/lkml/2012/9/3/265
* 4430es2panda: omap_hwmod: mcpdm: cannot be enabled for reset (3)
- clock source is from an external I2C-controlled source
- must skip reset until the switchover to hwmod late init
- http://www.spinics.net/lists/arm-kernel/msg178138.html
Failing tests: needing investigation
Boot tests:
* 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
* 3517EVM & CM-T3517: boot hangs with NFS root
- Likely some Kconfig, board file, and PM issues with EMAC
* CM-T3517: boot hangs with MMC boot
- Due to missing MMC setup in board file
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 reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent
Failing tests: needing local investigation (may be due to testbed issues)
-
Boot tests:
* AM335x Beaglebone: omap2plus_defconfig kernels don't boot
- May be fixed now, pending retest:
- http://marc.info/?l=linux-omap&m=135082257727502&w=2
- Not yet part of the automated test suite
* May be due to an old U-boot with FDT support problems used here?
Pending local investigation and re-test
I have the same result with omap2plus_defconfig and kernel 3.7.0-rc5. I dumped
the kernel log buffer via JTAG and can send this log if it could be useful.
* 4460pandaes: boot fails early
- Appears to be due to X-loader problems here
- Need to note the X-loader version so we know it's broken
PM tests:
* 3730 Beagle XM: does not serial wake from off-idle suspend when console
UART doesn't clock gate ("debug ignore_loglevel")
- Not shown in the current test logs; cause unknown
- Pending re-test
vmlinux object size
(delta in bytes from test_v3.7-rc4 (3d70f8c617a436c7146ecb81df2265b4626dfe89)):
text data bsstotal kernel
+500 -80 +492 am33xx_only
+456 +160 +472 n800_multi_omap2xxx
+424 +160 +440 n800_only_a
+16400 +164 omap1_defconfig
+16400 +164 omap1_defconfig_1510innovator_only
+16400 +164 omap1_defconfig_5912osk_only
+940 -80 +932 omap2plus_defconfig
+796 -80 +788 omap2plus_defconfig_2430sdp_only
+940 +240 +964 omap2plus_defconfig_cpupm
+940 -80 +932 omap2plus_defconfig_no_pm
+940 +160 +956 omap2plus_defconfig_omap2_4_only
+820 +160 +836 omap2plus_defconfig_omap3_4_only
+20 +8 +48 +76 rmk_omap3430_ldp_allnoconfig
+12400 +124 rmk_omap3430_ldp_oldconfig
+20 +8 +48 +76 rmk_omap4430_sdp_allnoconfig
+124 +80 +132 rmk_omap4430_sdp_oldconfig
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc5.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.7-rc5/2012081034/
Passing tests
-
Boot to userspace (9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
3730beaglexm, 37xxevm, 4430es2panda, 5912osk, am335xbone
PM ret/off, suspend + dynamic idle (2/4): 3730beaglexm, 37xxevm
Failing tests: fixed by posted patches
--
Boot tests:
* 3530ES3 Beagle: I2C timeouts during userspace init
- Intermittent, appears on 5 out of 6 boots here
- Aaro Koskinen observes this also on N900
- Appears to be caused by commit 3db11feffc1ad2ab9dea27789e6b5b3032827adc
- http://marc.info/?l=linux-arm-kernel&m=135071372426971&w=2
- http://marc.info/?l=linux-omap&m=135197877112220&w=2
- Revert posted, pending I2C maintainers:
- http://marc.info/?l=linux-arm-kernel&m=135221953727077&w=2
PM tests:
* 3530es3beagle: hangs during off-mode dynamic idle test
- Appears to be caused by commit 6c31b2150ff96755d24e0ab6d6fea08a7bf5c44c:
- http://marc.info/?l=linux-omap&m=135075364705188&w=2
- Fixed by http://www.spinics.net/lists/arm-kernel/msg202116.html
Other:
* 2420N800: powers down 30 seconds after boot
- Presumably due to missing CBUS patches for watchdog control
- http://lkml.org/lkml/2012/9/3/265
* 4430es2panda: omap_hwmod: mcpdm: cannot be enabled for reset (3)
- clock source is from an external I2C-controlled source
- must skip reset until the switchover to hwmod late init
- http://www.spinics.net/lists/arm-kernel/msg178138.html
Failing tests: needing investigation
Boot tests:
* 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
* 3517EVM & CM-T3517: boot hangs with NFS root
- Likely some Kconfig, board file, and PM issues with EMAC
* CM-T3517: boot hangs with MMC boot
- Due to missing MMC setup in board file
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 reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent
Failing tests: needing local investigation (may be due to testbed issues)
-
Boot tests:
* AM335x Beaglebone: omap2plus_defconfig kernels don't boot
- May be fixed now, pending retest:
- http://marc.info/?l=linux-omap&m=135082257727502&w=2
- Not yet part of the automated test suite
* May be due to an old U-boot with FDT support problems used here?
Pending local investigation and re-test
I have the same result with omap2plus_defconfig and kernel 3.7.0-rc5. I dumped
the kernel log buffer via JTAG and can send this log if it could be useful.
* 4460pandaes: boot fails early
- Appears to be due to X-loader problems here
- Need to note the X-loader version so we know it's broken
PM tests:
* 3730 Beagle XM: does not serial wake from off-idle suspend when console
UART doesn't clock gate ("debug ignore_loglevel")
- Not shown in the current test logs; cause unknown
- Pending re-test
vmlinux object size
(delta in bytes from test_v3.7-rc4 (3d70f8c617a436c7146ecb81df2265b4626dfe89)):
text data bsstotal kernel
+500 -80 +492 am33xx_only
+456 +160 +472 n800_multi_omap2xxx
+424 +160 +440 n800_only_a
+16400 +164 omap1_defconfig
+16400 +164 omap1_defconfig_1510innovator_only
+16400 +164 omap1_defconfig_5912osk_only
+940 -80 +932 omap2plus_defconfig
+796 -80 +788 omap2plus_defconfig_2430sdp_only
+940 +240 +964 omap2plus_defconfig_cpupm
+940 -80 +932 omap2plus_defconfig_no_pm
+940 +160 +956 omap2plus_defconfig_omap2_4_only
+820 +160 +836 omap2plus_defconfig_omap3_4_only
+20 +8 +48 +76 rmk_omap3430_ldp_allnoconfig
+12400 +124 rmk_omap3430_ldp_oldconfig
+20 +8 +48 +76 rmk_omap4430_sdp_allnoconfig
+124 +80 +132 rmk_omap4430_sdp_oldconfig
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc5.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.7-rc5/2012081034/
Passing tests
-
Boot to userspace (9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
3730beaglexm, 37xxevm, 4430es2panda, 5912osk, am335xbone
PM ret/off, suspend + dynamic idle (2/4): 3730beaglexm, 37xxevm
Failing tests: fixed by posted patches
--
Boot tests:
* 3530ES3 Beagle: I2C timeouts during userspace init
- Intermittent, appears on 5 out of 6 boots here
- Aaro Koskinen observes this also on N900
- Appears to be caused by commit 3db11feffc1ad2ab9dea27789e6b5b3032827adc
- http://marc.info/?l=linux-arm-kernel&m=135071372426971&w=2
- http://marc.info/?l=linux-omap&m=135197877112220&w=2
- Revert posted, pending I2C maintainers:
- http://marc.info/?l=linux-arm-kernel&m=135221953727077&w=2
PM tests:
* 3530es3beagle: hangs during off-mode dynamic idle test
- Appears to be caused by commit 6c31b2150ff96755d24e0ab6d6fea08a7bf5c44c:
- http://marc.info/?l=linux-omap&m=135075364705188&w=2
- Fixed by http://www.spinics.net/lists/arm-kernel/msg202116.html
Other:
* 2420N800: powers down 30 seconds after boot
- Presumably due to missing CBUS patches for watchdog control
- http://lkml.org/lkml/2012/9/3/265
* 4430es2panda: omap_hwmod: mcpdm: cannot be enabled for reset (3)
- clock source is from an external I2C-controlled source
- must skip reset until the switchover to hwmod late init
- http://www.spinics.net/lists/arm-kernel/msg178138.html
Failing tests: needing investigation
Boot tests:
* 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
* 3517EVM & CM-T3517: boot hangs with NFS root
- Likely some Kconfig, board file, and PM issues with EMAC
* CM-T3517: boot hangs with MMC boot
- Due to missing MMC setup in board file
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 reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent
Failing tests: needing local investigation (may be due to testbed issues)
-
Boot tests:
* AM335x Beaglebone: omap2plus_defconfig kernels don't boot
- May be fixed now, pending retest:
- http://marc.info/?l=linux-omap&m=135082257727502&w=2
- Not yet part of the automated test suite
* May be due to an old U-boot with FDT support problems used here?
Pending local investigation and re-test
I have the same result with omap2plus_defconfig and kernel 3.7.0-rc5. I dumped
the kernel log buffer via JTAG and can send this log if it could be useful.
* 4460pandaes: boot fails early
- Appears to be due to X-loader problems here
- Need to note the X-loader version so we know it's broken
PM tests:
* 3730 Beagle XM: does not serial wake from off-idle suspend when console
UART doesn't clock gate ("debug ignore_loglevel")
- Not shown in the current test logs; cause unknown
- Pending re-test
vmlinux object size
(delta in bytes from test_v3.7-rc4 (3d70f8c617a436c7146ecb81df2265b4626dfe89)):
text data bsstotal kernel
+500 -80 +492 am33xx_only
+456 +160 +472 n800_multi_omap2xxx
+424 +160 +440 n800_only_a
+16400 +164 omap1_defconfig
+16400 +164 omap1_defconfig_1510innovator_only
+16400 +164 omap1_defconfig_5912osk_only
+940 -80 +932 omap2plus_defconfig
+796 -80 +788 omap2plus_defconfig_2430sdp_only
+940 +240 +964 omap2plus_defconfig_cpupm
+940 -80 +932 omap2plus_defconfig_no_pm
+940 +160 +956 omap2plus_defconfig_omap2_4_only
+820 +160 +836 omap2plus_defconfig_omap3_4_only
+20 +8 +48 +76 rmk_omap3430_ldp_allnoconfig
+12400 +124 rmk_omap3430_ldp_oldconfig
+20 +8 +48 +76 rmk_omap4430_sdp_allnoconfig
+124 +80 +132 rmk_omap4430_sdp_oldconfig
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc5.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.7-rc5/2012081034/
Passing tests
-
Boot to userspace (9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
3730beaglexm, 37xxevm, 4430es2panda, 5912osk, am335xbone
PM ret/off, suspend + dynamic idle (2/4): 3730beaglexm, 37xxevm
Failing tests: fixed by posted patches
--
Boot tests:
* 3530ES3 Beagle: I2C timeouts during userspace init
- Intermittent, appears on 5 out of 6 boots here
- Aaro Koskinen observes this also on N900
- Appears to be caused by commit 3db11feffc1ad2ab9dea27789e6b5b3032827adc
- http://marc.info/?l=linux-arm-kernel&m=135071372426971&w=2
- http://marc.info/?l=linux-omap&m=135197877112220&w=2
- Revert posted, pending I2C maintainers:
- http://marc.info/?l=linux-arm-kernel&m=135221953727077&w=2
PM tests:
* 3530es3beagle: hangs during off-mode dynamic idle test
- Appears to be caused by commit 6c31b2150ff96755d24e0ab6d6fea08a7bf5c44c:
- http://marc.info/?l=linux-omap&m=135075364705188&w=2
- Fixed by http://www.spinics.net/lists/arm-kernel/msg202116.html
Other:
* 2420N800: powers down 30 seconds after boot
- Presumably due to missing CBUS patches for watchdog control
- http://lkml.org/lkml/2012/9/3/265
* 4430es2panda: omap_hwmod: mcpdm: cannot be enabled for reset (3)
- clock source is from an external I2C-controlled source
- must skip reset until the switchover to hwmod late init
- http://www.spinics.net/lists/arm-kernel/msg178138.html
Failing tests: needing investigation
Boot tests:
* 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
* 3517EVM & CM-T3517: boot hangs with NFS root
- Likely some Kconfig, board file, and PM issues with EMAC
* CM-T3517: boot hangs with MMC boot
- Due to missing MMC setup in board file
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 reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent
Failing tests: needing local investigation (may be due to testbed issues)
-
Boot tests:
* AM335x Beaglebone: omap2plus_defconfig kernels don't boot
- May be fixed now, pending retest:
- http://marc.info/?l=linux-omap&m=135082257727502&w=2
- Not yet part of the automated test suite
* May be due to an old U-boot with FDT support problems used here?
Pending local investigation and re-test
The same result with omap2plus_defconfig and kernel 3.7.0-rc5. I dumped the
kernel log buffer via JTAG and can send this log if it could be useful.
* 4460pandaes: boot fails early
- Appears to be due to X-loader problems here
- Need to note the X-loader version so we know it's broken
PM tests:
* 3730 Beagle XM: does not serial wake from off-idle suspend when console
UART doesn't clock gate ("debug ignore_loglevel")
- Not shown in the current test logs; cause unknown
- Pending re-test
vmlinux object size
(delta in bytes from test_v3.7-rc4 (3d70f8c617a436c7146ecb81df2265b4626dfe89)):
text data bsstotal kernel
+500 -80 +492 am33xx_only
+456 +160 +472 n800_multi_omap2xxx
+424 +160 +440 n800_only_a
+16400 +164 omap1_defconfig
+16400 +164 omap1_defconfig_1510innovator_only
+16400 +164 omap1_defconfig_5912osk_only
+940 -80 +932 omap2plus_defconfig
+796 -80 +788 omap2plus_defconfig_2430sdp_only
+940 +240 +964 omap2plus_defconfig_cpupm
+940 -80 +932 omap2plus_defconfig_no_pm
+940 +160 +956 omap2plus_defconfig_omap2_4_only
+820 +160 +836 omap2plus_defconfig_omap3_4_only
+20 +8 +48 +76 rmk_omap3430_ldp_allnoconfig
+12400 +124 rmk_omap3430_ldp_oldconfig
+20 +8 +48 +76 rmk_omap4430_sdp_allnoconfig
+124 +80 +132 rmk_omap4430_sdp_oldconfig
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP baseline test results for v3.7-rc5
* Paul Walmsley [121112 11:33]:
>
> Here are some basic OMAP test results for Linux v3.7-rc5.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.7-rc5/2012081034/
>
>
> Passing tests
> -
>
> Boot to userspace (9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
> 3730beaglexm, 37xxevm, 4430es2panda, 5912osk, am335xbone
>
> PM ret/off, suspend + dynamic idle (2/4): 3730beaglexm, 37xxevm
>
>
> Failing tests: fixed by posted patches
> --
>
> Boot tests:
>
> * 3530ES3 Beagle: I2C timeouts during userspace init
> - Intermittent, appears on 5 out of 6 boots here
> - Aaro Koskinen observes this also on N900
> - Appears to be caused by commit 3db11feffc1ad2ab9dea27789e6b5b3032827adc
> - http://marc.info/?l=linux-arm-kernel&m=135071372426971&w=2
> - http://marc.info/?l=linux-omap&m=135197877112220&w=2
> - Revert posted, pending I2C maintainers:
> - http://marc.info/?l=linux-arm-kernel&m=135221953727077&w=2
Here's one more booting issue I recently ran into:
- If DEBUG_LL and earlyprintk are enabled, and omap-serial.c
is compiled as a module, the kernel boot hangs early as the
clocks for serial port are cut while earlyprintk still uses
the port. This might be regression from v3.6.
> PM tests:
>
> * 3530es3beagle: hangs during off-mode dynamic idle test
> - Appears to be caused by commit 6c31b2150ff96755d24e0ab6d6fea08a7bf5c44c:
> - http://marc.info/?l=linux-omap&m=135075364705188&w=2
> - Fixed by http://www.spinics.net/lists/arm-kernel/msg202116.html
>
> Other:
>
> * 2420N800: powers down 30 seconds after boot
> - Presumably due to missing CBUS patches for watchdog control
> - http://lkml.org/lkml/2012/9/3/265
>
> * 4430es2panda: omap_hwmod: mcpdm: cannot be enabled for reset (3)
> - clock source is from an external I2C-controlled source
> - must skip reset until the switchover to hwmod late init
> - http://www.spinics.net/lists/arm-kernel/msg178138.html
>
>
> Failing tests: needing investigation
>
>
> Boot tests:
>
> * 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
>
> * 3517EVM & CM-T3517: boot hangs with NFS root
> - Likely some Kconfig, board file, and PM issues with EMAC
>
> * CM-T3517: boot hangs with MMC boot
> - Due to missing MMC setup in board file
>
> 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 reports this does not appear with the same X-loader/bootloader
> on his 4430ES2.3 Panda, so could be ES-level dependent
>
>
> Failing tests: needing local investigation (may be due to testbed issues)
> -
>
> Boot tests:
>
> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot
> - May be fixed now, pending retest:
> - http://marc.info/?l=linux-omap&m=135082257727502&w=2
> - Not yet part of the automated test suite
> * May be due to an old U-boot with FDT support problems used here?
> Pending local investigation and re-test
>
> * 4460pandaes: boot fails early
> - Appears to be due to X-loader problems here
> - Need to note the X-loader version so we know it's broken
>
> PM tests:
>
> * 3730 Beagle XM: does not serial wake from off-idle suspend when console
> UART doesn't clock gate ("debug ignore_loglevel")
> - Not shown in the current test logs; cause unknown
> - Pending re-test
>
>
> vmlinux object size
> (delta in bytes from test_v3.7-rc4
> (3d70f8c617a436c7146ecb81df2265b4626dfe89)):
>text data bsstotal kernel
>+500 -80 +492 am33xx_only
>+456 +160 +472 n800_multi_omap2xxx
>+424 +160 +440 n800_only_a
>+16400 +164 omap1_defconfig
>+16400 +164 omap1_defconfig_1510innovator_only
>+16400 +164 omap1_defconfig_5912osk_only
>+940 -80 +932 omap2plus_defconfig
>+796 -80 +788 omap2plus_defconfig_2430sdp_only
>+940 +240 +964 omap2plus_defconfig_cpupm
>+940 -80 +932 omap2plus_defconfig_no_pm
>+940 +160 +956 omap2plus_defconfig_omap2_4_only
>+820 +160 +836 omap2plus_defconfig_omap3_4_only
> +20 +8 +48 +76 rmk_omap3430_ldp_allnoconfig
>+12400 +124 rmk_omap3430_ldp_oldconfig
> +20 +8 +48 +76 rmk_omap4430_sdp_allnoconfig
>+124 +80 +132 rmk_omap4430_sdp_oldconfig
>
>
> - Paul
>
> --
> To unsubscribe from this list: send the line "unsubscribe linu
OMAP baseline test results for v3.7-rc5
Here are some basic OMAP test results for Linux v3.7-rc5.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.7-rc5/2012081034/
Passing tests
-
Boot to userspace (9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
3730beaglexm, 37xxevm, 4430es2panda, 5912osk, am335xbone
PM ret/off, suspend + dynamic idle (2/4): 3730beaglexm, 37xxevm
Failing tests: fixed by posted patches
--
Boot tests:
* 3530ES3 Beagle: I2C timeouts during userspace init
- Intermittent, appears on 5 out of 6 boots here
- Aaro Koskinen observes this also on N900
- Appears to be caused by commit 3db11feffc1ad2ab9dea27789e6b5b3032827adc
- http://marc.info/?l=linux-arm-kernel&m=135071372426971&w=2
- http://marc.info/?l=linux-omap&m=135197877112220&w=2
- Revert posted, pending I2C maintainers:
- http://marc.info/?l=linux-arm-kernel&m=135221953727077&w=2
PM tests:
* 3530es3beagle: hangs during off-mode dynamic idle test
- Appears to be caused by commit 6c31b2150ff96755d24e0ab6d6fea08a7bf5c44c:
- http://marc.info/?l=linux-omap&m=135075364705188&w=2
- Fixed by http://www.spinics.net/lists/arm-kernel/msg202116.html
Other:
* 2420N800: powers down 30 seconds after boot
- Presumably due to missing CBUS patches for watchdog control
- http://lkml.org/lkml/2012/9/3/265
* 4430es2panda: omap_hwmod: mcpdm: cannot be enabled for reset (3)
- clock source is from an external I2C-controlled source
- must skip reset until the switchover to hwmod late init
- http://www.spinics.net/lists/arm-kernel/msg178138.html
Failing tests: needing investigation
Boot tests:
* 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
* 3517EVM & CM-T3517: boot hangs with NFS root
- Likely some Kconfig, board file, and PM issues with EMAC
* CM-T3517: boot hangs with MMC boot
- Due to missing MMC setup in board file
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 reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent
Failing tests: needing local investigation (may be due to testbed issues)
-
Boot tests:
* AM335x Beaglebone: omap2plus_defconfig kernels don't boot
- May be fixed now, pending retest:
- http://marc.info/?l=linux-omap&m=135082257727502&w=2
- Not yet part of the automated test suite
* May be due to an old U-boot with FDT support problems used here?
Pending local investigation and re-test
* 4460pandaes: boot fails early
- Appears to be due to X-loader problems here
- Need to note the X-loader version so we know it's broken
PM tests:
* 3730 Beagle XM: does not serial wake from off-idle suspend when console
UART doesn't clock gate ("debug ignore_loglevel")
- Not shown in the current test logs; cause unknown
- Pending re-test
vmlinux object size
(delta in bytes from test_v3.7-rc4 (3d70f8c617a436c7146ecb81df2265b4626dfe89)):
text data bsstotal kernel
+500 -80 +492 am33xx_only
+456 +160 +472 n800_multi_omap2xxx
+424 +160 +440 n800_only_a
+16400 +164 omap1_defconfig
+16400 +164 omap1_defconfig_1510innovator_only
+16400 +164 omap1_defconfig_5912osk_only
+940 -80 +932 omap2plus_defconfig
+796 -80 +788 omap2plus_defconfig_2430sdp_only
+940 +240 +964 omap2plus_defconfig_cpupm
+940 -80 +932 omap2plus_defconfig_no_pm
+940 +160 +956 omap2plus_defconfig_omap2_4_only
+820 +160 +836 omap2plus_defconfig_omap3_4_only
+20 +8 +48 +76 rmk_omap3430_ldp_allnoconfig
+12400 +124 rmk_omap3430_ldp_oldconfig
+20 +8 +48 +76 rmk_omap4430_sdp_allnoconfig
+124 +80 +132 rmk_omap4430_sdp_oldconfig
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
