Received: by 2002:ac0:8c8e:0:0:0:0:0 with SMTP id r14csp340749ima; Wed, 6 Feb 2019 00:36:53 -0800 (PST) X-Google-Smtp-Source: AHgI3Ib1Y9KgB0QSU/nLAJPIhKugz1HBZQiA6KbwGQCt6Yj0BMuET1LpQ/owfqXuI11REs4S7wuw X-Received: by 2002:a63:981:: with SMTP id 123mr3869729pgj.444.1549442213226; Wed, 06 Feb 2019 00:36:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549442213; cv=none; d=google.com; s=arc-20160816; b=KsYwkDvtBtb7ul7qdEySDDJxfZmi9MSahKVNOs6+r5DzbMoER03hdVr9PGDr4lRT2O qQhL/mbz3ex6Km6Pn2DB8eONh+HkKdGy0PUiJKwny0liRZQNvdL0zE7j5rMSwq08PGB+ RK8m277Hd7lDhgMQgRwlfUt7RRpeuQIQ+V1XF3BFmL9xGfbKJlSzb0tRP8voYgPCBzqK Ehe/9Lcfz7hTidEUXL3OEmr6X24iM9L0QHaw3dkoiN9jdRDe40EHw8z95lZ75furbd+U xTW2P1l78Uwvdgp9mAulgR/8LEVdwRAnsh8URch6tS2IPTGcNP0yxDdLwhd7pNv8RgY4 2oAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=nCGdkwzma3LK0Mgm4Cy4Vl29WrmaRNcfo080isEA5vI=; b=wyugp8WU+dFaNPvToHsuVf4p2WPKhYlxeRvhGEAQDd+USoCfi0oAWLSsmsyhHQcErT TstJCrOPvg23Cue3xy1ua+71TBrJ0Id+LcuP2TrLF3xSBl0cxzcADNvB20Q1gP55f5ff ACeBPg5eGOXSHyWrOVfUviXnMskG2xUIUQP22AmH/yNpp7lCBYuCfiuTJjQufv7AkU1B UMNfsTMkGuDJSNOsSTLR71nJt/LvsjeuporUoEj4syaZ2aTEYU/4m/Sst576MaH0c/sm Cxex/4lcsBTbh2Wp+TCuE5+bDSqkB4Yq90WV3wlNsVGlxyPwgqMdXxkkpT98yzNy5sMN erCg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t3si5050891pgv.469.2019.02.06.00.36.37; Wed, 06 Feb 2019 00:36:53 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727756AbfBFIfo (ORCPT + 99 others); Wed, 6 Feb 2019 03:35:44 -0500 Received: from bhuna.collabora.co.uk ([46.235.227.227]:43544 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725897AbfBFIfo (ORCPT ); Wed, 6 Feb 2019 03:35:44 -0500 Received: from localhost.localdomain (unknown [IPv6:2a01:e0a:2c:6930:b93f:9fae:b276:a89a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: bbrezillon) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 53BD827D9D7; Wed, 6 Feb 2019 08:35:42 +0000 (GMT) From: Boris Brezillon To: Martin Kepplinger , han.xu@nxp.com, bbrezillon@kernel.org, miquel.raynal@bootlin.com, richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com, marek.vasut@gmail.com, linux-mtd@lists.infradead.org Cc: Your Name , Manfred Schlaegl , Fabio Estevam , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [v2] mtd: rawnand: gpmi: fix MX28 bus master lockup problem Date: Wed, 6 Feb 2019 09:35:33 +0100 Message-Id: <20190206083533.14104-1-boris.brezillon@collabora.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190205155251.18733-1-martin.kepplinger@ginzinger.com> References: MIME-Version: 1.0 X-linux-mtd-patch-notification: thanks X-linux-mtd-patch-commit: 803f4316fb74bf46a268d53bd1d95e7bf20e7350 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Your Name On Tue, 2019-02-05 at 15:52:51 UTC, Martin Kepplinger wrote: > Disable BCH soft reset according to MX23 erratum #2847 ("BCH soft > reset may cause bus master lock up") for MX28 too. It has the same > problem. > > Observed problem: once per 100,000+ MX28 reboots NAND read failed on > DMA timeout errors: > [ 1.770823] UBI: attaching mtd3 to ubi0 > [ 2.768088] gpmi_nand: DMA timeout, last DMA :1 > [ 3.958087] gpmi_nand: BCH timeout, last DMA :1 > [ 4.156033] gpmi_nand: Error in ECC-based read: -110 > [ 4.161136] UBI warning: ubi_io_read: error -110 while reading 64 > bytes from PEB 0:0, read only 0 bytes, retry > [ 4.171283] step 1 error > [ 4.173846] gpmi_nand: Chip: 0, Error -1 > > Without BCH soft reset we successfully executed 1,000,000 MX28 reboots. > > I have a quote from NXP regarding this problem, from July 18th 2016: > > "As the i.MX23 and i.MX28 are of the same generation, they share many > characteristics. Unfortunately, also the erratas may be shared. > In case of the documented erratas and the workarounds, you can also > apply the workaround solution of one device on the other one. This have > been reported, but I’m afraid that there are not an estimated date for > updating the Errata documents. > Please accept our apologies for any inconveniences this may cause." > > Fixes: 6f2a6a52560a ("mtd: nand: gpmi: reset BCH earlier, too, to avoid > NAND startup problems") > Cc: stable@vger.kernel.org > Signed-off-by: Manfred Schlaegl > Signed-off-by: Martin Kepplinger > Reviewed-by: Miquel Raynal > Reviewed-by: Fabio Estevam > Acked-by: Han Xu Applied to http://git.infradead.org/linux-mtd.git mtd/fixes, thanks. y'all come back now!