From: Maxime Ripard <maxime@cerno.tech>
To: Sergey Suloev <ssuloev@orpaltech.com>
Cc: wens@csie.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: BananaPi M2 support
Date: Mon, 16 Nov 2020 16:52:53 +0100 [thread overview]
Message-ID: <20201116155253.n3nuvzxup6izhh3m@gilmour.lan> (raw)
In-Reply-To: <9436b07d-7704-6a21-dfdb-b6aa9211d456@orpaltech.com>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
Hi,
On Sat, Nov 14, 2020 at 08:20:54PM +0300, Sergey Suloev wrote:
> Hi,
>
> I noticed that BananaPi M2 (A31 SoC) does not boot anymore on modern
> kernels. The problem arises somewhere between 5.7.19 - 5.8.18. I have saved
> boot logs for both versions https://pastebin.com/DTRZi8R7 and
> https://pastebin.com/PS2hq07A. Logs have been taken on clean/non-patched
> kernel with default config, u-boot v2020.10.
>
> The kernel versions 5.7.x and below work well (I tried 5.5.19 and 5.6.19).
> The versions 5.8.18 and above all fail (5.9 and 5.10).
>
> Could you look at the problem or provide an advice about further
> investigation, please ?
I'm not quite sure what the issue is exactly? How does it fail to boot?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-11-16 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 17:20 BananaPi M2 support Sergey Suloev
2020-11-16 15:52 ` Maxime Ripard [this message]
2020-11-16 17:12 ` Sergey Suloev
2020-11-17 8:06 ` Chen-Yu Tsai
2020-11-17 17:06 ` Sergey Suloev
2020-11-17 17:35 ` Maxime Ripard
2020-11-17 17:36 ` Chen-Yu Tsai
2020-11-18 11:14 ` Sergey Suloev
2020-11-18 11:22 ` Chen-Yu Tsai
2020-11-17 8:03 ` Pavel Machek
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=20201116155253.n3nuvzxup6izhh3m@gilmour.lan \
--to=maxime@cerno.tech \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssuloev@orpaltech.com \
--cc=wens@csie.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).