cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Bryce as root <root@www.linux.org.uk>
Cc: cpufreq@www.linux.org.uk, Russell King <rmk@www.linux.org.uk>
Subject: Re: When exactly should I worry?
Date: Sat, 4 Sep 2004 02:54:34 +0100	[thread overview]
Message-ID: <20040904015434.GB26517@redhat.com> (raw)
In-Reply-To: <E1C3FYD-0005fc-EX@www.linux.org.uk>

On Fri, Sep 03, 2004 at 04:00:29PM +0100, Bryce as root wrote:

 > Linux ZenIV.linux.org.uk 2.6.7-1.494.2.2smp #1 SMP Tue Aug 3 09:59:49 EDT 2004 i686 i686 i386 GNU/Linux

Is this one of Alan's VIA C3 toys ?
If so, the longhaul driver was seriously horked between 2.6.5 and 2.6.9rc1.
I fixed that up a week or two ago.   If you're stuck on that
kernel for whatever reason, just kill the longhaul.ko module.

		Dave

  reply	other threads:[~2004-09-04  1:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 15:00 When exactly should I worry? Bryce as root
2004-09-04  1:54 ` Dave Jones [this message]
2004-09-04  2:05 ` Dave Jones

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=20040904015434.GB26517@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=rmk@www.linux.org.uk \
    --cc=root@www.linux.org.uk \
    /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