From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: ACPI P-States vs Longhaul
Date: Mon, 20 Nov 2006 14:59:12 -0500 [thread overview]
Message-ID: <20061120195912.GC27924@redhat.com> (raw)
In-Reply-To: <456203F5.60606@interia.pl>
On Mon, Nov 20, 2006 at 08:37:25PM +0100, Rafał Bilski wrote:
> Hello,
>
> I know that a lot has changed since 2.6.18 in "ACPI P-States"
> driver, but I wasn't paing attention. Just in case if this
> issue isn't known. Reported by user.
> System: VIA Epia SP13000 (VIA C3-2 "Nehemiah" 6.9.8)
> Kernel: 2.6.18.2 custom config, apci-cpufreq=m, longhaul=m
> Issue:
> "ACPI P-States driver" is loaded (by distro) and stays loaded.
> When user try to load "Longhaul" CPU is already owned by other
> driver and "Longhaul" fails with -EBUSY. Of course rmmod does
> the trick. But why acpi-cpufreq didn't failed? This processor
> don't support P-states.
> Sadly "Longhaul" don't work too. No ACPI C3 support in BIOS
> and CN400 chipset on mainboard.
Probably due to the 'sticky' bug that was fixed in 2.6.18.3
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-11-20 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 19:37 ACPI P-States vs Longhaul Rafał Bilski
2006-11-20 19:59 ` Dave Jones [this message]
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=20061120195912.GC27924@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=rafalbilski@interia.pl \
/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.