[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b172d775afa24cea69a9490f531c6b37@mail.ncrmnt.org>
Date: Sun, 12 Apr 2015 18:41:31 +0300
From: Andrew <andrew@...mnt.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Russell King <linux@....linux.org.uk>,
Linus Walleij <linus.walleij@...aro.org>,
Wolfram Sang <wsa@...-dreams.de>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org,
Gregory Clement <gregory.clement@...e-electrons.com>,
Jason Cooper <jason@...edaemon.net>
Subject: Re: Fwd: Re: [PATCH 2/2] ARM: mvebu: dts: Add dts file for DLink DNS-327L
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. With cpuidle disabled I hit 50+ days of uptime with no
issue.
I have also attached the config that I used to reproduce this issue
today
on 4.0-rc7. Just in case.
Since DNS-327L has no JTAG whatsoever there's little I can do to debug
this one myself. I had a feeling though it was somehow related to power
supply: e.g. non-stock power supply 'looked like' triggered the bug more
often. But poking with oscilloscope around all the power lines didn't
show
any difference.
--
Regards,
Andrew
View attachment ".config" of type "text/plain" (94427 bytes)
Powered by blists - more mailing lists