From: Paul Walmsley <paul@pwsan.com>
To: "Bedia, Vaibhav" <vaibhav.bedia@ti.com>
Cc: "Porter, Matt" <mporter@ti.com>,
Richard Cochran <richardcochran@gmail.com>,
"Menon, Nishanth" <nm@ti.com>,
Mark Jackson <mpfj-list@mimc.co.uk>,
"Hiremath, Vaibhav" <hvaibhav@ti.com>,
Peter Korsgaard <jacmet@sunsite.dk>,
"linux-omap\\@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel\\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: OMAP baseline test results for v3.8-rc4
Date: Wed, 6 Feb 2013 22:00:56 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.00.1302062141480.12769@utopia.booyaka.com> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433ECFA0FC@DBDE01.ent.ti.com>
Hi Vaibhav,
On Thu, 24 Jan 2013, Bedia, Vaibhav wrote:
> I could not track down U-Boot that you were using
It's posted now at:
http://www.pwsan.com/omap/bootloaders/beaglebone/u-boot/2011.09-00009-gcf6e04d__20120803171543/
Care to try it?
> However, using your build configs for v3.7 and v3.8-rcX I got the same
> observations i.e. v3.7 boots but others don't.
>
> One difference that I found was that post v3.7 the configs that you are using have
> CONFIG_EARLY_PRINTK set. Once I disabled that I was able to bootup v3.8-rc1/4
> (didn't try rc2/3 but I suspect early_printk was the culprit there too).
>
> I checked with Santosh on this and he mentioned that for DT-only boot, which AM335x is,
> that's expected behavior.
>
> Can you update your AM335x-only config to disable CONFIG_EARLY_PRINTK
Setting CONFIG_EARLY_PRINTK=n doesn't fix the problem I'm seeing.
I also tried building a v3.8-rc6 kernel with the old v3.7-rc config that
was used before; no luck.
> or just skip earlyprintk option in the bootargs for now?
Haven't tried this one yet.
> If you still have issues booting can you update your U-Boot to v2013.01 since things
> seem to be working fine at this point.
Let's try to identify and get rid of bootloader dependencies in the
kernel. They indicate that the kernel isn't initializing something
appropriately, which could cause strange problems later.
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.8-rc4
Date: Wed, 6 Feb 2013 22:00:56 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.00.1302062141480.12769@utopia.booyaka.com> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433ECFA0FC@DBDE01.ent.ti.com>
Hi Vaibhav,
On Thu, 24 Jan 2013, Bedia, Vaibhav wrote:
> I could not track down U-Boot that you were using
It's posted now at:
http://www.pwsan.com/omap/bootloaders/beaglebone/u-boot/2011.09-00009-gcf6e04d__20120803171543/
Care to try it?
> However, using your build configs for v3.7 and v3.8-rcX I got the same
> observations i.e. v3.7 boots but others don't.
>
> One difference that I found was that post v3.7 the configs that you are using have
> CONFIG_EARLY_PRINTK set. Once I disabled that I was able to bootup v3.8-rc1/4
> (didn't try rc2/3 but I suspect early_printk was the culprit there too).
>
> I checked with Santosh on this and he mentioned that for DT-only boot, which AM335x is,
> that's expected behavior.
>
> Can you update your AM335x-only config to disable CONFIG_EARLY_PRINTK
Setting CONFIG_EARLY_PRINTK=n doesn't fix the problem I'm seeing.
I also tried building a v3.8-rc6 kernel with the old v3.7-rc config that
was used before; no luck.
> or just skip earlyprintk option in the bootargs for now?
Haven't tried this one yet.
> If you still have issues booting can you update your U-Boot to v2013.01 since things
> seem to be working fine at this point.
Let's try to identify and get rid of bootloader dependencies in the
kernel. They indicate that the kernel isn't initializing something
appropriately, which could cause strange problems later.
- Paul
next prev parent reply other threads:[~2013-02-06 22:00 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 21:38 OMAP baseline test results for v3.8-rc4 Paul Walmsley
2013-01-20 21:38 ` Paul Walmsley
2013-01-21 16:32 ` Mark Jackson
2013-01-21 16:32 ` Mark Jackson
2013-01-21 16:45 ` Nishanth Menon
2013-01-21 16:45 ` Nishanth Menon
2013-01-21 18:20 ` Richard Cochran
2013-01-21 18:20 ` Richard Cochran
[not found] ` <f36acfaf128c4844b8f696ea4440e253@DLEE74.ent.ti.com>
2013-01-21 18:24 ` Matt Porter
2013-01-21 18:24 ` Matt Porter
2013-01-21 18:34 ` Richard Cochran
2013-01-21 18:34 ` Richard Cochran
2013-01-21 20:36 ` Peter Korsgaard
2013-01-21 20:36 ` Peter Korsgaard
2013-01-22 2:24 ` Paul Walmsley
2013-01-22 2:24 ` Paul Walmsley
2013-01-22 8:55 ` Peter Korsgaard
2013-01-22 8:55 ` Peter Korsgaard
2013-01-22 13:02 ` Bedia, Vaibhav
2013-01-22 13:02 ` Bedia, Vaibhav
2013-01-22 9:24 ` Jan Lübbe
2013-01-22 9:24 ` Jan Lübbe
2013-01-22 9:40 ` Peter Korsgaard
2013-01-22 9:40 ` Peter Korsgaard
2013-01-22 9:52 ` Russell King - ARM Linux
2013-01-22 9:52 ` Russell King - ARM Linux
2013-01-22 12:19 ` Peter Korsgaard
2013-01-22 12:19 ` Peter Korsgaard
2013-01-25 8:23 ` Paul Walmsley
2013-01-25 8:23 ` Paul Walmsley
2013-01-22 10:15 ` Mark Jackson
2013-01-22 10:15 ` Mark Jackson
2013-01-22 12:21 ` Peter Korsgaard
2013-01-22 12:21 ` Peter Korsgaard
2013-01-22 13:45 ` Mark Jackson
2013-01-22 13:45 ` Mark Jackson
2013-01-22 13:32 ` Bedia, Vaibhav
2013-01-22 13:32 ` Bedia, Vaibhav
2013-01-22 13:39 ` Mark Jackson
2013-01-22 13:39 ` Mark Jackson
2013-01-22 18:23 ` Tony Lindgren
2013-01-22 18:23 ` Tony Lindgren
2013-01-23 10:18 ` Mark Jackson
2013-01-23 10:18 ` Mark Jackson
2013-01-23 14:32 ` Bedia, Vaibhav
2013-01-23 14:32 ` Bedia, Vaibhav
2013-01-25 16:59 ` Tony Lindgren
2013-01-25 16:59 ` Tony Lindgren
2013-01-28 12:23 ` Bedia, Vaibhav
2013-01-28 12:23 ` Bedia, Vaibhav
2013-01-24 12:49 ` Bedia, Vaibhav
2013-01-24 12:49 ` Bedia, Vaibhav
2013-01-25 8:42 ` Paul Walmsley
2013-01-25 8:42 ` Paul Walmsley
2013-02-06 22:00 ` Paul Walmsley [this message]
2013-02-06 22:00 ` Paul Walmsley
2013-02-06 22:20 ` Paul Walmsley
2013-02-06 22:20 ` Paul Walmsley
2013-02-07 14:42 ` Bedia, Vaibhav
2013-02-07 14:42 ` Bedia, Vaibhav
[not found] ` <49ca66a84bb245ca9cfe4fd044c4d6f6@DFLE72.ent.ti.com>
2013-01-21 17:10 ` Matt Porter
2013-01-21 17:10 ` Matt Porter
2013-01-21 20:36 ` Peter Korsgaard
2013-01-21 20:36 ` Peter Korsgaard
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=alpine.DEB.2.00.1302062141480.12769@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=hvaibhav@ti.com \
--cc=jacmet@sunsite.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpfj-list@mimc.co.uk \
--cc=mporter@ti.com \
--cc=nm@ti.com \
--cc=richardcochran@gmail.com \
--cc=vaibhav.bedia@ti.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.