All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nguyen Viet Dung <nv-dung@jinso.co.jp>
To: linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
	ltsi-dev@lists.linuxfoundation.org, "Simon さん" <simon@horms.net>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: S開12/坂戸SC <ryusuke.sakato.bx@renesas.com>,
	"Shimoda, Yoshihiro" <yoshihiro.shimoda.uh@renesas.com>,
	"Magnus さん" <magnus.damm@gmail.com>,
	"Hisao Munakata" <hisao.munakata.vt@renesas.com>
Subject: Re: [bug] kernel panic if writting data to mmc after suspendding
Date: Mon, 14 Dec 2015 11:34:40 +0900	[thread overview]
Message-ID: <566E2AC0.8060800@jinso.co.jp> (raw)
In-Reply-To: <566A21D2.4080009@jinso.co.jp>

Hello Mr.Geert

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

Please confirm for this failure with error log on Lager(Rcar-H2).
Log:LAGER_ltsi-v4.1.13-rc1_copy-to-mmc-after-suspend-error_log.txt
Best regard,
Nguyen Viet Dung

WARNING: multiple messages have this Message-ID (diff)
From: Nguyen Viet Dung <nv-dung@jinso.co.jp>
To: linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
	ltsi-dev@lists.linuxfoundation.org, "Simon さん" <simon@horms.net>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: S開12/坂戸SC <ryusuke.sakato.bx@renesas.com>,
	"Shimoda, Yoshihiro" <yoshihiro.shimoda.uh@renesas.com>,
	"Magnus さん" <magnus.damm@gmail.com>,
	"Hisao Munakata" <hisao.munakata.vt@renesas.com>
Subject: Re: [bug] kernel panic if writting data to mmc after suspendding
Date: Mon, 14 Dec 2015 02:34:40 +0000	[thread overview]
Message-ID: <566E2AC0.8060800@jinso.co.jp> (raw)
In-Reply-To: <566A21D2.4080009@jinso.co.jp>

Hello Mr.Geert

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

Please confirm for this failure with error log on Lager(Rcar-H2).
Log:LAGER_ltsi-v4.1.13-rc1_copy-to-mmc-after-suspend-error_log.txt
Best regard,
Nguyen Viet Dung

  reply	other threads:[~2015-12-14  2:34 UTC|newest]

Thread overview: 18+ 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-11  1:07 ` Nguyen Viet Dung
2015-12-14  2:34 ` Nguyen Viet Dung [this message]
2015-12-14  2:34   ` Nguyen Viet Dung
2015-12-14  2:49   ` Nguyen Viet Dung
2015-12-14  2:49     ` Nguyen Viet Dung
2015-12-18  9:33   ` Geert Uytterhoeven
2015-12-18  9:33     ` Geert Uytterhoeven
2015-12-18 10:27     ` Ulf Hansson
2015-12-18 10:27       ` Ulf Hansson
2015-12-22  3:16       ` Nguyen Viet Dung
2015-12-22  3:16         ` Nguyen Viet Dung
2016-02-04  0:52         ` Nguyen Viet Dung
2016-02-04  0:52           ` Nguyen Viet Dung
2016-02-04  8:26           ` Ulf Hansson
2016-02-04  8:26             ` Ulf Hansson
2016-02-05 17:34             ` 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=566E2AC0.8060800@jinso.co.jp \
    --to=nv-dung@jinso.co.jp \
    --cc=geert+renesas@glider.be \
    --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=magnus.damm@gmail.com \
    --cc=ryusuke.sakato.bx@renesas.com \
    --cc=simon@horms.net \
    --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 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.