From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from a.ns.miles-group.at ([95.130.255.143] helo=radon.swed.at) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Zd3YB-0000Mn-4b for linux-mtd@lists.infradead.org; Fri, 18 Sep 2015 21:50:35 +0000 Subject: Re: UBIFS corruptions on NOR-Flash To: Roshni Shah References: <55FC6BCB.1030901@nod.at> <55FC6F56.4050107@nod.at> Cc: "linux-mtd@lists.infradead.org" , han.xu@freescale.com From: Richard Weinberger Message-ID: <55FC8712.5040905@nod.at> Date: Fri, 18 Sep 2015 23:50:10 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am 18.09.2015 um 23:36 schrieb Roshni Shah: > Thanks. I tried 4.1 Kernel ran UBI tests and mounting the UBIFS on > Vybrid TWR. I see a different error, however corruptions & UBI test > failures still persist. > > Flash chip: s25fl128s (same as above). > > # uname -r > 4.1.5 > > Following are the results: [...] > ubi0 warning: ubi_eba_read_leb: CRC error: calculated 0x8f7714b9, must > be 0x31a3fc87 > ubi0 warning: vol_cdev_write: volume 0 on UBI device 0 is corrupted > ubi0 warning: ubi_eba_read_leb: CRC error: calculated 0xd1882123, must So, reading data using UBI does not work as expected. One thing MTD drivers sometimes get wrong is that UBI is using vmalloc'ed buffers and drivers cannot deal with that. Adding Han Xu, maybe he has an idea. Thanks, //richard