From: Lucas Stach <l.stach@pengutronix.de>
To: BOUGH CHEN <haibo.chen@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Angus Ainslie <angus@akkea.ca>
Cc: "Ulf Hansson" <ulf.hansson@linaro.org>,
"Guido Günther" <agx@sigxcpu.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
dl-linux-imx <linux-imx@nxp.com>,
"Sascha Hauer" <kernel@pengutronix.de>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: sdhci timeout on imx8mq
Date: Fri, 18 Dec 2020 21:07:34 +0100 [thread overview]
Message-ID: <4a1fb9fa69d6fdb0ec2d7c390112d412d512ff13.camel@pengutronix.de> (raw)
In-Reply-To: <VI1PR04MB52942233A0BA6BCB692F281E90670@VI1PR04MB5294.eurprd04.prod.outlook.com>
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 <angus@akkea.ca>
> Cc: BOUGH CHEN <haibo.chen@nxp.com>; Ulf Hansson
> <ulf.hansson@linaro.org>; Guido Günther <agx@sigxcpu.org>; linux-mmc
> <linux-mmc@vger.kernel.org>; Adrian Hunter <adrian.hunter@intel.com>;
> dl-linux-imx <linux-imx@nxp.com>; Sascha Hauer
> <kernel@pengutronix.de>;
> moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE
> <linux-arm-kernel@lists.infradead.org>
> Subject: Re: sdhci timeout on imx8mq
>
> Hi Angus,
>
> On Tue, Jun 30, 2020 at 4:39 PM Angus Ainslie <angus@akkea.ca> 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?
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?
Regards,
Lucas
next prev parent reply other threads:[~2020-12-18 20:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 19:19 sdhci timeout on imx8mq Fabio Estevam
2020-02-05 9:26 ` Guido Günther
2020-02-05 13:18 ` Fabio Estevam
2020-02-07 2:11 ` BOUGH CHEN
[not found] ` <VI1PR04MB504091C7991353F6092A8D91901A0@VI1PR04MB5040.eurprd04.prod.outlook.com>
2020-02-13 10:53 ` Fabio Estevam
2020-06-30 19:39 ` Angus Ainslie
2020-07-07 12:44 ` Fabio Estevam
2020-07-08 1:32 ` BOUGH CHEN
2020-12-18 20:07 ` Lucas Stach [this message]
2020-12-18 20:45 ` Angus Ainslie
2020-12-23 21:06 ` Angus Ainslie
2021-01-05 15:06 ` Lucas Stach
2021-01-06 9:29 ` Bough Chen
2021-01-06 15:09 ` Lucas Stach
2021-01-07 1:47 ` Bough Chen
2021-01-06 18:56 ` Fabio Estevam
2021-01-07 1:30 ` Jacky Bai
2021-01-07 11:26 ` Lucas Stach
2021-01-08 1:27 ` Jacky Bai
2021-03-09 7:35 ` Heiko Thiery
2021-01-19 2:35 ` Peng Fan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a1fb9fa69d6fdb0ec2d7c390112d412d512ff13.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=adrian.hunter@intel.com \
--cc=agx@sigxcpu.org \
--cc=angus@akkea.ca \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).