linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Benjamin Marty <info@benjaminmarty.ch>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: Kernel stuck at Starting kernel message on mvebu since Kernel 5.17
Date: Wed, 6 Apr 2022 09:16:03 +0100	[thread overview]
Message-ID: <Yk1MQ2nlqjt5Vl3a@shell.armlinux.org.uk> (raw)
In-Reply-To: <CABSdY3KQrT2WoU9tr7zUd+hvPDAgMawvp8MXotJnkTyKpBqtCg@mail.gmail.com>

Hi,

On Wed, Apr 06, 2022 at 01:19:35AM +0200, Benjamin Marty wrote:
> Hello
> 
> Since Kernel 5.17, more precisely commit
> 251cc826be7dec61e574b291b371362c10dd84ea, the Linux Kernel seems to be
> unable to Boot on the mvebu arm platform. After booting it via U-Boot
> it is stuck at the Message `Starting kernel`. Reverting the mentioned
> commit fixes this, and the Kernel boots again fine.
> 
> Any idea if I can try something else?

First, go back to a kernel tree before the above mentioned commit and
make clean to remove the copied files.

Then, move forward to the kernel you want to test, and apply 9189/1
(see patch system below), and try rebuilding.

Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

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

  reply	other threads:[~2022-04-06  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 23:19 Kernel stuck at Starting kernel message on mvebu since Kernel 5.17 Benjamin Marty
2022-04-06  8:16 ` Russell King (Oracle) [this message]
2022-04-07 19:22   ` Benjamin Marty

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=Yk1MQ2nlqjt5Vl3a@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=info@benjaminmarty.ch \
    --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).