linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: CPUIdle Armada 370
Date: Wed, 06 Aug 2014 17:43:38 +0200	[thread overview]
Message-ID: <53E24D2A.50706@free-electrons.com> (raw)
In-Reply-To: <53E249A1.900@free-electrons.com>

Hi Nicolas,

[..]

>> On 06/08/2014 16:01, Nicolas Derouineau wrote:
>>> Hello,
>>> I am currently trying to use the CPUIdle driver provided by linux-next (or by the patch here https://github.com/MISL-EBU-System-SW/mainline-public/commits/3.16/cpuidle-v3). 
>>
>> I have just tested using next-20140806 and mvebu_v7_defconfig.
>> And it worked well on a mirabox using the Armada 370 SoC.
>>
>>>
>>> Everything runs fine as long as I don't select the CPU driver for the ARMADA Family. When I do, at boottime, the program is entering the __cpu_suspend save function and then get lost in it and that turns into a kernel panic. I have already made a post about this on the ARM Community Forum (http://community.arm.com/thread/6326).
>>>
>>> The "faulty" configuration file is attached to this email.
>>
>> Now I will try with this configuration
> 
> Using your configuration file I didn't reproduce your issue.
> And according to the stat given by linux the kernel spent a lot
> of time in idle:
> 
> cat /sys/devices/system/cpu/cpu0/cpuidle/state1/time
> 338822284
> 
> 
> Could you try again with next-20140806?

Also could you send your full boot log until the crash
it may help us.

Thanks,

Gregory

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2014-08-06 15:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 14:01 CPUIdle Armada 370 Nicolas Derouineau
2014-08-06 14:34 ` Andrew Lunn
2014-08-06 15:14 ` Gregory CLEMENT
2014-08-06 15:28   ` Gregory CLEMENT
2014-08-06 15:43     ` Gregory CLEMENT [this message]
2014-08-06 16:01       ` Nicolas Derouineau
2014-08-06 16:10         ` Gregory CLEMENT
2014-08-06 16:16           ` Nicolas Derouineau
2014-08-07  8:28             ` Nicolas Derouineau
2014-08-07  9:30             ` Gregory CLEMENT
2014-08-07 13:21               ` Andrew Lunn
2014-08-07 14:44                 ` Simon Boulay
2014-08-29 12:33                   ` Nicolas Derouineau
2014-08-29 12:39                     ` Gregory CLEMENT

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=53E24D2A.50706@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).