cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10144] New: Wrong cpufreq speeds detected when overclocking (speeds reported using stock FSB, not overclocked)
Date: Sun,  2 Mar 2008 07:41:34 -0800 (PST)	[thread overview]
Message-ID: <bug-10144-3570@http.bugzilla.kernel.org/> (raw)

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

           Summary: Wrong cpufreq speeds detected when overclocking (speeds
                    reported using stock FSB, not overclocked)
           Product: Power Management
           Version: 2.5
     KernelVersion: 2.6.22.17-0.1-default
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@www.linux.org.uk
        ReportedBy: knuckles@gmail.com


Latest working kernel version: Don't know
Earliest failing kernel version: Don't know
Distribution: openSUSE, Ubuntu
Hardware Environment: ASUS P5K (latest bios: 0902), Intel E2180, 2GB Ram
Software Environment: Normal opensuse install
Problem Description:

The E2180 is spec'd to work with 200Mhz front side bus, and has 6x thru 10x
multipliers, so, with speedstep, it should go from 1.2ghz to 2.0ghz, and that
happens fine.

The problem is, I overclocked the frontside bus to 313Mhz, (and still have
speedstep enabled), so speeds should be between 1.88ghz and 3.13ghz, but the
problem is cpufreq still reports the "available" speeds as being between 1.2
and 2.0ghz. I think this is only visual, since when booting the kernel says
"Detected 3130.093 MHz processor.", but after booting, /proc/cpuinfo and other
places all assume the aforementioned speeds.

I've also tested, and this still happens on Ubuntu Herdy alpha 5 that uses
2.6.24.2, so this should be distro-unrelated.

Steps to reproduce:
Overclock the FSB, and check reported cpufreq speeds.


-- 
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:[~2008-03-02 15:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 15:41 bugme-daemon [this message]
2008-03-02 15:43 ` [Bug 10144] Wrong cpufreq speeds detected when overclocking (speeds reported using stock FSB, not overclocked) bugme-daemon
2008-03-02 15:44 ` bugme-daemon
2008-03-02 15:46 ` bugme-daemon
2008-03-02 15:49 ` bugme-daemon
2008-03-02 19:52 ` bugme-daemon
2008-03-02 23:17 ` bugme-daemon
2008-03-02 23:20 ` bugme-daemon
2008-03-02 23:20 ` bugme-daemon
2008-03-03  6:30 ` bugme-daemon
2008-03-03 11:37 ` bugme-daemon
2008-03-03 15:03 ` bugme-daemon
2008-03-03 15:07 ` bugme-daemon
2008-05-28 13:20 ` bugme-daemon
2008-05-28 18:26 ` 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-10144-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).