All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: speedfreq: epia + longhaul + speedfreq + copying large files = freeze
Date: Thu, 23 Dec 2004 12:05:03 -0800	[thread overview]
Message-ID: <1103832303.16431.60.camel@localhost> (raw)
In-Reply-To: <20041223182424.GA32326@redhat.com>

On Thu, 2004-12-23 at 13:24 -0500, Dave Jones wrote:
> Usually takes a few. I've noticed if I run cpuspeed, it steps it down
> from 1.2GHz to 500MHz through a half dozen or so steps. Whilst it does
> this, its stable. If I then kill cpuspeed, its stable.
> But, if I leave cpuspeed run, and then do something CPU intensive, it
> tries to jump up to fullspeed quickly (through less steps than
> it took to scale down), when it does this, it hangs shortly afterwards.

Sebastian is reporting the problem with speedfreqd, which will use the
same number of steps both ways (and, depending on the CPU load curve, at
the same rate).

Does rate-limiting the transitions help stability?

> We're not doing voltage scaling in longhaul yet, but that shouldn't
> matter, as we should be booting at max voltage (as we boot at max speed)

Is voltage switching complex?  It might be worth trying - its not
something which normally improves stability, but maybe there's some
regulator issue under load changes, or something...

	J

  reply	other threads:[~2004-12-23 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41C83AA7.6010204@gmx.net>
2004-12-22 19:02 ` speedfreq: epia + longhaul + speedfreq + copying large files = freeze Jeremy Fitzhardinge
2004-12-22 20:31   ` Dave Jones
2004-12-23  2:38     ` Jeremy Fitzhardinge
2004-12-23 18:24       ` Dave Jones
2004-12-23 20:05         ` Jeremy Fitzhardinge [this message]
2004-12-23 23:33           ` Dave Jones
2004-12-23 11:15     ` Sebastian
2004-12-23 13:17 Sebastian

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=1103832303.16431.60.camel@localhost \
    --to=jeremy@goop.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.