From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764485AbdAJBEt (ORCPT ); Mon, 9 Jan 2017 20:04:49 -0500 Received: from ecemailfilter.ece.umd.edu ([129.2.90.4]:44443 "EHLO mailfilter.ece.umd.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753418AbdAJBEr (ORCPT ); Mon, 9 Jan 2017 20:04:47 -0500 X-ASG-Debug-ID: 1484010286-04739d10e79161a0001-xx1T2L X-Barracuda-Envelope-From: sgilles@math.umd.edu X-Barracuda-RBL-Trusted-Forwarder: 209.85.216.199 X-ASG-Whitelist: Client Date: Mon, 9 Jan 2017 20:04:34 -0500 X-Barracuda-Effective-Source-IP: c-50-190-1-87.hsd1.md.comcast.net[50.190.1.87] X-Barracuda-Apparent-Source-IP: 50.190.1.87 From: "S. Gilles" To: Shawn Lin Cc: Jaehoon Chung , Ulf Hansson , Joonyoung Shim , linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy Message-ID: <20170110010434.GE13205@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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-Barracuda-Connect: mail-qt0-f199.google.com[209.85.216.199] X-Barracuda-Start-Time: 1484010286 X-Barracuda-URL: https://mailfilter.ece.umd.edu:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 769 X-Barracuda-BRTS-Status: 1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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