From: "Guido Günther" <agx@sigxcpu.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
NXP Linux Team <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: Wed, 5 Feb 2020 10:26:53 +0100 [thread overview]
Message-ID: <20200205092653.GB2737@bogon.m.sigxcpu.org> (raw)
In-Reply-To: <CAOMZO5DMMCZPfwNbTaG8_iQhWg2K1XeO719nSA0Gsf2ywHy4jQ@mail.gmail.com>
Hi Fabio,
On Mon, Feb 03, 2020 at 04:19:50PM -0300, Fabio Estevam wrote:
> Hi,
>
> I observe the following timeout on a imx8mq-evk running linux-next 20200203:
>
> # [ 11.747858] mmc0: Timeout waiting for hardware interrupt.
> [ 11.753264] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
> [ 11.759705] mmc0: sdhci: Sys addr: 0x00000800 | Version: 0x00000002
> [ 11.766145] mmc0: sdhci: Blk size: 0x00000200 | Blk cnt: 0x00000001
> [ 11.772584] mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000013
> [ 11.779024] mmc0: sdhci: Present: 0x01f88a0a | Host ctl: 0x00000011
> [ 11.785463] mmc0: sdhci: Power: 0x00000002 | Blk gap: 0x00000080
> [ 11.791902] mmc0: sdhci: Wake-up: 0x00000008 | Clock: 0x000020ff
> [ 11.798342] mmc0: sdhci: Timeout: 0x0000008f | Int stat: 0x00000000
> [ 11.804781] mmc0: sdhci: Int enab: 0x117f100b | Sig enab: 0x117f100b
> [ 11.811220] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00008402
> [ 11.817660] mmc0: sdhci: Caps: 0x07eb0000 | Caps_1: 0x8000b407
> [ 11.824100] mmc0: sdhci: Cmd: 0x0000083a | Max curr: 0x00ffffff
> [ 11.830539] mmc0: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0xffffffff
> [ 11.836978] mmc0: sdhci: Resp[2]: 0x320f5913 | Resp[3]: 0x00d04f01
> [ 11.843416] mmc0: sdhci: Host ctl2: 0x00000008
> [ 11.847860] mmc0: sdhci: ADMA Err: 0x00000001 | ADMA Ptr: 0xf97d2200
> [ 11.854297] mmc0: sdhci: ============================================
> [ 11.860908] mmc0: error -110 whilst initialising MMC card
> [ 12.027806] mmc0: new HS400 MMC card at address 0001
> [ 12.033283] mmcblk0: mmc0:0001 R1J56L 13.8 GiB
> [ 12.038007] mmcblk0boot0: mmc0:0001 R1J56L partition 1 4.00 MiB
> [ 12.044112] mmcblk0boot1: mmc0:0001 R1J56L partition 2 4.00 MiB
> [ 12.050172] mmcblk0rpmb: mmc0:0001 R1J56L partition 3 128 KiB,
> chardev (235:0)
> [ 12.058210] mmcblk0: p1 p2
>
> Haven't had a chance to debug this yet, but just reporting in case
> anyone has any ideas.
I've seen the same occasionally on the librem 5 with older linux-next as
well. Do you have a good reproducer?
Cheers,
-- Guido
>
> Thanks
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-05 9:27 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 [this message]
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
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=20200205092653.GB2737@bogon.m.sigxcpu.org \
--to=agx@sigxcpu.org \
--cc=adrian.hunter@intel.com \
--cc=festevam@gmail.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).