From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9475] New: jiffies counter leaps on CPU frequency changes
Date: Thu, 29 Nov 2007 08:36:24 -0800 (PST) [thread overview]
Message-ID: <bug-9475-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=9475
Summary: jiffies counter leaps on CPU frequency changes
Product: Power Management
Version: 2.5
KernelVersion: 2.6.24-rc3
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: stefano.brivio@polimi.it
Most recent kernel where this bug did not occur: unknown. I'm sorry, I can't
test 2.6.23 because of some dm-crypt issue.
Distribution: Gentoo.
Hardware Environment:
st3@morte ~ $ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.50GHz
stepping : 6
cpu MHz : 1500.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov pat
clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts est tm2
bogomips : 2993.49
clflush size : 64
Software environment: acpi-cpufreq module.
Problem Description:
when I switch the CPU frequency, the jiffies counter gets scaled by the ratio
of <old_frequency/new_frequency>, e.g.:
morte ~ # cpuspeedy max
cpuspeedy: CPU speed is now 1.50 GHz (100%) temperature is 55 C
morte ~ # tail -n1 /var/log/messages
[10609.463888] wmaster0: STA 00:14:c1:35:8d:eb Average rate: 10 (50/5)
morte ~ # cpuspeedy med
cpuspeedy: CPU speed is now 1 GHz (66%) temperature is 72 C
[15996.701445] wmaster0: STA 00:14:c1:35:8d:eb Average rate: 10 (60/6)
This isn't just an aesthetic issue, as many device drivers rely on the jiffies
counter.
Steps to reproduce:
see above.
--
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-11-29 16:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 16:36 bugme-daemon [this message]
2007-12-01 20:35 ` [Bug 9475] jiffies counter leaps on CPU frequency changes bugme-daemon
2007-12-01 20:35 ` bugme-daemon
2007-12-01 21:10 ` bugme-daemon
2007-12-04 21:12 ` bugme-daemon
2007-12-04 21:14 ` bugme-daemon
2007-12-04 21:28 ` bugme-daemon
2007-12-04 21:47 ` bugme-daemon
2007-12-04 22:04 ` bugme-daemon
2007-12-04 22:09 ` bugme-daemon
2007-12-04 22:25 ` bugme-daemon
2007-12-05 19:28 ` bugme-daemon
2007-12-05 19:38 ` bugme-daemon
2007-12-05 20:43 ` bugme-daemon
2007-12-07 1:26 ` bugme-daemon
2007-12-07 4:32 ` bugme-daemon
2007-12-07 5:16 ` bugme-daemon
2007-12-07 15:37 ` bugme-daemon
2007-12-08 1:40 ` bugme-daemon
2007-12-19 0:59 ` bugme-daemon
2007-12-19 13:46 ` 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-9475-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