From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9475] jiffies counter leaps on CPU frequency changes
Date: Wed, 5 Dec 2007 12:43:59 -0800 (PST) [thread overview]
Message-ID: <20071205204359.4721911D108@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 #10 from mingo@elte.hu 2007-12-05 12:43 -------
> I just managed to boot 2.6.23. Nothing changes. Do you want me to
> bisect some specific tree?
nothing changes == same problem?
If yes then please try to find the oldest kernel that still works fine.
2.6.20 would be a good pick i think, 2.6.16 after that. Then if you
could try to bisect between the youngest "good" and the oldest "bad"
tree that would be fantastic ... Expect a compile-fest though.
--
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-05 20:43 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
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 [this message]
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=20071205204359.4721911D108@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox