From: Shanker Donthineni <shankerd@codeaurora.org>
To: Julien Grall <julien.grall@arm.com>,
Itaru Kitayama <itaru.kitayama@riken.jp>,
Christoffer Dall <christoffer.dall@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu
Subject: Re: [PULL 00/29] KVM/ARM Changes for v4.7
Date: Tue, 17 May 2016 11:16:16 -0500 [thread overview]
Message-ID: <573B43D0.6020602@codeaurora.org> (raw)
In-Reply-To: <0b0fb6cc-e208-d3e1-e6f1-9e99ce6a663c@arm.com>
Hi Itaru,
Look at this commit that might be causing the problem.
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/firmware/efi/arm-runtime.c?id=14c43be60166981f0b1f034ad9c59252c6f99e0d
Review your EFI system table and runtime service region attributes.
On 05/17/2016 03:00 AM, Julien Grall wrote:
> Hello,
>
> On 17/05/2016 00:28, Itaru Kitayama wrote:
>> The new v4.6 upstream kernel gets to the prompt on Mustang (Rev A3).
>
> I would recommend you to bissect Linux and finger one or multiple commits which break booting on your board.
>
> Regards,
>
--
Shanker Donthineni
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-05-17 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 14:58 [PULL 00/29] KVM/ARM Changes for v4.7 Itaru Kitayama
2016-05-15 7:08 ` Christoffer Dall
2016-05-15 9:37 ` Itaru Kitayama
2016-05-15 11:19 ` Christoffer Dall
2016-05-15 11:42 ` Julien Grall
2016-05-15 13:30 ` Itaru Kitayama
2016-05-16 7:19 ` Christoffer Dall
2016-05-16 23:28 ` Itaru Kitayama
2016-05-17 8:00 ` Julien Grall
2016-05-17 16:16 ` Shanker Donthineni [this message]
2016-05-17 16:04 ` Shanker Donthineni
-- strict thread matches above, loose matches on Subject: below --
2016-05-11 13:29 Christoffer Dall
2016-05-11 15:23 ` Paolo Bonzini
2016-05-11 15:37 ` Marc Zyngier
2016-05-11 15:41 ` Paolo Bonzini
2016-05-11 15:42 ` Christoffer Dall
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=573B43D0.6020602@codeaurora.org \
--to=shankerd@codeaurora.org \
--cc=christoffer.dall@linaro.org \
--cc=itaru.kitayama@riken.jp \
--cc=julien.grall@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
/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