On Fri, 05 Feb 2010 10:26:32 +0100, Thomas Renninger said:
> On Thursday 04 February 2010 17:00:02 Valdis.Kletnieks@vt.edu wrote:
> > Hit this one again while setting up to bisect another issue.  I've verified
> > that the fix *is* someplace in 2.6.33-rc6-mmotm0201 (as that one lives at least
> > all the way to single-user mode), so I'm basically asking that somebody find
> > the commit that fixes it and make sure it gets into 2.6.33-final.  I'd offer
> > the commit number for the fix, but I'm hoping somebody recognizes it and pushes
> > it so I don't have bisect to find the fixing commit.
> > 
> > Thomas?  Did you have a fix for this that hasn't been pulled by Linus yet?
> The fix is to remove the patch.
> 
> > Refresher:  The bad commit was:
> > 
> > commit 46aeb7430f79cb4d03e17fedd6399884ab3aa697
> > Author: Thomas Renninger <trenn@suse.de>
> > Date:   Mon Dec 14 11:44:11 2009 +0100
> > 
> >     [CPUFREQ] Fix race in cpufreq_update_policy()
> This one never hit Linus tree?
> It was in -mm, but got reverted.
> 
> Did you bisect on another tree?

Good catch, Thomas.

Looks like a miscue on my part - although the timestamp on the vmlinuz in /boot
matched the one in arch/x86/boot/bzImage, the file size matched  the one left
at the end of that bisect from last time.  Looks like I managed to cd into the
wrong /usr/src/linux-* when I copied the bzImage to /boot.

"D'Oh!" - H. Simpson.

Sorry for the inconvenience.