From: Tim Harvey <tharvey@gateworks.com>
To: Linux MMC List <linux-mmc@vger.kernel.org>,
Marcel Ziswiler <marcel@ziswiler.com>,
Fabio Estevam <festevam@gmail.com>,
Schrempf Frieder <frieder.schrempf@kontron.de>,
Adam Ford <aford173@gmail.com>, Haibo Chen <haibo.chen@nxp.com>,
Lucas Stach <l.stach@pengutronix.de>, Peng Fan <peng.fan@nxp.com>,
Frank Li <Frank.Li@nxp.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Shawn Guo <shawnguo@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
Cale Collins <ccollins@gateworks.com>
Subject: IMX8MM eMMC CQHCI timeout
Date: Fri, 29 Oct 2021 13:47:29 -0700 [thread overview]
Message-ID: <CAJ+vNU2Vt2hWW=Yxh5W=bVerJjwbNoJpTDGgXxUUo9PZvzFe9A@mail.gmail.com> (raw)
Greetings,
I've encountered the following MMC CQHCI timeout message a couple of
times now on IMX8MM boards with eMMC with a 5.10 based kernel:
[ 224.356283] mmc2: cqhci: ============ CQHCI REGISTER DUMP ===========
[ 224.362764] mmc2: cqhci: Caps: 0x0000310a | Version: 0x00000510
[ 224.369250] mmc2: cqhci: Config: 0x00001001 | Control: 0x00000000
[ 224.375726] mmc2: cqhci: Int stat: 0x00000000 | Int enab: 0x00000006
[ 224.382197] mmc2: cqhci: Int sig: 0x00000006 | Int Coal: 0x00000000
[ 224.388665] mmc2: cqhci: TDL base: 0x8003f000 | TDL up32: 0x00000000
[ 224.395129] mmc2: cqhci: Doorbell: 0xbf01dfff | TCN: 0x00000000
[ 224.401598] mmc2: cqhci: Dev queue: 0x00000000 | Dev Pend: 0x08000000
[ 224.408064] mmc2: cqhci: Task clr: 0x00000000 | SSC1: 0x00011000
[ 224.414532] mmc2: cqhci: SSC2: 0x00000001 | DCMD rsp: 0x00000800
[ 224.420997] mmc2: cqhci: RED mask: 0xfdf9a080 | TERRI: 0x00000000
[ 224.427467] mmc2: cqhci: Resp idx: 0x0000000d | Resp arg: 0x00000000
[ 224.433934] mmc2: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 224.440404] mmc2: sdhci: Sys addr: 0x7c722000 | Version: 0x00000002
[ 224.446877] mmc2: sdhci: Blk size: 0x00000200 | Blk cnt: 0x00000020
[ 224.453346] mmc2: sdhci: Argument: 0x00018000 | Trn mode: 0x00000023
[ 224.459811] mmc2: sdhci: Present: 0x01f88008 | Host ctl: 0x00000030
[ 224.466281] mmc2: sdhci: Power: 0x00000002 | Blk gap: 0x00000080
[ 224.472752] mmc2: sdhci: Wake-up: 0x00000008 | Clock: 0x0000000f
[ 224.479225] mmc2: sdhci: Timeout: 0x0000008f | Int stat: 0x00000000
[ 224.485690] mmc2: sdhci: Int enab: 0x107f4000 | Sig enab: 0x107f4000
[ 224.492161] mmc2: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000502
[ 224.498628] mmc2: sdhci: Caps: 0x07eb0000 | Caps_1: 0x8000b407
[ 224.505097] mmc2: sdhci: Cmd: 0x00000d1a | Max curr: 0x00ffffff
[ 224.511575] mmc2: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0xffc003ff
[ 224.518043] mmc2: sdhci: Resp[2]: 0x328f5903 | Resp[3]: 0x00d07f01
[ 224.524512] mmc2: sdhci: Host ctl2: 0x00000088
[ 224.528986] mmc2: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0xfe179020
[ 224.535451] mmc2: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS DUMP ====
[ 224.543052] mmc2: sdhci-esdhc-imx: cmd debug status: 0x2120
[ 224.548740] mmc2: sdhci-esdhc-imx: data debug status: 0x2200
[ 224.554510] mmc2: sdhci-esdhc-imx: trans debug status: 0x2300
[ 224.560368] mmc2: sdhci-esdhc-imx: dma debug status: 0x2400
[ 224.566054] mmc2: sdhci-esdhc-imx: adma debug status: 0x2510
[ 224.571826] mmc2: sdhci-esdhc-imx: fifo debug status: 0x2680
[ 224.577608] mmc2: sdhci-esdhc-imx: async fifo debug status: 0x2750
[ 224.583900] mmc2: sdhci: ============================================
I don't know how to make the issue occur, both times it occured simply
reading a file in the rootfs ext4 fs on the emmc.
Some research shows:
- https://community.nxp.com/t5/i-MX-Processors/The-issues-on-quot-mmc0-cqhci-timeout-for-tag-0-quot/m-p/993779
- http://git.toradex.com/cgit/linux-toradex.git/commit/?h=toradex_5.4-2.3.x-imx&id=fd33531be843566c59a5fc655f204bbd36d7f3c6
I'm not clear if this info is up-to-date. The NXP 5.4 kernel did not
enable this feature but if I'm not mistaken CQHCI support itself
didn't land in mainline until a later kernel so it would make sense it
was not enabled at that time. I do see the NXP 5.10 kernels have this
enabled so I'm curious if it is an issue there.
Any other IMX8MM or other SoC users know what this could be about or
what I could do for a test to try to reproduce it so I can see if it
occurs in other kernel versions?
Best regards,
Tim
next reply other threads:[~2021-10-29 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 20:47 Tim Harvey [this message]
2021-11-01 1:57 ` IMX8MM eMMC CQHCI timeout Bough Chen
2021-11-03 16:49 ` Tim Harvey
2021-11-03 16:54 ` [PATCH] mmc: sdhci-esdhc-imx: disable CMDQ support Tim Harvey
2021-11-03 17:12 ` Fabio Estevam
2021-11-04 2:06 ` Bough Chen
2021-11-04 2:06 ` Bough Chen
2021-11-05 7:56 ` Adrian Hunter
2021-11-15 14:54 ` Ulf Hansson
2021-11-03 17:21 ` IMX8MM eMMC CQHCI timeout Marcel Ziswiler
2021-11-04 2:13 ` Bough Chen
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='CAJ+vNU2Vt2hWW=Yxh5W=bVerJjwbNoJpTDGgXxUUo9PZvzFe9A@mail.gmail.com' \
--to=tharvey@gateworks.com \
--cc=Frank.Li@nxp.com \
--cc=adrian.hunter@intel.com \
--cc=aford173@gmail.com \
--cc=ccollins@gateworks.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-mmc@vger.kernel.org \
--cc=marcel@ziswiler.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.