From: "Michal Suchánek" <msuchanek@suse.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Michal Suchanek <msuchanek@suse.de>,
Ulf Hansson <ulf.hansson@linaro.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Eric Anholt <eric@anholt.net>,
Stefan Wahren <stefan.wahren@i2se.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
linux-mmc@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mmc: bcm2835: print some informational messages during reset
Date: Wed, 14 Feb 2018 20:47:33 +0100 [thread overview]
Message-ID: <20180214204733.7987d16c@naga.suse.cz> (raw)
In-Reply-To: <F404E9C8-AE64-4B36-AD1B-911BD3C33946@gmail.com>
On Wed, 14 Feb 2018 08:50:16 -0800
Florian Fainelli <f.fainelli@gmail.com> wrote:
> On February 14, 2018 6:38:58 AM PST, Michal Suchanek
> <msuchanek@suse.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?
Since every such message happens when the system stalls for like half a
minute I don't think there will be that many until somebody notices
something is amiss. It might be also helpful in diagnosing if other
cards lock up in different way - for me the DMA shutdown is short so I
guess it's the mmc host that is locked up and the DMA engine is fine.
It might look differently on different systems, though.
I understand that adding messages it somewhat controversial so I added
them in separate patch.
Thanks
Michal
next prev parent reply other threads:[~2018-02-14 19:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 14:38 [PATCH 1/2] mmc: bcm2835: reset host on timeout Michal Suchanek
2018-02-14 14:38 ` [PATCH 2/2] mmc: bcm2835: print some informational messages during reset Michal Suchanek
2018-02-14 16:50 ` Florian Fainelli
2018-02-14 19:47 ` Michal Suchánek [this message]
2018-02-15 18:22 ` Stefan Wahren
2018-03-04 15:46 ` Michal Suchánek
2018-02-14 16:50 ` Florian Fainelli
2018-02-14 14:58 ` [PATCH 1/2] mmc: bcm2835: reset host on timeout Stefan Wahren
2018-02-14 15:36 ` Michal Suchánek
2018-02-14 15:58 ` Michal Suchánek
2018-02-14 16:49 ` Stefan Wahren
2018-02-14 19:24 ` Michal Suchánek
2018-02-14 20:30 ` Stefan Wahren
2018-03-04 15:57 ` Michal Suchánek
2018-03-04 18:11 ` Stefan Wahren
2018-03-04 18:44 ` Michal Suchánek
2018-03-03 13:58 ` Stefan Wahren
2018-03-04 16:04 ` Michal Suchánek
2018-03-04 16:36 ` Michal Suchánek
2018-03-04 18:15 ` Stefan Wahren
2018-03-06 19:21 ` Michal Suchánek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180214204733.7987d16c@naga.suse.cz \
--to=msuchanek@suse.de \
--cc=Julia.Lawall@lip6.fr \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=garsilva@embeddedor.com \
--cc=kraxel@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox