[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPDyKFo-vEO7zN_F+NqcKtnKmAo_deOZx3gYNiks3yTAQAjv-Q@mail.gmail.com>
Date: Fri, 21 Feb 2020 10:48:23 +0100
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Jens Axboe <axboe@...nel.dk>, Alexei Starovoitov <ast@...nel.org>,
linux-block <linux-block@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
open list <linux-kernel@...r.kernel.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
John Stultz <john.stultz@...aro.org>
Subject: Re: LKFT: arm x15: mmc1: cache flush error -110
On Thu, 20 Feb 2020 at 18:54, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
>
> On Wed, 19 Feb 2020 at 21:54, Ulf Hansson <ulf.hansson@...aro.org> wrote:
> >
> > On Thu, 13 Feb 2020 at 16:43, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> > >
> >
> > Try to restore the value for the cache flush timeout, by updating the
> > define MMC_CACHE_FLUSH_TIMEOUT_MS to 10 * 60 * 1000".
>
> I have increased the timeout to 10 minutes but it did not help.
> Same error found.
> [ 608.679353] mmc1: Card stuck being busy! mmc_poll_for_busy
> [ 608.684964] mmc1: cache flush error -110
> [ 608.689005] blk_update_request: I/O error, dev mmcblk1, sector
> 4302400 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
>
> OTOH, What best i could do for my own experiment to revert all three patches and
> now the reported error gone and device mount successfully [1].
>
> List of patches reverted,
> mmc: core: Specify timeouts for BKOPS and CACHE_FLUSH for eMMC
> mmc: block: Use generic_cmd6_time when modifying
> INAND_CMD38_ARG_EXT_CSD
> mmc: core: Default to generic_cmd6_time as timeout in __mmc_switch()
>
> [1] https://lkft.validation.linaro.org/scheduler/job/1238275#L4346
>
> - Naresh
Thanks for testing!
This sounds a bit weird, I must say. Also, while looking into the
logs, it seems like you are comparing a v5.5 kernel with v5.6-rc2, but
maybe I didn't read the logs carefully enough.
In any case, I am looking into creating a debug patch so we can
narrow down the problem a bit further.
Kind regards
Uffe
Powered by blists - more mailing lists