lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170110174018.GF13205@number18.npnth.net>
Date:   Tue, 10 Jan 2017 12:40:18 -0500
From:   "S. Gilles" <sgilles@...h.umd.edu>
To:     Jaehoon Chung <jh80.chung@...sung.com>
Cc:     Ziyuan <xzy.xu@...k-chips.com>,
        Shawn Lin <shawn.lin@...k-chips.com>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        Joonyoung Shim <jy0922.shim@...sung.com>,
        linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ