From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6F61FC4361B for ; Fri, 18 Dec 2020 20:53:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3A20D23B6C for ; Fri, 18 Dec 2020 20:53:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725796AbgLRUw7 (ORCPT ); Fri, 18 Dec 2020 15:52:59 -0500 Received: from node.akkea.ca ([192.155.83.177]:60324 "EHLO node.akkea.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725775AbgLRUw7 (ORCPT ); Fri, 18 Dec 2020 15:52:59 -0500 X-Greylist: delayed 409 seconds by postgrey-1.27 at vger.kernel.org; Fri, 18 Dec 2020 15:52:59 EST Received: from localhost (localhost [127.0.0.1]) by node.akkea.ca (Postfix) with ESMTP id F1E194E6562; Fri, 18 Dec 2020 20:45:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akkea.ca; s=mail; t=1608324330; bh=WejVtnCVkdeP6cDq74BjfNEvVaPnFPD/qvuyqoneZ7I=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=QyqfV//OV8teMzPd1evgPoAx+qln9nmPYh0YvmOFdcaBlyXg4DlHA/84J6sb280rA hV0V29vb6nFu0/zknNaupQCV6BJcREzPFPmgMSMud2mDNedA3rnE/PqSssmz5ezGtC HbJ5jKVUckwTTUAjoUOwh7eFZj/PlggBqwRzBXcg= X-Virus-Scanned: Debian amavisd-new at mail.akkea.ca Received: from node.akkea.ca ([127.0.0.1]) by localhost (mail.akkea.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5lwaYtbGhqB; Fri, 18 Dec 2020 20:45:28 +0000 (UTC) Received: from www.akkea.ca (node.akkea.ca [192.155.83.177]) by node.akkea.ca (Postfix) with ESMTPSA id AFBD74E655D; Fri, 18 Dec 2020 20:45:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akkea.ca; s=mail; t=1608324328; bh=WejVtnCVkdeP6cDq74BjfNEvVaPnFPD/qvuyqoneZ7I=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=w4HhWqrYngUcJFcjAv35NdpV8AhlPoXaIpHKfKj6PG62zrAOF9VCoW1821O0sb6qB KQ3QDQ8IaLmFRoPDHtk3nExoU6bGDHBiqsMW+Cs6+ESgZ7rBy2GzuPvuCPM0/+V2wc ZTGkDhEXFgwy5fK/AHQjDQQ5PpcnQuVgqJtsmcec= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 18 Dec 2020 12:45:28 -0800 From: Angus Ainslie To: Lucas Stach Cc: BOUGH CHEN , Fabio Estevam , Ulf Hansson , =?UTF-8?Q?Guido_G=C3=BCnther?= , linux-mmc , Adrian Hunter , dl-linux-imx , Sascha Hauer , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Subject: Re: sdhci timeout on imx8mq In-Reply-To: <4a1fb9fa69d6fdb0ec2d7c390112d412d512ff13.camel@pengutronix.de> References: <20200205092653.GB2737@bogon.m.sigxcpu.org> <5ad361195f2e191484c8a231be0f5a07@akkea.ca> <4a1fb9fa69d6fdb0ec2d7c390112d412d512ff13.camel@pengutronix.de> Message-ID: X-Sender: angus@akkea.ca User-Agent: Roundcube Webmail/1.3.6 Precedence: bulk List-ID: X-Mailing-List: linux-mmc@vger.kernel.org Hi Lucas, Thanks for the ping, I've been meaning to get back to this. On 2020-12-18 12:07, Lucas Stach wrote: > Hi all, > > Am Mittwoch, dem 08.07.2020 um 01:32 +0000 schrieb BOUGH CHEN: >> -----Original Message----- >> From: Fabio Estevam [mailto:festevam@gmail.com] >> Sent: 2020年7月7日 20:45 >> To: Angus Ainslie >> Cc: BOUGH CHEN ; Ulf Hansson >> ; Guido Günther ; linux-mmc >> ; Adrian Hunter ; >> dl-linux-imx ; Sascha Hauer >> ; >> moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE >> >> Subject: Re: sdhci timeout on imx8mq >> >> Hi Angus, >> >> On Tue, Jun 30, 2020 at 4:39 PM Angus Ainslie wrote: >> >> > Has there been any progress with this. I'm getting this on about >> > 50% >> > of >> >> Not from my side, sorry. >> >> Bough, >> >> Do you know why this problem affects the imx8mq-evk versions that are >> populated with the Micron eMMC and not the ones with Sandisk eMMC? > > Hi Angus, > > Can you show me the full fail log? I do not meet this issue on my side, > besides, which kind of uboot do you use? I have not seen this on any of my devices running 5.9.x but I think there have been reports of this still failing so I'll try and find out whether it's with the 5.9.x kernel or newer. We're using a modified imx u-boot https://source.puri.sm/Librem5/uboot-imx/ > > Has there been any progress on this issue? I'm now hitting this on a > system that just upgraded from 5.4 to 5.10. Has anyone tried bisecting > this issue, yet? We have other issues with 5.10 right now so it hasn't had much testing. Angus > > Regards, > Lucas