From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dave Jones <davej@redhat.com>
Cc: Sebastian <sebastian_ml@gmx.net>,
cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: speedfreq: epia + longhaul + speedfreq + copying large files = freeze
Date: Wed, 22 Dec 2004 18:38:52 -0800 [thread overview]
Message-ID: <1103769532.16431.52.camel@localhost> (raw)
In-Reply-To: <20041222203136.GB21861@redhat.com>
On Wed, 2004-12-22 at 15:31 -0500, Dave Jones wrote:
> Yeah, longhaul is badly broken right now, and tbh, I've no idea
> what on earth is wrong. Speed transitions happen, and work correctly.
> Then a few minutes later, system locks up.
>
> 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.
Do you mean that it will crash some minutes after a single transition,
or is it less deterministic than that? Do lots of transitions make it
worse? Is the delay between transition and crash a random or
approximately fixed length, and does it depend on either core or bus
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.
J
next prev parent reply other threads:[~2004-12-23 2:38 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 [this message]
2004-12-23 18:24 ` Dave Jones
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=1103769532.16431.52.camel@localhost \
--to=jeremy@goop.org \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=sebastian_ml@gmx.net \
/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.