linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "S. Gilles" <sgilles@math.umd.edu>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Joonyoung Shim <jy0922.shim@samsung.com>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy
Date: Mon, 9 Jan 2017 20:04:34 -0500	[thread overview]
Message-ID: <20170110010434.GE13205@number18.npnth.net> (raw)
In-Reply-To: <f30b97b0-d0e2-b6dd-e11e-ca4ea592b18d@rock-chips.com>

On 2017-01-10T08:47:16+0800, Shawn Lin wrote:
> Hi
> 
> On 2017/1/9 22:49, S. Gilles wrote:
> > On 2017-01-09T09:19:55-0500, S. Gilles wrote:
> > > Hi,
> > > 
> > > I have a C201, a veyron_speedy device (which uses rk3288) running vanilla
> > > kernels. With recent kernels it will fail to boot (screen is on, with
> > > blinking cursor, but no login prompt and the machine does not respond
> > > over ssh).
> > > 
> > > I've bisected this to df9bcc2bc0a1f8d2963bd916698268fb2470713b, and
> > > reverting that commit on -mainline gives me a bootable kernel. I can
> > > provide more information as needed.
> > 
> 
> The fix is on the way,
> 
> https://patchwork.kernel.org/patch/9498527/

Great - thanks for letting me know.

Thanks,
S. Gilles

  reply	other threads:[~2017-01-10  1:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 14:19 [BUG] Boot failure since df9bcc2bc on veyron_speedy S. Gilles
2017-01-09 14:49 ` S. Gilles
2017-01-10  0:47   ` Shawn Lin
2017-01-10  1:04     ` S. Gilles [this message]
2017-01-10  7:20       ` Ziyuan
2017-01-10  7:23         ` Jaehoon Chung
2017-01-10 17:40           ` S. Gilles

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=20170110010434.GE13205@number18.npnth.net \
    --to=sgilles@math.umd.edu \
    --cc=jh80.chung@samsung.com \
    --cc=jy0922.shim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=ulf.hansson@linaro.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).