* sh_mobile_sdhi ee100000.mmc: timeout waiting for hardware interrupt (CMD19)
@ 2022-09-30 8:53 Geert Uytterhoeven
2022-10-01 6:43 ` Wolfram Sang
0 siblings, 1 reply; 3+ messages in thread
From: Geert Uytterhoeven @ 2022-09-30 8:53 UTC (permalink / raw)
To: Wolfram Sang; +Cc: Linux MMC List, Linux-Renesas
Hi Wolfram,
When an SD-card is inserted on Koelsch (R-Car M2-W), I see:
sh_mobile_sdhi ee100000.mmc: timeout waiting for hardware interrupt (CMD19)
Regardless, the card works afterwards:
mmc0: new ultra high speed SDR104 SDHC card at address aaaa
mmcblk0: mmc0:aaaa SM32G 29.7 GiB
mmcblk0: p1 p2
Note that this only happens for the "fast" slot (SDHI0), not for the
(33%) slower slot.
On Salvator-XS (R-Car H3 ES2.0) I do not see that timeout message
(and reading is 4x faster than on Koelsch).
Sometimes, I also see:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 37 at kernel/dma/debug.c:568 add_dma_entry+0x1f8/0x248
DMA-API: rcar-dmac e6700000.dma-controller: cacheline tracking
EEXIST, overlapping mappings aren't supported
Modules linked in:
CPU: 0 PID: 37 Comm: kworker/0:3 Tainted: G N
6.0.0-rc7-koelsch-00770-g14669bb22198 #1686
Hardware name: Generic R-Car Gen2 (Flattened Device Tree)
Workqueue: events_freezable mmc_rescan
unwind_backtrace from show_stack+0x10/0x14
show_stack from dump_stack_lvl+0x68/0x90
dump_stack_lvl from __warn+0xa8/0x1d8
__warn from warn_slowpath_fmt+0x78/0xb0
warn_slowpath_fmt from add_dma_entry+0x1f8/0x248
add_dma_entry from debug_dma_map_sg+0x250/0x35c
debug_dma_map_sg from __dma_map_sg_attrs+0x6c/0x11c
__dma_map_sg_attrs from dma_map_sg_attrs+0x10/0x1c
dma_map_sg_attrs from renesas_sdhi_sys_dmac_start_dma+0xf8/0x424
renesas_sdhi_sys_dmac_start_dma from tmio_process_mrq+0x124/0x264
tmio_process_mrq from mmc_start_request+0x90/0xa4
mmc_start_request from mmc_wait_for_req+0x64/0xac
mmc_wait_for_req from mmc_send_tuning+0xf4/0x16c
mmc_send_tuning from renesas_sdhi_execute_tuning+0x2a0/0x41c
renesas_sdhi_execute_tuning from mmc_execute_tuning+0x58/0xb8
mmc_execute_tuning from mmc_sd_init_uhs_card.part.0+0x2f0/0x3d4
mmc_sd_init_uhs_card.part.0 from mmc_sd_init_card+0x35c/0x7d4
mmc_sd_init_card from mmc_attach_sd+0xe8/0x164
mmc_attach_sd from mmc_rescan+0x1f0/0x25c
mmc_rescan from process_one_work+0x2f0/0x4c4
process_one_work from worker_thread+0x240/0x2d0
worker_thread from kthread+0xd0/0xe0
kthread from ret_from_fork+0x14/0x34
Exception stack(0xf0925fb0 to 0xf0925ff8)
5fa0: 00000000 00000000
00000000 00000000
5fc0: 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000
5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
irq event stamp: 3717
hardirqs last enabled at (3729): [<c027e610>] __up_console_sem+0x40/0x60
hardirqs last disabled at (3742): [<c027e5f4>] __up_console_sem+0x24/0x60
softirqs last enabled at (3716): [<c0201330>] __do_softirq+0x168/0x400
softirqs last disabled at (3637): [<c0228590>] __irq_exit_rcu+0x114/0x174
---[ end trace 0000000000000000 ]---
DMA-API: Mapped at:
__dma_map_sg_attrs+0x6c/0x11c
dma_map_sg_attrs+0x10/0x1c
renesas_sdhi_sys_dmac_start_dma+0xf8/0x424
tmio_process_mrq+0x124/0x264
mmc_start_request+0x90/0xa4
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sh_mobile_sdhi ee100000.mmc: timeout waiting for hardware interrupt (CMD19)
2022-09-30 8:53 sh_mobile_sdhi ee100000.mmc: timeout waiting for hardware interrupt (CMD19) Geert Uytterhoeven
@ 2022-10-01 6:43 ` Wolfram Sang
2022-10-01 11:57 ` Geert Uytterhoeven
0 siblings, 1 reply; 3+ messages in thread
From: Wolfram Sang @ 2022-10-01 6:43 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Linux MMC List, Linux-Renesas
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
On Fri, Sep 30, 2022 at 10:53:55AM +0200, Geert Uytterhoeven wrote:
> Hi Wolfram,
>
> When an SD-card is inserted on Koelsch (R-Car M2-W), I see:
>
> sh_mobile_sdhi ee100000.mmc: timeout waiting for hardware interrupt (CMD19)
Is this a regression? If so, since when? I seem to recall this is
"expected" on Gen2, we ensured that it retries gracefully and
successfuly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sh_mobile_sdhi ee100000.mmc: timeout waiting for hardware interrupt (CMD19)
2022-10-01 6:43 ` Wolfram Sang
@ 2022-10-01 11:57 ` Geert Uytterhoeven
0 siblings, 0 replies; 3+ messages in thread
From: Geert Uytterhoeven @ 2022-10-01 11:57 UTC (permalink / raw)
To: Wolfram Sang; +Cc: Linux MMC List, Linux-Renesas
Hi Wolfram,
On Sat, Oct 1, 2022 at 8:44 AM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> On Fri, Sep 30, 2022 at 10:53:55AM +0200, Geert Uytterhoeven wrote:
> > When an SD-card is inserted on Koelsch (R-Car M2-W), I see:
> >
> > sh_mobile_sdhi ee100000.mmc: timeout waiting for hardware interrupt (CMD19)
>
> Is this a regression? If so, since when? I seem to recall this is
> "expected" on Gen2, we ensured that it retries gracefully and
> successfuly.
No, this is not a (recent) regression. I reported it before.
The "EEXIST, overlapping mappings aren't supported" was also
reported before.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-10-01 11:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-30 8:53 sh_mobile_sdhi ee100000.mmc: timeout waiting for hardware interrupt (CMD19) Geert Uytterhoeven
2022-10-01 6:43 ` Wolfram Sang
2022-10-01 11:57 ` Geert Uytterhoeven
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).