linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Dewar <alex.dewar@gmx.co.uk>
To: Heiko Stuebner <heiko@sntech.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Asus C101P Chromeboot fails to boot with Linux 5.2
Date: Fri, 12 Jul 2019 16:00:21 +0100	[thread overview]
Message-ID: <59042b09-7651-be1d-347f-0dc4aa02a91b@gmx.co.uk> (raw)

Hi all,

Since upgrading to the 5.2 kernel, my Chromebook is failing to boot. The
Asus C101P is based on the RK3399 SoC and uses the rk3399-gru-bob device
tree. It used to boot with the 5.1 kernel and mostly worked, with the
exception of broken suspend and resume.

When I try to boot the screen just gets flooded with messages like this:
http://users.sussex.ac.uk/~ad374/boot_fail.jpg

I'm using Arch Linux ARM's linux-aarch64 package, source here:
https://archlinuxarm.org/packages/aarch64/linux-aarch64/files/PKGBUILD

Best,
Alex

             reply	other threads:[~2019-07-12 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 15:00 Alex Dewar [this message]
2019-07-12 15:44 ` Asus C101P Chromeboot fails to boot with Linux 5.2 Emil Renner Berthing
2019-07-12 16:27   ` Alex Dewar
2019-07-12 22:07     ` Alex Dewar
2019-07-13 11:38       ` [REGRESSION] Xorg segfaults on Asus Chromebook CP101 with Linux v5.2 (was Asus C101P Chromeboot fails to boot with Linux 5.2) Alex Dewar
2019-07-13 14:47         ` Greg Kroah-Hartman
2019-07-13 15:17         ` Heiko Stuebner
2019-07-13 16:43           ` Alex Dewar
2019-07-13 22:58             ` Ezequiel Garcia

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=59042b09-7651-be1d-347f-0dc4aa02a91b@gmx.co.uk \
    --to=alex.dewar@gmx.co.uk \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@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).