From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 8720] New: still problems with k7 mobile frequency is lower than real
Date: Fri, 6 Jul 2007 10:18:20 -0700 (PDT) [thread overview]
Message-ID: <bug-8720-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=8720
Summary: still problems with k7 mobile frequency is lower than
real
Product: Power Management
Version: 2.5
KernelVersion: 2.6.22-rc5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: cimmo@libero.it
CC: dsd@gentoo.org
Most recent kernel where this bug did not occur: don't know
Distribution: Kubuntu 7.04 and 7.10 Tribe2
Hardware Environment: Athlon XP-M 2400+
Problem Description: This cpu has 1800 Mhz and is detected well during early
startup but after by powernowdas 1473 Mhz, the last fix in bug #8255 didn't
solve the problem for me, before and after that patch is the same.
I tried also Kubuntu 7.10 Tribe 2 that has a 2.6.22rc5 custom according to
https://lists.ubuntu.com/archives/gutsy-changes/2007-June/003601.html
I personally verified that has the patch posted in bug #8255 and it has, but
same bug.
from dmesg attacched:
[ 0.000000] Detected 1807.794 MHz processor.
[ 118.852989] powernow: PowerNOW! Technology present. Can scale: frequency and
voltage.
[ 118.862515] powernow: Trying ACPI perflib
[ 118.864625] powernow: Minimum speed 1473 MHz. Maximum speed 1473 MHz.
The processor has the Barton core with 512 KB of cache
--
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.
next reply other threads:[~2007-07-06 17:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 17:18 bugme-daemon [this message]
2007-07-06 17:19 ` [Bug 8720] still problems with k7 mobile frequency is lower than real bugme-daemon
2007-07-06 23:57 ` bugme-daemon
2007-07-09 17:50 ` bugme-daemon
2007-07-23 0:08 ` bugme-daemon
2007-07-23 0:09 ` bugme-daemon
2007-07-28 14:40 ` bugme-daemon
2007-07-28 14:42 ` bugme-daemon
2007-07-28 14:43 ` bugme-daemon
2007-07-30 2:50 ` bugme-daemon
2007-07-30 18:21 ` bugme-daemon
2007-07-30 18:53 ` bugme-daemon
2007-07-30 22:46 ` bugme-daemon
2007-08-01 19:48 ` bugme-daemon
2007-08-01 19:50 ` bugme-daemon
2007-09-01 12:41 ` bugme-daemon
2007-09-01 12:41 ` bugme-daemon
2007-09-01 12:43 ` bugme-daemon
2007-09-01 12:46 ` bugme-daemon
2007-09-01 14:34 ` bugme-daemon
2007-09-01 15:21 ` bugme-daemon
2007-09-06 14:33 ` bugme-daemon
2007-09-06 14:46 ` bugme-daemon
2007-09-23 9:35 ` bugme-daemon
2007-09-23 11:19 ` bugme-daemon
2007-09-30 15:07 ` 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-8720-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.