From: Angus Ainslie <angus@akkea.ca>
To: Lucas Stach <l.stach@pengutronix.de>
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>,
"BOUGH CHEN" <haibo.chen@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
"Sascha Hauer" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: sdhci timeout on imx8mq
Date: Wed, 23 Dec 2020 13:06:08 -0800 [thread overview]
Message-ID: <0c2bdbe7b99f7edd6c39272d8307cd33@akkea.ca> (raw)
In-Reply-To: <4a1fb9fa69d6fdb0ec2d7c390112d412d512ff13.camel@pengutronix.de>
Hi Lucas,
On 2020-12-18 12:07, Lucas Stach wrote:
>
> 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've got the dmesg output and it's 33K. Should I send it to the list or
do you want to see it out of band ?
The 2 relevant sections are
[ 13.281867] mmc0: Timeout waiting for hardware interrupt.
[ 13.287310] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 13.293810] mmc0: sdhci: Sys addr: 0x00000800 | Version: 0x00000002
[ 13.300290] mmc0: sdhci: Blk size: 0x00000200 | Blk cnt: 0x00000001
[ 13.306774] mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000013
[ 13.313258] mmc0: sdhci: Present: 0x01f88a0a | Host ctl: 0x00000011
[ 13.319738] mmc0: sdhci: Power: 0x00000002 | Blk gap: 0x00000080
[ 13.326218] mmc0: sdhci: Wake-up: 0x00000008 | Clock: 0x000020ff
[ 13.332699] mmc0: sdhci: Timeout: 0x0000008f | Int stat: 0x00000000
[ 13.339178] mmc0: sdhci: Int enab: 0x107f100b | Sig enab: 0x107f100b
[ 13.345658] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00008402
[ 13.352141] mmc0: sdhci: Caps: 0x07eb0000 | Caps_1: 0x8000b407
[ 13.358622] mmc0: sdhci: Cmd: 0x0000083a | Max curr: 0x00ffffff
[ 13.365106] mmc0: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0xffffffff
[ 13.371589] mmc0: sdhci: Resp[2]: 0x328f5903 | Resp[3]: 0x00d02700
[ 13.378068] mmc0: sdhci: Host ctl2: 0x00000000
[ 13.382554] mmc0: sdhci: ADMA Err: 0x00000001 | ADMA Ptr: 0xe5b90200
[ 13.389042] mmc0: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS
DUMP =========
[ 13.396661] mmc0: sdhci-esdhc-imx: cmd debug status: 0x2100
[ 13.402361] mmc0: sdhci-esdhc-imx: data debug status: 0x2200
[ 13.408119] mmc0: sdhci-esdhc-imx: trans debug status: 0x2300
[ 13.413991] mmc0: sdhci-esdhc-imx: dma debug status: 0x2402
[ 13.419718] mmc0: sdhci-esdhc-imx: adma debug status: 0x2501
[ 13.425478] mmc0: sdhci-esdhc-imx: fifo debug status: 0x2610
[ 13.431294] mmc0: sdhci-esdhc-imx: async fifo debug status: 0x2751
[ 13.437600] mmc0: sdhci: ============================================
[ 13.453076] mmc0: error -110 whilst initialising MMC card
[ 13.662288] mmc0: new HS400 MMC card at address 0001
[ 13.676191] mmcblk0: mmc0:0001 032G32 29.1 GiB
[ 13.684755] mmcblk0boot0: mmc0:0001 032G32 partition 1 4.00 MiB
[ 13.694405] mmcblk0boot1: mmc0:0001 032G32 partition 2 4.00 MiB
[ 13.702264] mmcblk0rpmb: mmc0:0001 032G32 partition 3 4.00 MiB,
chardev (245:0)
[ 13.715966] mmcblk0: p1 p2
[ 29.665891] mmc1: Timeout waiting for hardware interrupt.
[ 29.671310] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 29.677758] mmc1: sdhci: Sys addr: 0x00000800 | Version: 0x00000002
[ 29.684201] mmc1: sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001
[ 29.690642] mmc1: sdhci: Argument: 0x12008004 | Trn mode: 0x00000013
[ 29.697086] mmc1: sdhci: Present: 0x01f88a0a | Host ctl: 0x00000013
[ 29.703529] mmc1: sdhci: Power: 0x00000002 | Blk gap: 0x00000080
[ 29.709980] mmc1: sdhci: Wake-up: 0x00000008 | Clock: 0x0000003f
[ 29.716426] mmc1: sdhci: Timeout: 0x0000008f | Int stat: 0x00000000
[ 29.722868] mmc1: sdhci: Int enab: 0x107f110b | Sig enab: 0x107f110b
[ 29.729310] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00008402
[ 29.735754] mmc1: sdhci: Caps: 0x07eb0000 | Caps_1: 0x8000b407
[ 29.742212] mmc1: sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff
[ 29.748658] mmc1: sdhci: Resp[0]: 0x00002000 | Resp[1]: 0x00000000
[ 29.755099] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
[ 29.761540] mmc1: sdhci: Host ctl2: 0x00000000
[ 29.765989] mmc1: sdhci: ADMA Err: 0x00000001 | ADMA Ptr: 0xe6605200
[ 29.772439] mmc1: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS
DUMP =========
[ 29.780026] mmc1: sdhci-esdhc-imx: cmd debug status: 0x2100
[ 29.785692] mmc1: sdhci-esdhc-imx: data debug status: 0x2200
[ 29.791448] mmc1: sdhci-esdhc-imx: trans debug status: 0x2300
[ 29.797284] mmc1: sdhci-esdhc-imx: dma debug status: 0x2402
[ 29.802943] mmc1: sdhci-esdhc-imx: adma debug status: 0x2501
[ 29.808690] mmc1: sdhci-esdhc-imx: fifo debug status: 0x2690
[ 29.814437] mmc1: sdhci-esdhc-imx: async fifo debug status: 0x2751
[ 29.820701] mmc1: sdhci: ============================================
Thanks
Angus
_______________________________________________
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-12-23 21: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
2020-12-18 20:45 ` Angus Ainslie
2020-12-23 21:06 ` Angus Ainslie [this message]
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=0c2bdbe7b99f7edd6c39272d8307cd33@akkea.ca \
--to=angus@akkea.ca \
--cc=adrian.hunter@intel.com \
--cc=agx@sigxcpu.org \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@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).