linux-kernel - Re: [PATCH v2] ARM: EXYNOS: Fix failed second suspend on Exynos4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <17192323.C79bdPNvX5@amdc1032>
Date:	Wed, 18 Mar 2015 11:47:51 +0100
From:	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
To:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
Cc:	Kukjin Kim <kgene@...nel.org>, Arnd Bergmann <arnd@...db.de>,
	Olof Johansson <olof@...om.net>,
	linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	stable@...r.kernel.org
Subject: Re: [PATCH v2] ARM: EXYNOS: Fix failed second suspend on Exynos4


Hi,

On Wednesday, March 18, 2015 10:47:44 AM Krzysztof Kozlowski wrote:
> On śro, 2015-03-18 at 09:57 +0100, Krzysztof Kozlowski wrote:
> > On śro, 2015-03-18 at 03:05 +0900, Kukjin Kim wrote:
> > > On 03/11/15 19:29, Krzysztof Kozlowski wrote:
> > > > On śro, 2015-03-11 at 11:20 +0100, Krzysztof Kozlowski wrote:
> > > >> On Exynos4412 boards (Trats2, Odroid U3) after enabling L2 cache in
> > > >> 56b60b8bce4a ("ARM: 8265/1: dts: exynos4: Add nodes for L2 cache
> > > >> controller") the second suspend to RAM failed. First suspend worked fine
> > > >> but the next one hang just after powering down of secondary CPUs (system
> > > >> consumed energy as it would be running but was not responsive).
> > > >>
> > > >> The issue was caused by enabling delayed reset assertion for CPU0 just
> > > >> after issuing power down of cores. This was introduced for Exynos4 in
> > > >> 13cfa6c4f7fa ("ARM: EXYNOS: Fix CPU idle clock down after CPU off").
> > > >>
> > > >> The whole behavior is not well documented but after checking with vendor
> > > >> code this should be done like this (on Exynos4):
> > > >> 1. Enable delayed reset assertion when system is running (for all CPUs).
> > > >> 2. Disable delayed reset assertion before suspending the system.
> > > >>    This can be done after powering off secondary CPUs.
> > > >> 3. Re-enable the delayed reset assertion when system is resumed.
> > > >>
> > > >> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>
> > > >> Fixes: 13cfa6c4f7fa ("ARM: EXYNOS: Fix CPU idle clock down after CPU off")
> > > >> Cc: <stable@...r.kernel.org>
> > > >> Tested-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
> > > >> Tested-by: Chanwoo Choi <cw00.choi@...sung.com>
> 
> (...)
> 
> > 
> > > 
> > > And please make sure your updates don't hurt other exynos5 stuff. Any
> > > tests on exynos5 platforms would be helpful.
> > > 
> > > And I don't think the fix should be sent to 'stable' because I can't see
> > > the 'add node for L2$ controller' in v3.19...looks applied from v4.0-rc...
> > 
> > You're right. git-describe gave me 3.19-rc1 but this was tag for the
> > specific commit, not for merge-commit. The stable can be removed if this
> > comes during this RC-cycle.
> 
> Actually the "fixes" tag is for commit introducing wrong usage of
> "use_delayed_reset_assertion" which was merged for 3.19. Although
> mentioned bug (failed second to RAM) is observable only after enabling
> L2 cache, the fix is for original commit.

IMHO "fixes" tag should be for "L2 cache" commit not for "use delayed reset
assertion" one.  Without L2 cache being enabled the delayed reset assertion
code worked fine (even though in theory it was wrong).

> I have also other proposal: what about reverting the commit 13cfa6c4f7fa
> ("ARM: EXYNOS: Fix CPU idle clock down after CPU off")? It will
> introduce minor issue (CPU idle clock down will stop to work after CPU
> hot unplug) but the main problem with suspend to RAM will be fixed.

Please don't do that.  We should not replace one regression with the
other one.  If you want to revert something it would be better to revert
the patch adding L2 cache nodes for Exynos4 SoCs for now.  However we
should not be reverting anything IMO.

The regression fix patch is simple and is working.  I would really prefer
to have it applied now (to fix suspend and cpuidle v4.0-rc1 regressions
finally and not keep code broken for months as we do now).  We can always
revisit it to something more 'perfect' later when we have more data.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/