[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F404E9C8-AE64-4B36-AD1B-911BD3C33946@gmail.com>
Date: Wed, 14 Feb 2018 08:50:16 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Michal Suchanek <msuchanek@...e.de>,
Ulf Hansson <ulf.hansson@...aro.org>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
Eric Anholt <eric@...olt.net>,
Stefan Wahren <stefan.wahren@...e.com>,
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 2/2] mmc: bcm2835: print some informational messages during reset
On February 14, 2018 6:38:58 AM PST, Michal Suchanek <msuchanek@...e.de> wrote:
>The previous patch does reset during hardware error so make the reset
>progress more visible.
Based on your previous email it looks like this can happen quite frequently so we might be spamming the kernel log with such reset messages. Turning this into a debug print would not be great either, how about a custom sysfs attribute counting the number of times a reset was done?
We should ideally root cause this but I am sure we can.
--
Florian
Powered by blists - more mailing lists