All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP baseline test results for v3.7-rc5
Date: Tue, 13 Nov 2012 17:07:39 -0800	[thread overview]
Message-ID: <87obj1f0v8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20121112225830.GW6801@atomide.com> (Tony Lindgren's message of "Mon, 12 Nov 2012 14:58:31 -0800")

Tony Lindgren <tony@atomide.com> writes:

> * Paul Walmsley <paul@pwsan.com> [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/20121111081034/
>> 
>> 
>> 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);

WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.7-rc5
Date: Tue, 13 Nov 2012 17:07:39 -0800	[thread overview]
Message-ID: <87obj1f0v8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20121112225830.GW6801@atomide.com> (Tony Lindgren's message of "Mon, 12 Nov 2012 14:58:31 -0800")

Tony Lindgren <tony@atomide.com> writes:

> * Paul Walmsley <paul@pwsan.com> [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/20121111081034/
>> 
>> 
>> 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);

  reply	other threads:[~2012-11-14  1:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 19:30 OMAP baseline test results for v3.7-rc5 Paul Walmsley
2012-11-12 19:30 ` Paul Walmsley
2012-11-12 22:58 ` Tony Lindgren
2012-11-12 22:58   ` Tony Lindgren
2012-11-14  1:07   ` Kevin Hilman [this message]
2012-11-14  1:07     ` Kevin Hilman
2012-11-14 23:36     ` Tony Lindgren
2012-11-14 23:36       ` Tony Lindgren
2012-11-13 15:59 ` Igor Mazanov
2012-11-13 16:00 ` Igor Mazanov
2012-11-13 16:04 ` Igor Mazanov
2012-11-13 16:05 ` Igor Mazanov
2012-11-13 16:05   ` Igor Mazanov
2012-11-16  7:47   ` Richard Cochran
2012-11-16  7:47     ` Richard Cochran
2012-11-16 11:35     ` Igor Mazanov
2012-11-16 11:35       ` Igor Mazanov
2012-11-16 10:49 ` Yegor Yefremov
2012-11-16 11:56   ` Igor Mazanov
2012-11-16 12:01     ` Yegor Yefremov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obj1f0v8.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.