linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut.n900@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: PXA27x: CPUFREQ: Don't use fastbus mode
Date: Tue, 12 Apr 2011 07:22:26 +0200	[thread overview]
Message-ID: <1302585746.6862.2.camel@konomi> (raw)
In-Reply-To: <201104112311.01002.anarsoul@gmail.com>

> On Monday 11 April 2011 16:46:43 Pavel Machek wrote:
> > Hi!
> > 
> > Well, some other pxa27x machcines?  (spitz) are crashing randomly for
> > _years_ now... so maybe the problem is more widespread?
> > 
> > How easy is to trigger the problem? Do you have script?
> > 
> > Is it possible that this bug triggers with governor==performance.
> 
> It's hard to trigger it with performance governor (because it's quite
> stable?  @416mhz even with fastbus), so I suggest trying ondemand or
> conservative?  governors.

Iirc ondemand crashes it easily, yes.

      reply	other threads:[~2011-04-12  5:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 19:51 [PATCH RFC] ARM: PXA27x: CPUFREQ: Don't use fastbus mode Vasily Khoruzhick
2011-03-27  0:52 ` Marek Vasut
2011-03-27  7:28   ` Vasily Khoruzhick
2011-03-27  9:09     ` Igor Grinberg
2011-03-27  9:48       ` Vasily Khoruzhick
2011-03-27 10:09         ` Igor Grinberg
2011-03-27 14:45           ` Vasily Khoruzhick
2011-03-27 14:50             ` Marek Vasut
2011-03-27 14:56               ` Vasily Khoruzhick
2011-03-27 15:34                 ` Marek Vasut
2011-03-27 16:56                   ` Robert Jarzmik
2011-03-27 17:13                     ` Vasily Khoruzhick
2011-03-28  8:22                       ` Igor Grinberg
2011-04-11 13:46       ` Pavel Machek
2011-04-11 20:11         ` Vasily Khoruzhick
2011-04-12  5:22           ` Marek Vasut [this message]

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=1302585746.6862.2.camel@konomi \
    --to=marek.vasut.n900@gmail.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).