All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 56101] New: Intel Core2 Duo E6600 reports max-frequency of just 900 MHz instead of 2.4 GHz
Date: Tue,  2 Apr 2013 09:41:19 +0000 (UTC)	[thread overview]
Message-ID: <bug-56101-12968@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=56101

           Summary: Intel Core2 Duo E6600 reports max-frequency of just
                    900 MHz instead of 2.4 GHz
           Product: Power Management
           Version: 2.5
    Kernel Version: 3.8.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@vger.kernel.org
        ReportedBy: spam@kernelspace.de
                CC: trenn@suse.de
        Regression: No


Created an attachment (id=96971)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=96971)
Output of dmesg

I discovered that my IBM Intellistation M Pro 9229Y with its Intel
Core2 Duo E6600 is reported to clock only at a max frequency of 900.000
MHz instead of 2.4 GHz.

cpufreq-info only lists 600 and 900 MHz as hardware-supported frequencies.

The BIOS is at the latest version 1.35A, there have been no updates since 2008
(this being a rather outdated IBM workstation...)

Please see the attached output of dmesg, cpufreq-info, /proc/cpuinfo and
dmidecode for further information.

Thanks in advance

Simon

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

             reply	other threads:[~2013-04-02  9:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02  9:41 bugzilla-daemon [this message]
2013-04-02  9:41 ` [Bug 56101] Intel Core2 Duo E6600 reports max-frequency of just 900 MHz instead of 2.4 GHz bugzilla-daemon
2013-04-02  9:42 ` bugzilla-daemon
2013-04-02  9:42 ` bugzilla-daemon
2013-04-02 10:09 ` bugzilla-daemon
2013-04-02 10:18 ` bugzilla-daemon
2013-04-02 10:20 ` bugzilla-daemon
2013-04-05 12:54 ` bugzilla-daemon
2013-04-05 13:45 ` bugzilla-daemon
2013-04-05 14:09 ` bugzilla-daemon
2013-04-05 14:10 ` bugzilla-daemon
2013-04-05 14:14 ` bugzilla-daemon
2013-04-05 14:23 ` bugzilla-daemon
2013-04-05 14:48 ` bugzilla-daemon
2013-04-05 15:17 ` bugzilla-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-56101-12968@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.kernel.org \
    /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.