All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9636] New: cpufreq reports too low max freq on Intel P4
Date: Wed, 26 Dec 2007 04:34:41 -0800 (PST)	[thread overview]
Message-ID: <bug-9636-3570@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=9636

           Summary: cpufreq reports too low max freq on Intel P4
           Product: Power Management
           Version: 2.5
     KernelVersion: 2.6.23
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@www.linux.org.uk
        ReportedBy: peter.ganzhorn@googlemail.com


Most recent kernel where this bug did not occur: -
Distribution: Debian testing
Hardware Environment: Intel P4 3.0GHz HT, Intel 945 chipset
Software Environment: Debian testing
Problem Description:
Using the acpi-cpufreq driver the CPU will not switch to a frequency higher
than 1.5 GHz; the sysfs cpufreq interface (cpuinfo_max_freq) reports 1.5 GHz to
be the maximum frequency available as well.
The same kernel without cpufreq support enabled does not show those problems,
the CPU will run at 3 GHz without cpufreq.
Kernel 2.6.23 and 2.6.24-rc* both show the problem.

Here some output with cpufreq enabled:
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 
1500000
# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq 
1500000
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 
1500000 1400000

Actually it *should* report frequencies up to 3 GHz, but only does report up to
1.5 GHz.
I'm gonna attach the /proc/cpuinfo data to this bug report, let me know if you
need any other information.
This is a really, really nasty bug.

Steps to reproduce: Depends on my hardware I guess.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2007-12-26 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 12:34 bugme-daemon [this message]
2007-12-26 12:35 ` [Bug 9636] cpufreq reports too low max freq on Intel P4 bugme-daemon
2007-12-26 12:39 ` bugme-daemon
2008-01-01 18:15 ` bugme-daemon
2008-01-27 11:20 ` bugme-daemon
2008-01-27 11:21 ` bugme-daemon
2008-03-02 19:44 ` bugme-daemon

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=bug-9636-3570@http.bugzilla.kernel.org/ \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=cpufreq@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 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.