From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Subject: Re: [PATCH 2/2] mmc: bcm2835: print some informational messages during reset Date: Wed, 14 Feb 2018 08:50:16 -0800 Message-ID: References: <97593d6e1a41af1baff61f7d9e6e68a450fc9da6.1518619058.git.msuchanek@suse.de><97593d6e1a41af1baff61f7d9e6e68a450fc9da6.1518619058.git.msuchanek@suse.de> <57ff1e429a7fc12300a3cca0c5e9a637beed0d3a.1518619058.git.msuchanek@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <57ff1e429a7fc12300a3cca0c5e9a637beed0d3a.1518619058.git.msuchanek@suse.de> Sender: linux-kernel-owner@vger.kernel.org To: Michal Suchanek , Ulf Hansson , Ray Jui , Scott Branden , bcm-kernel-feedback-list@broadcom.com, Eric Anholt , Stefan Wahren , Gerd Hoffmann , "Gustavo A. R. Silva" , Julia Lawall , linux-mmc@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org List-Id: linux-mmc@vger.kernel.org On February 14, 2018 6:38:58 AM PST, Michal Suchanek = wrote: >The previous patch does reset during hardware error so make the reset >progress more visible=2E Based on your previous email it looks like this can happen quite frequentl= y so we might be spamming the kernel log with such reset messages=2E Turnin= g this into a debug print would not be great either, how about a custom sys= fs attribute counting the number of times a reset was done? We should ideally root cause this but I am sure we can=2E --=20 Florian