From: Dave Jones <davej@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: speedfreq: epia + longhaul + speedfreq + copying large files = freeze
Date: Thu, 23 Dec 2004 13:24:24 -0500 [thread overview]
Message-ID: <20041223182424.GA32326@redhat.com> (raw)
In-Reply-To: <1103769532.16431.52.camel@localhost>
On Wed, Dec 22, 2004 at 06:38:52PM -0800, Jeremy Fitzhardinge wrote:
> > I've been trying all sorts of things, from disabling PCI mastering,
> > disabling CPU caches, etc, but nothing seems to help. I'm truly puzzled.
>
> I remember old versions of the C3 used to forget to snoop DMA traffic
> while in the hlt instruction, so it wouldn't surprise me if there's some
> other bug like that related to longhaul.
That's why I was hoping disablign mastering would do the trick.
> Do you mean that it will crash some minutes after a single transition,
> or is it less deterministic than that?
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.
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)
> The reason I ask is that I have the ear of Via engineering support at
> the moment (we're using embedded C3's in a product at work), so I could
> ask a few well-placed questions.
I speak with the centaur folks regularly, but they haven't got any
ideas what the problem could be either.
Dave
next prev parent reply other threads:[~2004-12-23 18:24 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 [this message]
2004-12-23 20:05 ` Jeremy Fitzhardinge
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=20041223182424.GA32326@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=jeremy@goop.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 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.