Re: Linux 5.18.x: sdhci issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 1, 2022 at 8:08 AM Yegor Yefremov
<yegorslists@xxxxxxxxxxxxxx> wrote:
> On Tue, May 31, 2022 at 11:23 AM Arnd Bergmann <arnd@xxxxxxxx> wrote:
> > On Tue, May 31, 2022 at 10:28 AM Yegor Yefremov
> >
> > +       WARN_ON_ONCE(memory_intersects(_stext, _etext, buf, size));
> > +       WARN_ON_ONCE(memory_intersects(__start_rodata, __end_rodata,
> > buf, size));
> > +       WARN_ON_ONCE(object_is_on_stack(buf));
> > +       WARN_ON_ONCE(is_vmalloc_or_module_addr(buf));
> > +
> >         /* Do the bulk of the transfer using block mode (if supported). */
> >         if (func->card->cccr.multi_block && (size > sdio_max_byte_size(func))) {
> >                 /* Blocks per command is limited by host count, host transfer
> >
> >  Does that show something new?
> >
> > If this is a block device, the change won't help, but I can't find a good place
> > to hook into that at the moment. mmc_mq_queue_rq() might work, but
> > I think that is still called asynchronously.
>
> No, the patch provides the same output.

Can you say what devices are attached to the mmc controller? Is it
an eMMC block device, an SDIO device, or both?

         Arnd



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux