From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9475] jiffies counter leaps on CPU frequency changes
Date: Tue, 4 Dec 2007 14:04:20 -0800 (PST) [thread overview]
Message-ID: <20071204220420.1F146108010@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-9475-3570@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=9475
------- Comment #5 from stefano.brivio@polimi.it 2007-12-04 14:04 -------
(In reply to comment #4)
> hm, maybe i'm missing something obvious, but adjust_jiffies() seems to
> fix up loops_per_jiffy, not the jiffies variable. The bugreport included
> a /var/log/messages snippets that showed printk timestamps - the printk
> timestamps are directly derived from the 'jiffies' variable. Those
> timestamps jumped back and forth according to CPU frequency. So
> _something_ does seem to affect the jiffies variable - and it's not
> adjust_jiffies(). Or at least so i think.
Yes, I'm wondering about this as well. But so far, I hadn't been able to find
out where in the kernel a CPU frequency switch could trigger a sudden change to
the jiffies counter. The only related thing I observed is that adjust_jiffies()
is called, but that doesn't seem to be the culprit.
BTW, I just sorted out the dm-crypt issue which prevented me to test 2.6.23.
Will let you know ASAP about further tests.
--
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 prev parent reply other threads:[~2007-12-04 22:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 16:36 [Bug 9475] New: jiffies counter leaps on CPU frequency changes bugme-daemon
2007-12-01 20:35 ` [Bug 9475] " 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 [this message]
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=20071204220420.1F146108010@picon.linux-foundation.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.