From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fulvio Subject: Re: [PATCH] cpuidle: mvebu: Fix the CPU PM notifier usage Date: Tue, 03 Mar 2015 11:52:53 +0100 Message-ID: <54F59285.5060306@libero.it> References: <1424971248-29076-1-git-send-email-gregory.clement@free-electrons.com> <4892716.Bf612zPN6E@vostro.rjw.lan> <54F03B51.1010708@free-electrons.com> <54F58D2F.2010907@linaro.org> <54F58E3B.9040302@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54F58E3B.9040302@free-electrons.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Gregory CLEMENT Cc: Thomas Petazzoni , Andrew Lunn , Jason Cooper , Tawfik Bayouk , linux-pm@vger.kernel.org, Boris BREZILLON , Daniel Lezcano , "Rafael J. Wysocki" , Nadav Haklai , Lior Amsalem , Ezequiel Garcia , Maxime Ripard , linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth List-Id: linux-pm@vger.kernel.org Gregory CLEMENT wrote: > Hi Rafael, > > > > On 03/03/2015 11:30, Daniel Lezcano wrote: > >> On 02/27/2015 10:39 AM, Gregory CLEMENT wrote: >> >>> Hi Rafael, >>> >>> On 26/02/2015 22:55, Rafael J. Wysocki wrote: >>> >>>> On Thursday, February 26, 2015 06:20:48 PM Gregory CLEMENT wrote: >>>> >>>>> As stated in kernel/cpu_pm.c, "Platform is responsible for ensuring >>>>> that cpu_pm_enter is not called twice on the same CPU before >>>>> cpu_pm_exit is called.". In the current code in case of failure when >>>>> calling mvebu_v7_cpu_suspend, the function cpu_pm_exit() is never >>>>> called whereas cpu_pm_enter() was called just before. >>>>> >>>>> This patch moves the cpu_pm_exit() in order to balance the >>>>> cpu_pm_enter() calls. >>>>> >>>>> Reported-by: Fulvio Benini >>>>> Signed-off-by: Gregory CLEMENT >>>>> >>>> Should that go to "stable" too? Which "stable" series it should go to if so? >>>> >>> Yes as it fixes a potential issue, you're right it should go >>> to "stable". The bug was here since the introduction of the driver >>> in 3.16. >>> >> Hi Gregory, >> >> actually the 'stable' rules state clearly: >> >> "- It must fix a real bug that bothers people (not a, "This could be a >> problem..." type thing)." >> >> You say "it fixes a potential issue", so no bug has been raise yet, right ? >> > > Indeed nobody claimed yet having a bug related to this issue. > > Gregory > > I reported the issue, but i cannot say if it's a real bug. I had random kernel panics with a Netgear ReadyNAS RN102 (armada 370 cpu): http://www.readynas.com/forum/viewtopic.php?f=20&t=78697&sid=14747617286d55ac27296cdee7a3f420&start=210#p452214 All i can say is that the system use the "armadaxp_idle" driver and works fine when running "stress --cpu 8" in background. I asked Netgear to provide a firmware without the idle driver to confirm if it's the cause of the problem, but they did not answered. Bye, Fulvio