From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4D542657.2060903@users.sourceforge.net> Date: Thu, 10 Feb 2011 18:54:31 +0100 From: =?ISO-8859-1?Q?Anders_Grafstr=F6m?= MIME-Version: 1.0 To: Michael Cashwell Subject: Re: Numonyx NOR and chip->mutex bug? References: <16826B66-31FE-41AD-A6EF-E668A45AF1FE@prograde.net> <4D4BDD48.6040600@keymile.com> <541E19B8-D428-4F59-B6BB-A3BD8F455AE4@prograde.net> <0488D3BA-7BA3-4E98-B289-3F3D1DB485D4@prograde.net> <85661EDC-9882-41B1-A926-0A88EF1CEF2E@prograde.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-mtd-bounces@lists.infradead.org, Holger brunck , stefan.bigler@keymile.com, Joakim Tjernlund , linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 2011-02-10 17:43, Michael Cashwell wrote: > On Feb 10, 2011, at 10:59 AM, Michael Cashwell wrote: > Troublesome 65nm parts: > run 1: > NOR Flash: block erase suspended and resumed 29 times. > buffered write fails. Buffered write fails with SR[4] set? Have you configured with CONFIG_MTD_UBI_DEBUG_PARANOID so that UBI does the all 0xff check after erase? I'm wondering if the blocks being written to are in a properly erased state. /Anders