From: Dave Jones <davej@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
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 15:31:36 -0500 [thread overview]
Message-ID: <20041222203136.GB21861@redhat.com> (raw)
In-Reply-To: <1103742159.16413.24.camel@localhost>
On Wed, Dec 22, 2004 at 11:02:39AM -0800, Jeremy Fitzhardinge wrote:
> On Tue, 2004-12-21 at 16:00 +0100, Sebastian wrote:
> > Dear Jeremy,
> >
> > thanks for your tool! I like it best of all cpufreq daemons,
>
> Thanks!
>
> This problem sounds like a bug in the longhaul driver though, which I
> don't really know anything about. (The system should never crash,
> regardless of what speedfreqd does.)
>
> I've cc:d the cpufreq list to see if someone there can help. Dave?
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.
Dave
next prev parent reply other threads:[~2004-12-22 20:31 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 [this message]
2004-12-23 2:38 ` Jeremy Fitzhardinge
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=20041222203136.GB21861@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=jeremy@goop.org \
--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.