From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from b.ns.miles-group.at ([95.130.255.144] helo=radon.swed.at) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1VtxF8-0006Gb-7N for linux-mtd@lists.infradead.org; Fri, 20 Dec 2013 10:23:43 +0000 From: Richard Weinberger To: Iwo Mergler , "linux-mtd@lists.infradead.org" Subject: Re: UBI VID header corruption, offset data Date: Fri, 20 Dec 2013 11:23:13 +0100 Message-ID: <3341132.5Nv0YlqARB@sandpuppy> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am Freitag, 20. Dezember 2013, 10:08:04 schrieb Iwo Mergler: > > Let's start simple. Is your MTD driver sane? > > UBI/UBIFS issues are often related to subtle NOR/NAND driver bugs. > > Good point, thanks. The evidence suggests that it may not be. > > So maybe I should extend the question - does anyone recall > seeing arbitrary data offsets during NAND page writes? If the driver is broken millions of things can get wrong. Did you run MTD and UBI tests? These tests often uncover issues within a MTD driver. BTW: Is this a mainline driver? Not that mainline drivers are better by definition, but still. ;-) Thanks, //richard