From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] omap3_beagle problem booting kernel on latest u-boot
Date: Thu, 29 Sep 2011 14:39:22 +0530 [thread overview]
Message-ID: <4E8435C2.4020207@ti.com> (raw)
In-Reply-To: <CADDGHU9ic=bVN_hMg4ZkNK_zAkRdSVOaNy5x3dTmB5XnL+rNXg@mail.gmail.com>
John,
My primary suspect would be cache. But the fact that
CONFIG_SYS_DCACHE_OFF is not helping is strange. Could you double-check
this and also make sure that CONFIG_SYS_L2CACHE_OFF is enabled too.
regards,
Aneesh
On Thursday 29 September 2011 11:50 AM, John Rigby wrote:
> Aneesh, Dirk, Jason:
>
> During our monthly release testing of Linaro images we discovered that
> the kernel was pretty unreliable with the latest upstream u-boot.
> After bisecting we found that reverting this patch fixes the problem
>
> commit 45bf05854bc94ed8bae9e9114292895b990327ea
> Author: Aneesh V<aneesh@ti.com>
> Date: Thu Jun 16 23:30:53 2011 +0000
>
> armv7: adapt omap3 to the new cache maintenance framework
>
> adapt omap3 to the new layered cache maintenance framework
>
> Signed-off-by: Aneesh V<aneesh@ti.com>
>
> No idea why because we tried disabling cache by adding
> CONFIG_SYS_DCACHE_OFF to the board config but that did not seem to fix
> the problem. The problem in the kernel was general instability
> usually ending in the rootfs not being mounted. Sometimes random
> kernel crashes have been observed. We have never made it to a shell
> prompt before reverting.
>
> If we figure anything else out we will let you know.
>
> --john
next prev parent reply other threads:[~2011-09-29 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 6:20 [U-Boot] omap3_beagle problem booting kernel on latest u-boot John Rigby
2011-09-29 9:09 ` Aneesh V [this message]
2011-09-29 15:30 ` John Rigby
2011-09-29 18:59 ` Aneesh V
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=4E8435C2.4020207@ti.com \
--to=aneesh@ti.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox