Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757594AbdLQVBc (ORCPT ); Sun, 17 Dec 2017 16:01:32 -0500 Received: from mail-pg0-f54.google.com ([74.125.83.54]:38275 "EHLO mail-pg0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757380AbdLQVBa (ORCPT ); Sun, 17 Dec 2017 16:01:30 -0500 X-Google-Smtp-Source: ACJfBos9yIOuQJq52dlQqbxfJ5YVNHRRgbctDuzEJ4i3Dc1PQLA1/p+eBsHeJ/D/LC/6jdLVbjDuXm8YJL8kvswtYx8= MIME-Version: 1.0 In-Reply-To: <20171217190056.GA1107@1wt.eu> References: <20171217120503.GA3323@1wt.eu> <20171217155305.16c5bb4f@bbrezillon> <20171217150043.GA1403@1wt.eu> <20171217162342.GA1833@1wt.eu> <20171217190746.2a61232c@bbrezillon> <20171217190056.GA1107@1wt.eu> From: Ezequiel Garcia Date: Sun, 17 Dec 2017 18:01:29 -0300 Message-ID: Subject: Re: pxa3xx_nand times out in 4.14 with JFFS2 To: Willy Tarreau Cc: Boris Brezillon , "linux-mtd@lists.infradead.org" , Robert Jarzmik , linux-arm-kernel , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id vBHL1bB1017129 Content-Length: 1169 Lines: 26 On 17 December 2017 at 16:00, Willy Tarreau wrote: > On Sun, Dec 17, 2017 at 07:07:46PM +0100, Boris Brezillon wrote: >> > > This would guarantee that devices with factory bad blocks, >> > > (and no BBT), would be OK with this patch. >> > >> > I see. I'm fine with trying provided I have reasonably good assurance >> > that I won't have to go through the kwboot pain again :-/ >> >> There's a easy test you can do without scrubing the NAND: >> 1/ comment the nand-on-flash-bbt property in your DT (this will trigger >> a full scan) >> 2/ from u-boot (before booting the kernel), erase a block that you know >> contains nothing important >> 3/ during the kernel scan, make sure this block is not reported as bad > > OK so I tried and never faced any error. Thus I also attempted to mark > a bad block in u-boot, it appeared in the bad blocks table, then I had > to scrub the whole table to get rid of it. Each time when I booted I > saw the message "Scanning device for bad blocks" but no error ever > happened. So I hope it's OK. > Nice. Thanks a lot Willy. I think this acks Boris' patch. -- Ezequiel García, VanguardiaSur www.vanguardiasur.com.ar