On Sun, Jul 09, 2006 at 08:55:02AM +1000, Jean-Marc Valin wrote:
> > If you're prepared to play around with 'git bisect' a little, it shouldn't
> > take that many iterations, as you've already narrowed it down quite a lot.
> >
> > $ git bisect start drivers/cpufreq/cpufreq_ondemand.c
> > $ git bisect bad
> > $ git bisect good v2.6.12-rc5
> >
> > should get you most of the way there.
> >
> > http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
> > has more info.
>
> Could you give me a bit more info, since I've never used git before (I
> only downloaded the git snapshots)? Also, if I understand correctly,
> cpufreq_ondemand.c is the only file that could cause the problem. Is
> that right? Also, is it possible to use an old version of it on a new
> kernel?
Actually, before deep diving into chasing bugs in ondemand, we should
probably confirm that the same behaviour doesn't happen with a different
governor. Can you try that ? Try setting it to userspace, and then
running a userspace app like cpuspeed/powernowd etc.
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
