From: Stephen Boyd <sboyd@codeaurora.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Regression since v3.11 on ARM shmobile ape6evm board
Date: Thu, 17 Oct 2013 16:24:44 +0000 [thread overview]
Message-ID: <52600F4C.8060202@codeaurora.org> (raw)
In-Reply-To: <20131017091317.GA30729@verge.net.au>
On 10/17/13 02:13, Simon Horman wrote:
> Hi,
>
> I have noticed what appears to be a regression since v3.11
> in Thierry Reding's next-20131017.
>
> The effect, when booting the ape6evm board which is based on the r8a73a4
> using its defconfig is that the boot does not proceed past the bootloader.
>
> I see the following:
>
> ## Booting kernel from Legacy Image at 41000000 ...
> Image Name: Linux-3.12.0-rc1-00012-g65cd4f6
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2208640 Bytes = 2.1 MiB
> Load Address: 40008000
> Entry Point: 40008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> I have not investigated the problem any further.
>
>
>
You're the third report. See
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-October/204665.html
and http://www.spinics.net/lists/arm-kernel/msg279955.html
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression since v3.11 on ARM shmobile ape6evm board
Date: Thu, 17 Oct 2013 09:24:44 -0700 [thread overview]
Message-ID: <52600F4C.8060202@codeaurora.org> (raw)
In-Reply-To: <20131017091317.GA30729@verge.net.au>
On 10/17/13 02:13, Simon Horman wrote:
> Hi,
>
> I have noticed what appears to be a regression since v3.11
> in Thierry Reding's next-20131017.
>
> The effect, when booting the ape6evm board which is based on the r8a73a4
> using its defconfig is that the boot does not proceed past the bootloader.
>
> I see the following:
>
> ## Booting kernel from Legacy Image at 41000000 ...
> Image Name: Linux-3.12.0-rc1-00012-g65cd4f6
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2208640 Bytes = 2.1 MiB
> Load Address: 40008000
> Entry Point: 40008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> I have not investigated the problem any further.
>
>
>
You're the third report. See
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-October/204665.html
and http://www.spinics.net/lists/arm-kernel/msg279955.html
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-10-17 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 9:13 Regression since v3.11 on ARM shmobile ape6evm board Simon Horman
2013-10-17 9:13 ` Simon Horman
2013-10-17 16:24 ` Stephen Boyd [this message]
2013-10-17 16:24 ` Stephen Boyd
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=52600F4C.8060202@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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.