[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1fbf0d77-cb53-f0fa-b810-e9954138d907@i2se.com>
Date: Wed, 14 Feb 2018 15:58:31 +0100
From: Stefan Wahren <stefan.wahren@...e.com>
To: Michal Suchanek <msuchanek@...e.de>,
Ulf Hansson <ulf.hansson@...aro.org>,
Florian Fainelli <f.fainelli@...il.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
Eric Anholt <eric@...olt.net>,
Gerd Hoffmann <kraxel@...hat.com>,
"Gustavo A. R. Silva" <garsilva@...eddedor.com>,
Julia Lawall <Julia.Lawall@...6.fr>, linux-mmc@...r.kernel.org,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] mmc: bcm2835: reset host on timeout
Hi Michal,
Am 14.02.2018 um 15:38 schrieb Michal Suchanek:
> The bcm2835 mmc host tends to lock up for unknown reason so reset it on
> timeout. The upper mmc block layer tries retransimitting with single
> blocks which tends to work out after a long wait.
>
> This is better than giving up and leaving the machine broken for no
> obvious reason.
could you please provide more information about this issue (affected
hardware, kernel config, version, dmesg, reproducible scenario)?
Powered by blists - more mailing lists