From: Nguyen Viet Dung <nv-dung@jinso.co.jp>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux MMC List <linux-mmc@vger.kernel.org>
Cc: "Linux-sh list" <linux-sh@vger.kernel.org>,
"ltsi-dev@lists.linuxfoundation.org"
<ltsi-dev@lists.linuxfoundation.org>,
"Simon さん" <simon@horms.net>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Shimoda, Yoshihiro" <yoshihiro.shimoda.uh@renesas.com>,
"Hisao Munakata" <hisao.munakata.vt@renesas.com>
Subject: Re: [bug] kernel panic if writting data to mmc after suspendding
Date: Thu, 4 Feb 2016 09:52:17 +0900 [thread overview]
Message-ID: <56B2A0C1.9050808@jinso.co.jp> (raw)
In-Reply-To: <5678C081.5090001@jinso.co.jp>
Hi Ulf
I want to test this problem withc your patch.
Please sent pacthset for me.
I have checked below link but detail of patch haven't.
Best regard,
Nguyen Viet Dung
On 2015年12月22日 12:16, Nguyen Viet Dung wrote:
> Hi Geert
>
> Thank for your reply.
>
> On 2015年12月18日 19:27, Ulf Hansson wrote:
>> On 18 December 2015 at 10:33, Geert Uytterhoeven
>> <geert@linux-m68k.org> wrote:
>>> Hi Dung-san,
>>>
>>> CC Ulf
>>>
>>> On Mon, Dec 14, 2015 at 3:34 AM, Nguyen Viet Dung
>>> <nv-dung@jinso.co.jp> wrote:
>>>> While is testting LTSI-v4.1.13-rc1, we have found the following the
>>>> failure
>>>> of mmcif.
>>>> 1. mount mmc block
>>>> 2. write data to mmc block
>>>> 3. suspend/resume
>>>> 4. write data to mmc block one again => happen kernel panic
>>>> (Probability in this test procedure is 100%)
>>>>
>>>> We have used git bisect to find cause of failure in LTS-v4.1.13 to
>>>> LTSI-v4.1.13-rc1
>>>> and have found commit which cause failure.
>>>> (On LTS-v4.1.13 has not this failure)
>>>> drivers: sh: Disable PM runtime for multi-platform ARM with genpd
>>>> commit :cbc41d0a761bffb3166a413a3c77100a737c0cd7
>>> That means there's a bug in Runtime PM handling of the sh_mmcif
>>> driver, or
>>> in the MMC subsystem.
>>>
>>> Usually such bugs cause a kernel hang on register access, not a NULL
>>> pointer
>>> dereference, though.
>> Agree!
>>
>> I doubt the bisected commit is where the *real* issue is. Looking into
>> the details for how system PM and runtime PM is deployed in sh_mmcif,
>> I believe some improvements are needed.
>>
>> Actually, I made an attempt to modernize the PM code for sh_mmcif a
>> while ago.
>> http://marc.info/?l=linux-mmc&m=138245085523815&w=2
>>
>> Whether that fixes the problem reported here, I have no idea. Although
>> if not, it should move the code to a position where it becomes easier
>> to properly fix this issue.
>>
>> I am willing to help and rebase that patchset, but I require help in
>> testing since I haven't been able to get a hold of a HW. Can I count
>> on that?
> Yes , I can help you test.
> If you have rebased patchset, phease tell me.
>
> Best regards,
> Nguyen Viet Dung
next prev parent reply other threads:[~2016-02-04 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 1:07 [bug] kernel panic if writting data to mmc after suspendding Nguyen Viet Dung
2015-12-14 2:34 ` Nguyen Viet Dung
2015-12-14 2:49 ` Nguyen Viet Dung
2015-12-18 9:33 ` Geert Uytterhoeven
2015-12-18 10:27 ` Ulf Hansson
2015-12-22 3:16 ` Nguyen Viet Dung
2016-02-04 0:52 ` Nguyen Viet Dung [this message]
2016-02-04 8:26 ` Ulf Hansson
2016-02-05 17:34 ` Ulf Hansson
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=56B2A0C1.9050808@jinso.co.jp \
--to=nv-dung@jinso.co.jp \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=hisao.munakata.vt@renesas.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ltsi-dev@lists.linuxfoundation.org \
--cc=simon@horms.net \
--cc=ulf.hansson@linaro.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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