From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Andrew Lunn <andrew@lunn.ch>, Andrew <andrew@ncrmnt.org>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Linus Walleij <linus.walleij@linaro.org>,
Wolfram Sang <wsa@the-dreams.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: Fwd: Re: [PATCH 2/2] ARM: mvebu: dts: Add dts file for DLink DNS-327L
Date: Mon, 13 Apr 2015 16:16:10 +0200 [thread overview]
Message-ID: <552BCFAA.2020109@free-electrons.com> (raw)
In-Reply-To: <20150412194735.GA27921@lunn.ch>
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?
Thanks,
Gregory
>
> Andrew
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-04-13 14:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 11:43 Fwd: Re: [PATCH 2/2] ARM: mvebu: dts: Add dts file for DLink DNS-327L Andrew
2015-04-12 12:16 ` Sebastian Hesselbarth
2015-04-12 13:02 ` Andrew
2015-04-12 14:58 ` Andrew Lunn
[not found] ` <20150412145857.GA14038-g2DYL2Zd6BY@public.gmane.org>
2015-04-12 15:41 ` Andrew
[not found] ` <b172d775afa24cea69a9490f531c6b37-IcawJbj+vY1vZ+LtbKW8tg@public.gmane.org>
2015-04-12 19:47 ` Andrew Lunn
2015-04-13 14:16 ` Gregory CLEMENT [this message]
2015-04-13 14:32 ` Andrew
[not found] ` <1ec8906f00468ca5a9fa227f8c83fe69-IcawJbj+vY1vZ+LtbKW8tg@public.gmane.org>
2015-04-20 15:04 ` Gregory CLEMENT
2015-04-20 15:15 ` Andrew
2015-04-20 15:17 ` Gregory CLEMENT
2015-05-03 10:18 ` Andrew
2015-05-03 10:58 ` Sebastian Hesselbarth
2015-05-03 11:37 ` Andrew
2015-05-06 12:13 ` Gregory CLEMENT
2015-05-06 13:39 ` Andrew
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=552BCFAA.2020109@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=andrew@ncrmnt.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=wsa@the-dreams.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).