linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: kernel.org - master not booting on keystone (ARM v7 Cortex A15 SoC) EVMs
Date: Fri, 19 Dec 2014 17:00:14 -0500	[thread overview]
Message-ID: <54949FEE.8070808@ti.com> (raw)
In-Reply-To: <20141219211816.GH10857@pengutronix.de>

On 12/19/2014 04:18 PM, Uwe Kleine-K?nig wrote:
> Hello,
>
> On Fri, Dec 19, 2014 at 03:55:50PM -0500, Murali Karicheri wrote:
>> I have pulled the latest master from
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git and
>> tried booting on keystone k2hk and k2e EVM. The boot hangs with
>> following log. Has anyone seen this? Keystone is an ARM v7 cortex
>> A15 SMP platform. I am assuming master branch is broken for ARM v7
>> and someone is working to address this. v3.18 booted up fine on my
>> EVM.
>>
>> Any idea?
> You forgot to attach the log?! So no, I don't have any idea. Did you
> bisect?
>
> Best regards
> Uwe
>
Just see below if I enable debug earlyprintk

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.18.0-11757-gd790be3 
(a0868495 at ares-ubuntu) (gcc version 4.7.3 20130226 (prerelease) 
(crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) 
#1 SMP PREEMPT Fri Dec 19 15:53:47 EST 2014
[    0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), 
cr=30c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction 
cache
[    0.000000] Machine model: Texas Instruments Keystone 2 Edison EVM
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] Switching to high address space at 0x800000000
[    0.000000] WARNING: unsafe modification of in-place page tables - 
tainting kernel
[    0.000000] cma: Reserved 16 MiB at 0x000000085f000000
[    0.000000] Forcing write-allocate cache policy for SMP
[    0.000000] Memory policy: Data cache writealloc

I am currently doing a git bisect to find the offending commit.

Murali

-- 
Murali Karicheri
Linux Kernel, Texas Instruments

  parent reply	other threads:[~2014-12-19 22:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 20:55 kernel.org - master not booting on keystone (ARM v7 Cortex A15 SoC) EVMs Murali Karicheri
2014-12-19 21:17 ` Murali Karicheri
2014-12-19 21:18 ` Uwe Kleine-König
2014-12-19 21:25   ` Tyler Baker
2014-12-19 23:48     ` Murali Karicheri
2014-12-21 10:29       ` Uwe Kleine-König
2014-12-22 15:04         ` Murali Karicheri
2014-12-23 14:22           ` Grygorii.Strashko@linaro.org
2014-12-23 15:39             ` Murali Karicheri
2014-12-23 16:23             ` Murali Karicheri
2014-12-23 17:36             ` Murali Karicheri
2014-12-23 18:05               ` santosh.shilimkar at oracle.com
2014-12-23 18:13                 ` santosh.shilimkar at oracle.com
2014-12-23 18:17                   ` Grygorii.Strashko@linaro.org
2014-12-23 18:43                   ` Grygorii.Strashko@linaro.org
2014-12-23 19:07                     ` santosh.shilimkar at oracle.com
2015-01-02 15:33                       ` Murali Karicheri
2015-01-02 19:25                         ` santosh.shilimkar at oracle.com
2015-01-05 20:01             ` Kees Cook
2014-12-19 22:00   ` Murali Karicheri [this message]
2014-12-19 23:26     ` Nishanth Menon
2014-12-19 23:49       ` Murali Karicheri

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=54949FEE.8070808@ti.com \
    --to=m-karicheri2@ti.com \
    --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 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).