mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "S K" <nospamnoham@gmail.com>
To: "Zhao Yakui" <yakui.zhao@intel.com>
Cc: none <aj504@student.cs.york.ac.uk>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Thu, 7 Aug 2008 21:53:05 -0700	[thread overview]
Message-ID: <514e099a0808072153w2e944037gbfbdf8e9156d7df0@mail.gmail.com> (raw)
In-Reply-To: <1218159124.6671.32.camel@yakui_zhao.sh.intel.com>

Hi,

I already did the cpufreq.debug thing and it was using the
smi_speedstep driver instread of the acpi_speedstep (or whatever is
the right name).

Alan already told me this is likely an ACPI issue. So, I already sent
the acpidump in a prev email (Aug 3rd 08). I'm don't have access to my
home machine right now. Will send it again later if you can't get my
prev email from the archives.

Is lspci output needed for this?

Thanks,
SK

On 8/7/08, Zhao Yakui <yakui.zhao@intel.com> wrote:
> On Thu, 2008-08-07 at 02:35 -0700, S K wrote:
>  > Anyone care to help?
>  >
>  Will you please confirm whether the acpi_cpufreq driver is used on your
>  machine?
>  Please enable CONFIG_CPUFREQ_DEBUG in kernel configuration and boot the
>  system with "cpufreq.debug=7".
>  After the system is booted, please attach the output of dmesg.
>
>  please attach the output of acpidump using the latest pmtools at
>   http://www.lesswatts.org/patches/linux_acpi/
>
>  Of course you can open a new bug in bugzilla and attach the output of
>  dmesg, acpidump, lspci -vxxx.
>
>  http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
>
>  Thanks.
>
> > -SK
>  >
>  > 2008/8/3 S K <nospamnoham@gmail.com>:
>  > > Hi,
>  > >
>  > >  I'm attaching the acpidump output. Can someone (ACPI guys??) please
>  > > me help figure this out?
>  > > Is there any other info that's needed to debug this?
>  > >
>  > > I can be a tester for this and even do some development within the
>  > > limits of my understanding.
>  > >
>  > > Thanks,
>  > > SK
>  > >
>  > > On Sun, Aug 3, 2008 at 3:31 AM, none <aj504@student.cs.york.ac.uk> wrote:
>  > >> S K wrote:
>  > >>> Hi,
>  > >>>
>  > >>>   I have an Intel Core 2 Quad and running kernel
>  > >>> 2.6.25.11-97.fc9.i686. cpufreq doesn't seem to work. The cpufreq
>  > >>> scaling monitor in Gnome says CPU Freq scaling is not supported in my
>  > >>> CPU. The CPU can run at 2.0 and 2.5 GHz but mine always runs at 2.5
>  > >>> GHz in Linux.
>  > >>>
>  > >>> So I checked  /sys and there is no cpufreq dir in /sys/...
>  > >>>
>  > >>> # ls /sys/devices/system/cpu/
>  > >>> cpu0  cpu1  cpu2  cpu3  cpuidle  sched_mc_power_savings
>  > >>> # ls /sys/devices/system/cpu/cpuidle/
>  > >>> current_driver  current_governor_ro
>  > >>>
>  > >>> I have no clue what cpuidle directory is for.
>  > >>>
>  > >>> I added cpufreq.debug=7 in kernel boot params and saw the following in
>  > >>> the dmesg:
>  > >>>
>  > >>> speedstep-smi: No supported Intel CPU detected.
>  > >>> cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
>  > >>> cpufreq-core: CPU 3: _PPC is 0 - frequency not limited
>  > >>> cpufreq-core: CPU 1: _PPC is 0 - frequency not limited
>  > >>> cpufreq-core: CPU 2: _PPC is 0 - frequency not limited
>  > >>> cpuidle: using governor ladder
>  > >>> cpuidle: using governor menu
>  > >>>
>  > >>> I looked at arch/x86/kernel/cpu/cpufreq/speedstep-smi.c and it seems
>  > >>> to detect only Pentium IIIs.
>  > >>>
>  > >>> Anyone know what files have the cpufreq code for Intel Core 2?
>  > >>> Does cpufreq support Intel Core 2 Quads? Especially the Q9300? If not,
>  > >>> anything I can do to help?
>  > >>
>  > >> I have an Intel Core 2 Duo and it uses the ACPI cpufreq driver; your
>  > >> Quad should do the same.  So this is likely an ACPI/BIOS issue.
>  > >>
>  > >> If you ask ACPI people they will ask you to post the output of acpidump.
>  > >> Also you should probably check if you have a BIOS option that needs to be
>  > >> enabled for this to work.
>  > >>
>  > >> BTW, cpuidle is something quite different, it is about how to save power
>  > >> when CPU is doing nothing (i.e. idle :-).  Cpu frequency scaling is how to
>  > >> save power when CPU is working (but doesn't need to run flat out).
>  > >>
>  > >> Alan
>  > >>
>  > >
>
> > --
>  > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
>  > the body of a message to majordomo@vger.kernel.org
>  > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>

  reply	other threads:[~2008-08-08  4:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 10:00 S K
2008-08-03 10:31 ` none
2008-08-04  5:06   ` S K
2008-08-07  9:35     ` S K
2008-08-07 19:24       ` Alan Jenkins
2008-08-08  1:32       ` Zhao Yakui
2008-08-08  4:53         ` S K [this message]
2008-08-08  8:41           ` Alan Jenkins
2008-08-08 10:10             ` S K
2008-08-08 10:43               ` S K
2008-08-08 12:30                 ` Thomas Renninger
2008-08-08 18:23                   ` S K
2008-08-09 18:59                     ` Thomas Renninger
2008-08-09 19:30                       ` Thomas Renninger
2008-08-10  8:28                       ` S K
2008-08-11  1:33                         ` Zhao Yakui
2008-08-11  4:44                           ` S K
2008-08-11  5:24                             ` Zhao Yakui
2008-08-11  5:24                               ` S K
2008-08-11  7:00                                 ` Alan Cox
2008-08-11 10:55                               ` Andi Kleen
2008-08-11 13:15                                 ` S K
2008-08-11 13:23                                   ` Andi Kleen
2008-08-12  5:43                                     ` S K
2008-08-11 11:22                             ` Arjan van de Ven
2008-08-11 11:38                               ` Alexey Dobriyan
2008-08-11 11:53                                 ` Matthew Garrett
2008-08-11 14:02                               ` Adrian Bunk
2008-08-11 14:07                                 ` Matthew Garrett
2008-08-11 14:12                                   ` Arjan van de Ven
2008-08-11 14:11                                 ` Arjan van de Ven
2008-08-11 16:03                                   ` Adrian Bunk
2008-08-11 16:20                                     ` Arjan van de Ven
2008-08-11 16:28                                       ` Adrian Bunk
2008-08-11 16:44                                         ` Arjan van de Ven
2008-08-12 19:27                                           ` Adrian Bunk
2008-08-11 19:33                                   ` Dominik Brodowski
2008-08-11 23:58                                     ` Arjan van de Ven
2008-08-12 19:03                                       ` Dominik Brodowski
2008-08-12 19:59                                         ` Arjan van de Ven

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=514e099a0808072153w2e944037gbfbdf8e9156d7df0@mail.gmail.com \
    --to=nospamnoham@gmail.com \
    --cc=aj504@student.cs.york.ac.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yakui.zhao@intel.com \
    /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

all inboxes | Powered by JetHome®