All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: Jaehoon Chung <jh80.chung@samsung.com>, sw0312.kim@samsung.com
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: mmc: dw_mmc: log spamming
Date: Mon, 19 Sep 2016 09:41:55 +0200	[thread overview]
Message-ID: <57DF96C3.7050706@math.uni-bielefeld.de> (raw)
In-Reply-To: <6dd25843-3852-b059-4c42-6c720887db38@samsung.com>

Hello Jaehoon,


Jaehoon Chung wrote:
> Hi Tobias,
> 
> CC'd mmc mailing.
> 
> On 09/19/2016 10:03 AM, Seung-Woo Kim wrote:
>> Hello Jaehoon,
>>
>> On 2016년 09월 19일 09:32, Jaehoon Chung wrote:
>>> Hi Tobias,
>>>
>>> On 09/16/2016 02:29 AM, Tobias Jakobi wrote:
>>>> Hello everyone,
>>>>
>>>> I'm experiencing massive kernel log spamming by dw_mmc, the commit that
>>>> causes this is the following one.
>>>>
>>>> 65257a0deed5aee66b4e3708944f0be62a64cabc
>>>>
>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=65257a0deed5aee66b4e3708944f0be62a64cabc
>>>>
>>>> I've briefly checked the commit and I think the rationale behind
>>>> removing the check is incorrect. While MMC_CLKGATE was certainly
>>>> removed, runtime PM has "replaced" it (the commit
>>>> 9eadcc0581a8ccaf4c2378aa1c193fb164304f1d even mentions this).
>>>>
>>>> This is on an Exynos4412 board, kernel is 4.8-rc6. Nothing is connected
>>>> to the eMMC connector.
>>>
>>> Thanks for reporting this.
>>>
>>> Seung-Woo, Could you check your patch? I will also check this.
> 
> Did you test after reverting this commit? or previous version is working fine?
yes, reverting the commit fixes the log spamming. I'm aware though that
the check is more of less broken (undefined behaviour because of
bit-shifting with large values), so I have also tried the following
thing: Just checking against 'div' instead of 'clock << div'. Anyway,
this also works for me.


> Which exynos4412 board do you use? I think it's related with "broken-cd".
> (If you can share which board and dts you are using, we can check in more detail.)
This is an Odroid-X2 board.


> As you mentioned, you didn't insert the eMMC card on board.
> Then it should be polling whether card is inserted/removed. (If broken-cd is set...)
I can check the callstack leading to dw_mci_setup_bus() I guess. Would
that should make it easier for you guys to understand where the issue
originates from?


> I think it's not related with runtime PM.
> 
> Best Regards,
> Jaehoon Chung

WIth best wishes,
Tobias




>> Ok, I will check on Exynos4412 SpC boards.
>>
>> By the way, to check no condition case, when I posted after v2[1], I
>> checked with Exynos5422 and Exynos5433 SoC boards and they didn't show
>> duplicated log, so I agreed not to check condition for logging.
>>
>> [1] https://patchwork.kernel.org/patch/9182469/
>>
>> Best Regards,
>> - Seung-Woo Kim
>>
>>>
>>> Best Regards,
>>> Jaehoon Chung
>>>
>>>>
>>>> With best wishes,
>>>> Tobias
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
> 


  reply	other threads:[~2016-09-19  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20160915172951epcas1p13022fec9254b5903b353dff6398cbcae@epcas1p1.samsung.com>
     [not found] ` <57DADA85.2000200@math.uni-bielefeld.de>
     [not found]   ` <a36ad9ba-1758-7048-d8b8-e3d85862ff08@samsung.com>
     [not found]     ` <57DF396E.9050503@samsung.com>
2016-09-19  7:33       ` mmc: dw_mmc: log spamming Jaehoon Chung
2016-09-19  7:41         ` Tobias Jakobi [this message]
2016-09-19  7:54           ` Jaehoon Chung
2016-09-19 10:00             ` Tobias Jakobi
2016-09-20  6:30               ` Jaehoon Chung
2016-09-20 12:09                 ` Tobias Jakobi
2016-09-21 13:41                 ` Tobias Jakobi

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=57DF96C3.7050706@math.uni-bielefeld.de \
    --to=tjakobi@math.uni-bielefeld.de \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=sw0312.kim@samsung.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 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.