From: daniel.thompson@linaro.org (Daniel Thompson)
To: linux-arm-kernel@lists.infradead.org
Subject: Latest mainline (3.16 merge window) does not boot in B2020/STiH416
Date: Fri, 13 Jun 2014 13:59:28 +0100 [thread overview]
Message-ID: <539AF5B0.6060509@linaro.org> (raw)
Hi Folks
Using the lastest Linus T. mainline it is no longer possible to boot a
B2020/STiH416.
The kernel boots OK and issues UART messages, but the system gets stuck
trying to mount the NFS root filesystem.
Configuration is multi_v7_defconfig+CGROUPS+AUTOFS4_FS+IPV6 (although
the deviations from multi_v7_defconfig should make little difference).
An automated bisect identified the first broken version as:
--- cut here ---
commit 948d8ffb4775705c729501f9a433d05163e2f253
Author: Gabriel FERNANDEZ <gabriel.fernandez@st.com>
Date: Fri Apr 11 17:07:00 2014 +0200
ARM: STi: DT: add keyscan for stih416
Add keyscan support for stih416.
It is disabled by default given that it is not enabled on all boards.
Also there are PIOs conflict with already claimed lines.
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Signed-off-by: Giuseppe Condorelli <giuseppe.condorelli@st.com>
Signed-off-by: Gabriel Fernandez <gabriel.fernandez@linaro.org>
Signed-off-by: Maxime Coquelin <maxime.coquelin@st.com>
--- cut here ---
Unfortunately 'git revert 948d8ffb4775705c729501f9a433d05163e2f253' is
insufficient to get things working when merged back to head.
Feel free to ask for any help in resolving the problem.
Daniel.
next reply other threads:[~2014-06-13 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 12:59 Daniel Thompson [this message]
2014-06-13 13:10 ` [STLinux Kernel] Latest mainline (3.16 merge window) does not boot in B2020/STiH416 Peter Griffin
2014-06-13 13:30 ` Daniel Thompson
2014-06-13 14:30 ` Peter Griffin
2014-06-13 13:23 ` Giuseppe CONDORELLI
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=539AF5B0.6060509@linaro.org \
--to=daniel.thompson@linaro.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 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).