From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Nishanth Menon <nm@ti.com>, linux-omap <linux-omap@vger.kernel.org>
Cc: Kevin Hilman <khilman@linaro.org>
Subject: Re: linux-next regressions (next-20140423 A15: uevm/dra7)
Date: Wed, 23 Apr 2014 16:55:19 +0300 [thread overview]
Message-ID: <5357C647.9000307@ti.com> (raw)
In-Reply-To: <5357C481.4090906@ti.com>
On 04/23/2014 04:47 PM, Nishanth Menon wrote:
> Hi,
>
> Will be great if someone else could confirm as well.
>
> next-20140423-multi_lpae_defconfig
> 1: DRA7xx-EVM: Boot FAIL: http://slexy.org/raw/s2HJJ9SKzM
> 2: OMAP5432uEVM: Boot FAIL: http://slexy.org/raw/s2HoDCbtO0
> TOTAL = 2 boards, Booted Boards = 0, No Boot boards = 2
>
> next-20140423-multi_v7_defconfig
> 1: DRA7xx-EVM: Boot FAIL: http://slexy.org/raw/s2070nXdAg
> 2: OMAP5432uEVM: Boot FAIL: http://slexy.org/raw/s20wKQEqGp
> TOTAL = 2 boards, Booted Boards = 0, No Boot boards = 2
>
> next-20140423-omap2plus_defconfig
> 1: DRA7xx-EVM: Boot FAIL: http://slexy.org/raw/s2XrqUmRqz
> 2: OMAP5432uEVM: Boot FAIL: http://slexy.org/raw/s2gQkdoTH4
I suspect you are using ext4 as rootfs?
I just sent a fix for this or similar crash (as in the OMAP5432uEVM log):
http://marc.info/?l=linux-kernel&m=139826085609497&w=2
>
>
> Exactly the same setup (rootfs and bootloader) as of yesterday's built
> image:
> next-20140422-omap2plus_defconfig
> 1: DRA7xx-EVM: Boot PASS: http://slexy.org/raw/s20sRLHVgN
> 2: OMAP5432uEVM: Boot PASS: http://slexy.org/raw/s20ZxlYWaB
> TOTAL = 2 boards, Booted Boards = 2, No Boot boards = 0
>
>
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-04-23 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 13:47 linux-next regressions (next-20140423 A15: uevm/dra7) Nishanth Menon
2014-04-23 13:55 ` Peter Ujfalusi [this message]
2014-04-23 14:23 ` Nishanth Menon
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=5357C647.9000307@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=khilman@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).