From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S942252AbdAJRkl (ORCPT <rfc822;w@1wt.eu>);
        Tue, 10 Jan 2017 12:40:41 -0500
Received: from mailfilter.ece.umd.edu ([129.2.90.4]:48453 "EHLO
        mailfilter.ece.umd.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1764591AbdAJRkc (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 10 Jan 2017 12:40:32 -0500
X-ASG-Debug-ID: 1484070030-04739d10e7959a60001-xx1T2L
X-Barracuda-Envelope-From: sgilles@math.umd.edu
X-Barracuda-Effective-Source-IP: mail-qt0-f198.google.com[209.85.216.198]
X-Barracuda-Apparent-Source-IP: 209.85.216.198
X-ASG-Whitelist: Client
Date: Tue, 10 Jan 2017 12:40:18 -0500
From: "S. Gilles" <sgilles@math.umd.edu>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: Ziyuan <xzy.xu@rock-chips.com>, Shawn Lin <shawn.lin@rock-chips.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
Message-ID: <20170110174018.GF13205@number18.npnth.net>
X-ASG-Orig-Subj: Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy
References: <20170109141955.GB13205@number18.npnth.net>
 <20170109144937.GC13205@number18.npnth.net>
 <f30b97b0-d0e2-b6dd-e11e-ca4ea592b18d@rock-chips.com>
 <20170110010434.GE13205@number18.npnth.net>
 <CGME20170110072114epcas2p3418c5dd1d9e7ec449b027e2543167497@epcas2p3.samsung.com>
 <58748B31.7040307@rock-chips.com>
 <d8e83301-f7c5-ad0a-932c-6ccdd51b8c3f@samsung.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <d8e83301-f7c5-ad0a-932c-6ccdd51b8c3f@samsung.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
X-Barracuda-Connect: mail-qt0-f198.google.com[209.85.216.198]
X-Barracuda-Start-Time: 1484070030
X-Barracuda-URL: https://mailfilter.ece.umd.edu:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size: 1213
X-Barracuda-BRTS-Status: 1
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 2017-01-10T16:23:11+0900, Jaehoon Chung wrote:
> Hi 
> 
> On 01/10/2017 04:20 PM, Ziyuan wrote:
> > Hi,
> > 
> > On 01/10/2017 09:04 AM, S. Gilles wrote:
> >> 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.
> > 
> > Can you share the result ?
> 
> Sorry for late. If it's working fine, I will apply it on fixes.

My apologies - I wasn't sure if the fix was complete, or just in-progress.

It works fine for me: my system boots as normal.

Thanks,
S. Gilles