* [BUG] 5.6-rc1 breaks sdhci on tegra-30 ouya
@ 2020-03-05 20:56 ` Peter Geis
0 siblings, 0 replies; 4+ messages in thread
From: Peter Geis @ 2020-03-05 20:56 UTC (permalink / raw)
To: Ulf Hansson
Cc: linux-mmc-u79uwXL29TY76Z2rM5mHXA, Dmitry Osipenko,
linux-tegra-u79uwXL29TY76Z2rM5mHXA
Good Afternoon,
I have been fighting a bug with sdhci on the tegra-30 based ouya since 5.6-rc1.
I've traced it to the following commit:
mmc: core: Specify timeouts for BKOPS and CACHE_FLUSH for eMMC
24ed3bd01d6a844fd5e8a75f48d0a3d10ed71bf9
[ 51.401369] mmc0: Card stuck being busy! mmc_poll_for_busy
[ 51.407288] mmc0: cache flush error -110
[ 51.412347] blk_update_request: I/O error, dev mmcblk0, sector 0 op
0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
It also caused issues with hitching with the bcm4330 sdio wifi chip.
Reverting this commit fixes the issue.
After reverting this commit, with the following commit still intact:
mmc: core: Default to generic_cmd6_time as timeout in __mmc_switch()
I am seeing a lot of the following messages:
[ 22.626377] mmc0: unspecified timeout for CMD6 - use generic
[ 22.687349] mmc0: unspecified timeout for CMD6 - use generic
[ 23.362736] mmc0: unspecified timeout for CMD6 - use generic
[ 23.487824] mmc0: unspecified timeout for CMD6 - use generic
[ 23.547674] mmc0: unspecified timeout for CMD6 - use generic
[ 23.745527] mmc0: unspecified timeout for CMD6 - use generic
[ 23.817678] mmc0: unspecified timeout for CMD6 - use generic
[ 24.045600] mmc0: unspecified timeout for CMD6 - use generic
[ 24.155577] mmc0: unspecified timeout for CMD6 - use generic
[ 24.223448] mmc0: unspecified timeout for CMD6 - use generic
[ 24.286257] mmc0: unspecified timeout for CMD6 - use generic
Very Respectfully,
Peter Geis
^ permalink raw reply [flat|nested] 4+ messages in thread
* [BUG] 5.6-rc1 breaks sdhci on tegra-30 ouya
@ 2020-03-05 20:56 ` Peter Geis
0 siblings, 0 replies; 4+ messages in thread
From: Peter Geis @ 2020-03-05 20:56 UTC (permalink / raw)
To: Ulf Hansson; +Cc: linux-mmc, Dmitry Osipenko, linux-tegra
Good Afternoon,
I have been fighting a bug with sdhci on the tegra-30 based ouya since 5.6-rc1.
I've traced it to the following commit:
mmc: core: Specify timeouts for BKOPS and CACHE_FLUSH for eMMC
24ed3bd01d6a844fd5e8a75f48d0a3d10ed71bf9
[ 51.401369] mmc0: Card stuck being busy! mmc_poll_for_busy
[ 51.407288] mmc0: cache flush error -110
[ 51.412347] blk_update_request: I/O error, dev mmcblk0, sector 0 op
0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
It also caused issues with hitching with the bcm4330 sdio wifi chip.
Reverting this commit fixes the issue.
After reverting this commit, with the following commit still intact:
mmc: core: Default to generic_cmd6_time as timeout in __mmc_switch()
I am seeing a lot of the following messages:
[ 22.626377] mmc0: unspecified timeout for CMD6 - use generic
[ 22.687349] mmc0: unspecified timeout for CMD6 - use generic
[ 23.362736] mmc0: unspecified timeout for CMD6 - use generic
[ 23.487824] mmc0: unspecified timeout for CMD6 - use generic
[ 23.547674] mmc0: unspecified timeout for CMD6 - use generic
[ 23.745527] mmc0: unspecified timeout for CMD6 - use generic
[ 23.817678] mmc0: unspecified timeout for CMD6 - use generic
[ 24.045600] mmc0: unspecified timeout for CMD6 - use generic
[ 24.155577] mmc0: unspecified timeout for CMD6 - use generic
[ 24.223448] mmc0: unspecified timeout for CMD6 - use generic
[ 24.286257] mmc0: unspecified timeout for CMD6 - use generic
Very Respectfully,
Peter Geis
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [BUG] 5.6-rc1 breaks sdhci on tegra-30 ouya
2020-03-05 20:56 ` Peter Geis
@ 2020-03-06 10:32 ` Jon Hunter
-1 siblings, 0 replies; 4+ messages in thread
From: Jon Hunter @ 2020-03-06 10:32 UTC (permalink / raw)
To: Peter Geis, Ulf Hansson
Cc: linux-mmc-u79uwXL29TY76Z2rM5mHXA, Dmitry Osipenko,
linux-tegra-u79uwXL29TY76Z2rM5mHXA
Hi Peter,
On 05/03/2020 20:56, Peter Geis wrote:
> Good Afternoon,
>
> I have been fighting a bug with sdhci on the tegra-30 based ouya since 5.6-rc1.
> I've traced it to the following commit:
>
> mmc: core: Specify timeouts for BKOPS and CACHE_FLUSH for eMMC
> 24ed3bd01d6a844fd5e8a75f48d0a3d10ed71bf9
>
> [ 51.401369] mmc0: Card stuck being busy! mmc_poll_for_busy
> [ 51.407288] mmc0: cache flush error -110
> [ 51.412347] blk_update_request: I/O error, dev mmcblk0, sector 0 op
> 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
>
> It also caused issues with hitching with the bcm4330 sdio wifi chip.
>
> Reverting this commit fixes the issue.
>
> After reverting this commit, with the following commit still intact:
>
> mmc: core: Default to generic_cmd6_time as timeout in __mmc_switch()
>
> I am seeing a lot of the following messages:
> [ 22.626377] mmc0: unspecified timeout for CMD6 - use generic
> [ 22.687349] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.362736] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.487824] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.547674] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.745527] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.817678] mmc0: unspecified timeout for CMD6 - use generic
> [ 24.045600] mmc0: unspecified timeout for CMD6 - use generic
> [ 24.155577] mmc0: unspecified timeout for CMD6 - use generic
> [ 24.223448] mmc0: unspecified timeout for CMD6 - use generic
> [ 24.286257] mmc0: unspecified timeout for CMD6 - use generic
Yes we are seeing this on other Tegra platforms. This is being triaged
in the following thread ...
https://lkml.org/lkml/2020/2/13/781
Cheers
Jon
--
nvpublic
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [BUG] 5.6-rc1 breaks sdhci on tegra-30 ouya
@ 2020-03-06 10:32 ` Jon Hunter
0 siblings, 0 replies; 4+ messages in thread
From: Jon Hunter @ 2020-03-06 10:32 UTC (permalink / raw)
To: Peter Geis, Ulf Hansson; +Cc: linux-mmc, Dmitry Osipenko, linux-tegra
Hi Peter,
On 05/03/2020 20:56, Peter Geis wrote:
> Good Afternoon,
>
> I have been fighting a bug with sdhci on the tegra-30 based ouya since 5.6-rc1.
> I've traced it to the following commit:
>
> mmc: core: Specify timeouts for BKOPS and CACHE_FLUSH for eMMC
> 24ed3bd01d6a844fd5e8a75f48d0a3d10ed71bf9
>
> [ 51.401369] mmc0: Card stuck being busy! mmc_poll_for_busy
> [ 51.407288] mmc0: cache flush error -110
> [ 51.412347] blk_update_request: I/O error, dev mmcblk0, sector 0 op
> 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
>
> It also caused issues with hitching with the bcm4330 sdio wifi chip.
>
> Reverting this commit fixes the issue.
>
> After reverting this commit, with the following commit still intact:
>
> mmc: core: Default to generic_cmd6_time as timeout in __mmc_switch()
>
> I am seeing a lot of the following messages:
> [ 22.626377] mmc0: unspecified timeout for CMD6 - use generic
> [ 22.687349] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.362736] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.487824] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.547674] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.745527] mmc0: unspecified timeout for CMD6 - use generic
> [ 23.817678] mmc0: unspecified timeout for CMD6 - use generic
> [ 24.045600] mmc0: unspecified timeout for CMD6 - use generic
> [ 24.155577] mmc0: unspecified timeout for CMD6 - use generic
> [ 24.223448] mmc0: unspecified timeout for CMD6 - use generic
> [ 24.286257] mmc0: unspecified timeout for CMD6 - use generic
Yes we are seeing this on other Tegra platforms. This is being triaged
in the following thread ...
https://lkml.org/lkml/2020/2/13/781
Cheers
Jon
--
nvpublic
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-03-06 10:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-05 20:56 [BUG] 5.6-rc1 breaks sdhci on tegra-30 ouya Peter Geis
2020-03-05 20:56 ` Peter Geis
[not found] ` <CAMdYzYoxsBAyBhp+S6LKE060qLLq=XioVVPUmOka0auOo8aXcg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-03-06 10:32 ` Jon Hunter
2020-03-06 10:32 ` Jon Hunter
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.