From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.free-electrons.com ([62.4.15.54]) by bombadil.infradead.org with esmtp (Exim 4.87 #1 (Red Hat Linux)) id 1eQrpj-0000KV-TV for linux-mtd@lists.infradead.org; Mon, 18 Dec 2017 09:35:41 +0000 Date: Mon, 18 Dec 2017 10:35:18 +0100 From: Miquel RAYNAL To: Sean =?UTF-8?B?Tnlla2rDpnI=?= Cc: Boris Brezillon , , , "Kasper Revsbech (KREV)" Subject: Re: [SPAM] Re: [BUG] pxa3xx: wait time out when scanning for bb Message-ID: <20171218103518.4d2f2009@xps13> In-Reply-To: References: <7df7abb5-e666-c999-e449-75762b551ea5@prevas.dk> <20171212123523.48185f21@xps13> <75bd6b87-12ed-4003-262a-b1bd03a62cbd@prevas.dk> <20171212134706.49f3c57e@xps13> <2f16ce90-6e00-c95f-7a81-5603d9acf574@prevas.dk> <20171212143512.3b62d3f5@xps13> <48EEEC1C-954B-42E5-92BE-A00AD97A5789@prevas.dk> <20171212192327.57b1fa80@xps13> <9f578b28-ef3b-8e84-0a8c-b70c494efff0@prevas.dk> <20171213094105.73646658@xps13> <20171215182512.2449af9e@xps13> <45D7D798-BA86-41CD-AB56-156C1BD7FCC4@prevas.dk> <20171215201955.2431195c@xps13> <7892957c-273b-ea58-1d50-b35e70c69e02@prevas.dk> <20171217141916.04e377ab@bbrezillon> <461b45a8-de1f-0b54-567f-001ea30ee927@prevas.dk> <20171217230032.30853780@bbrezillon> <20171217231952.74637510@xps13> <4e25e578-f0a6-89a0-b6f8-98bda37d12de@prevas.dk> <20171218095609.30408c57@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hello Sean, =20 > >> https://gist.github.com/anonymous/08049fbb46bf6df2d24a07aab8783833 =20 > > This is really helpful. It shows the driver is the problem. I don't > > know yet why it reads the NAND status instead of the actual data at > > this moment. I am looking into it. > > > > I added one fixup in my github branch that could possibly help, > > could you give it a try while I am going deeper in my research? > > =20 > Rebased on top of 8cec3f8653e0fe914d831f05cf91ab9face5c1a5 > The "print_req_error: I/O error, dev mtdblock1, sector 0" is gone >=20 > And what you did have apperently fixed the issue with ecc. > The driver is reading the bbt uboot have written :-) >=20 > https://gist.github.com/anonymous/4476819c081896e5e265b3282db52e46 That is good news but can you please also do a dump without -n but with -o, it failed in this configuration until now and if I am not doing any mistake, you did not try this with the last fix? I know the boot should have failed like the previous ones, but it is just to be sure ;) Thanks, we are getting closer. Miqu=C3=A8l