public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: kirill.shutemov@linux.intel.com, mhocko@suse.com,
	torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, amit.kucheria@linaro.org,
	vincent.guittot@linaro.org, guodong.xu@linaro.org
Subject: Kernel crash at boot time or reboot on ARM64/Hikey
Date: Wed, 15 Mar 2017 22:40:29 +0100	[thread overview]
Message-ID: <20170315214029.GA2170@mai> (raw)


Hi Kirill,

I'm facing an issue with my ARM64/Hikey board. The kernel crashes after booting
when running services. With the linaro toolchain, the same happens but when I
reboot the system.

It is hard to see a clear error, as randomly the console shows an infinite
dump, a couple of lines saying "Invalid address".

I have been asking Vincent to test if its board was crashing and it appears the
same happens.

After git bisecting, I found this commit is the offending one.

c2febafc67734a62196c1b9dfba926412d4077ba is the first bad commit
commit c2febafc67734a62196c1b9dfba926412d4077ba
Author: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Date:   Thu Mar 9 17:24:07 2017 +0300

    mm: convert generic code to 5-level paging

    Convert all non-architecture-specific code to 5-level paging.

    It's mostly mechanical adding handling one more page table level in
    places where we deal with pud_t.

    Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

:040000 040000 492678235575b71f88062912e3d2a8f0983a7ab1 1e17bdef1b1ecae4261dd431bc4be67107dfdd5b M      drivers
:040000 040000 13e1ad3cf4523bab0e62efe9afa846c53b2738fc 183b6407eea0f34e5132dc67aaae1d8e3e23e555 M      fs
:040000 040000 1f90d08acc5850318753d5958f615e3b2a484ec7 dcdc7cce85ddbc5b5ef68fcfc77bb2809b4e1115 M      include
:040000 040000 9b3446e04a8d7939962c2df710f6113eea696a50 f6e627b0d378f0a00d2987fdd0c7b215306e6e3c M      lib
:040000 040000 77b15108634671b2286fcefcd3009ea96ba41543 6fc93cb7cb991c2c26b50ce7762ba469e5d4f367 M      mm

Was this issue already spotted ?

Thanks in advance

  -- Daniel

-- 

 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

             reply	other threads:[~2017-03-15 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 21:40 Daniel Lezcano [this message]
     [not found] ` <CA+55aFx=TkLsZKZ5v-EQzhcvd+Cw22ZJsysh4JdnXFw3Bdz9aA@mail.gmail.com>
2017-03-15 21:45   ` Kernel crash at boot time or reboot on ARM64/Hikey Daniel Lezcano
2017-03-16 13:33   ` Daniel Lezcano
2017-03-16 14:25     ` Kirill A. Shutemov
     [not found]     ` <CA+55aFxo266BOXVOJu_x9MJgH2HOMOg12-opqibX+0fPz2vCoA@mail.gmail.com>
2017-03-16 14:47       ` Daniel Lezcano

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=20170315214029.GA2170@mai \
    --to=daniel.lezcano@linaro.org \
    --cc=amit.kucheria@linaro.org \
    --cc=guodong.xu@linaro.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vincent.guittot@linaro.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