Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754572AbbDTPQA (ORCPT ); Mon, 20 Apr 2015 11:16:00 -0400 Received: from forward8l.mail.yandex.net ([84.201.143.141]:51519 "EHLO forward8l.mail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750765AbbDTPP4 (ORCPT ); Mon, 20 Apr 2015 11:15:56 -0400 To: Gregory CLEMENT Subject: Re: Fwd: Re: [PATCH 2/2] ARM: mvebu: dts: Add dts file for DLink DNS-327L X-PHP-Originating-Script: 501:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 20 Apr 2015 18:15:46 +0300 From: Andrew Cc: Andrew Lunn , Sebastian Hesselbarth , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Linus Walleij , Wolfram Sang , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, Jason Cooper In-Reply-To: <55351569.7000307@free-electrons.com> References: <552A6209.9040903@gmail.com> <20150412145857.GA14038@lunn.ch> <20150412194735.GA27921@lunn.ch> <552BCFAA.2020109@free-electrons.com> <1ec8906f00468ca5a9fa227f8c83fe69@mail.ncrmnt.org> <55351569.7000307@free-electrons.com> Message-ID: User-Agent: Roundcube Webmail/1.0.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3099 Lines: 107 Gregory CLEMENT писал 20.04.2015 18:04: > Hi Andrew, > > On 13/04/2015 16:32, Andrew wrote: >> Gregory CLEMENT писал 13.04.2015 17:16: >>> Hi Andrew(s), >>> >>> On 12/04/2015 21:47, Andrew Lunn wrote: >>>> On Sun, Apr 12, 2015 at 06:41:31PM +0300, Andrew wrote: >>>>> Andrew Lunn ?????????? 12.04.2015 17:58: >>>>>>> Okay, got it. >>>>>>> I'll file a bug about this issue to the the bugzilla. However >>>>>>> something >>>>>>> tells me it might not be cpuidle, but D-link. This one's sounds >>>>>>> nasty >>>>>>> and it has been around since 3.16.x. How could it go unnoticed? >>>>>>> Unfortunately I have no other armada-370 hardware to test it. >>>>>> >>>>>> Hi Andrew >>>>>> >>>>>> A few of us here do have hardware to test with. Please give a >>>>>> detailed >>>>>> description of how you reproduce the issue, and your kernel >>>>>> configuration, if different from mvebu_v7_defconfig, or >>>>>> multi_v7_defconfig. >>>>>> >>>>>> Thanks >>>>>> Andrew >>>>> >>>>> >>>>> arch/arm/configs/mvebu_v7_defconfig has >>>>> CONFIG_ARM_MVEBU_V7_CPUIDLE=y, >>>>> so it should be sufficient to reproduce the issue. I first >>>>> encountered >>>>> this issue using that very config and observed it on 2 DNS-327L >>>>> boxes >>>>> I >>>>> own. >>>>> >>>>> All I have to do to trigger the bug - enable cpuidle driver and let >>>>> the box >>>>> sit for some 4-12 hours, till it hard-freezes. If wdt is enabled - >>>>> wdt reboot >>>>> will happen. >>>> >>>> That simple! Well i've got a 370RD which has been sat mostly idle >>>> for >>>> weeks, using the mvebu_v7_defconfig, with a few addition things >>>> turned >>>> on for testing the Ethernet switch on the board. I've not had that >>>> lockup. >>>> >>>> One thing you can try to narrow it down is the disable the second >>>> idle >>>> mode. Take a look at armada370_idle_driver. Keep the >>>> ARM_CPUIDLE_WFI_STATE but disable the "Deep Idle" state. >>> >>> Actually you don't have to modify the kernel you can setup the CPU >>> idle >>> level >>> you want at runtime: >>> >>> echo 1 > /sys/devices/system/cpu/cpu0/cpuidle/state1/disable >>> >>> will disable the state1. By doing this on Armada 370 then you >>> will only use the WFI state. >>> >>> Do you still have this issue on v4.0-rc7? >> >> Yep, I can confirm having this issue on 4.0-rc7. I will only be able >> to >> test if >> disabling state1 fixes it the next weekend. > > Did you manage to do some test this week-end? > > Thanks, > > Gregory > > >> >>> >>> Thanks, >>> >>> Gregory >>> >>> >>> >>>> >>>> Andrew >>>> >> Sorry, I've been away for the weekend but managed to take the hardware home on my way back. I'll rig it for a long test today in the evening. Expect some test results somewhere around Wednesday. (Guess it doesn't count unless it's stable for 24+ hours). -- Regards, Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/