All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@csie.org>
To: Sergey Suloev <ssuloev@orpaltech.com>
Cc: Maxime Ripard <maxime@cerno.tech>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: BananaPi M2 support
Date: Tue, 17 Nov 2020 16:06:58 +0800	[thread overview]
Message-ID: <CAGb2v64-Tq1ZsmX6D7T+s2XiooQwJDdwe2oO=1aSDGjU1c9TnA@mail.gmail.com> (raw)
In-Reply-To: <1b4bc573-05ae-7c93-75af-50af12054b86@orpaltech.com>

Hi,

Please try linux-next. There were some regulator fixes that got merged recently.
One of them fixes an infinite recursion when resolving regulator supplies.

ChenYu

On Tue, Nov 17, 2020 at 1:12 AM Sergey Suloev <ssuloev@orpaltech.com> wrote:
>
> Hi, Maxime,
>
> it just hangs on that last lines and nothing happens anymore, see 5.18 log.
>
>
> On 16.11.2020 18:52, Maxime Ripard wrote:
> > 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
>
>
> Thank you,
> Sergey
>

WARNING: multiple messages have this Message-ID (diff)
From: Chen-Yu Tsai <wens@csie.org>
To: Sergey Suloev <ssuloev@orpaltech.com>
Cc: Maxime Ripard <maxime@cerno.tech>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BananaPi M2 support
Date: Tue, 17 Nov 2020 16:06:58 +0800	[thread overview]
Message-ID: <CAGb2v64-Tq1ZsmX6D7T+s2XiooQwJDdwe2oO=1aSDGjU1c9TnA@mail.gmail.com> (raw)
In-Reply-To: <1b4bc573-05ae-7c93-75af-50af12054b86@orpaltech.com>

Hi,

Please try linux-next. There were some regulator fixes that got merged recently.
One of them fixes an infinite recursion when resolving regulator supplies.

ChenYu

On Tue, Nov 17, 2020 at 1:12 AM Sergey Suloev <ssuloev@orpaltech.com> wrote:
>
> Hi, Maxime,
>
> it just hangs on that last lines and nothing happens anymore, see 5.18 log.
>
>
> On 16.11.2020 18:52, Maxime Ripard wrote:
> > 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
>
>
> Thank you,
> Sergey
>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-11-17  8:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14 17:20 BananaPi M2 support Sergey Suloev
2020-11-14 17:20 ` Sergey Suloev
2020-11-16 15:52 ` Maxime Ripard
2020-11-16 15:52   ` Maxime Ripard
2020-11-16 17:12   ` Sergey Suloev
2020-11-16 17:12     ` Sergey Suloev
2020-11-17  8:06     ` Chen-Yu Tsai [this message]
2020-11-17  8:06       ` Chen-Yu Tsai
2020-11-17 17:06       ` Sergey Suloev
2020-11-17 17:06         ` Sergey Suloev
2020-11-17 17:35         ` Maxime Ripard
2020-11-17 17:35           ` Maxime Ripard
2020-11-17 17:36         ` Chen-Yu Tsai
2020-11-17 17:36           ` Chen-Yu Tsai
2020-11-18 11:14           ` Sergey Suloev
2020-11-18 11:14             ` Sergey Suloev
2020-11-18 11:22             ` Chen-Yu Tsai
2020-11-18 11:22               ` Chen-Yu Tsai
2020-11-17  8:03 ` Pavel Machek
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='CAGb2v64-Tq1ZsmX6D7T+s2XiooQwJDdwe2oO=1aSDGjU1c9TnA@mail.gmail.com' \
    --to=wens@csie.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=ssuloev@orpaltech.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.