From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
stable@vger.kernel.org
Subject: Re: [RESEND PATCH] ARM: EXYNOS: Fix failed second suspend on Exynos4
Date: Tue, 24 Feb 2015 08:59:22 +0100 [thread overview]
Message-ID: <1424764762.2877.3.camel@AMDC1943> (raw)
In-Reply-To: <54EBE43C.1020901@samsung.com>
On wto, 2015-02-24 at 11:38 +0900, Chanwoo Choi wrote:
> Hi Krzysztof,
>
> I tested this patch for suspend-to-ram on Exynos4412-based trats2 board.
> When I tested suspend-to-ram repetitively, I faced on hang issue of
> suspend-to-ram for Exynos4 as before.
>
> Could you send .config file for test?
I am testing on exynos_defconfig with some stuff enabled (nothing
special: regulators, chargers, PM_ADVANCED_DEBUG, extcon etc.). However
sometimes I also see hangs related to MMC. But I believe this issue is
present for some time and is not related to my DELAYED_RESET_ASSERTION
changes.
Maybe you could try to boot with "no_console_suspend loglevel=7" and see
when the suspend fails?
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] ARM: EXYNOS: Fix failed second suspend on Exynos4
Date: Tue, 24 Feb 2015 08:59:22 +0100 [thread overview]
Message-ID: <1424764762.2877.3.camel@AMDC1943> (raw)
In-Reply-To: <54EBE43C.1020901@samsung.com>
On wto, 2015-02-24 at 11:38 +0900, Chanwoo Choi wrote:
> Hi Krzysztof,
>
> I tested this patch for suspend-to-ram on Exynos4412-based trats2 board.
> When I tested suspend-to-ram repetitively, I faced on hang issue of
> suspend-to-ram for Exynos4 as before.
>
> Could you send .config file for test?
I am testing on exynos_defconfig with some stuff enabled (nothing
special: regulators, chargers, PM_ADVANCED_DEBUG, extcon etc.). However
sometimes I also see hangs related to MMC. But I believe this issue is
present for some time and is not related to my DELAYED_RESET_ASSERTION
changes.
Maybe you could try to boot with "no_console_suspend loglevel=7" and see
when the suspend fails?
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-02-24 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 10:45 [RESEND PATCH] ARM: EXYNOS: Fix failed second suspend on Exynos4 Krzysztof Kozlowski
2015-02-18 10:45 ` Krzysztof Kozlowski
2015-02-23 16:25 ` Bartlomiej Zolnierkiewicz
2015-02-23 16:25 ` Bartlomiej Zolnierkiewicz
2015-02-23 17:12 ` Krzysztof Kozlowski
2015-02-23 17:12 ` Krzysztof Kozlowski
2015-03-03 11:28 ` Bartlomiej Zolnierkiewicz
2015-03-03 11:28 ` Bartlomiej Zolnierkiewicz
2015-02-24 2:38 ` Chanwoo Choi
2015-02-24 2:38 ` Chanwoo Choi
2015-02-24 7:59 ` Krzysztof Kozlowski [this message]
2015-02-24 7:59 ` Krzysztof Kozlowski
2015-02-24 8:45 ` Chanwoo Choi
2015-02-24 8:45 ` Chanwoo Choi
2015-02-24 8:46 ` Chanwoo Choi
2015-02-24 8:46 ` Chanwoo Choi
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=1424764762.2877.3.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=stable@vger.kernel.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.