Re: 2.6.33-rc6 - BUG at drivers/cpufreq/cpufreq.c:88

[Thomas Renninger]

On Thursday 04 February 2010 17:00:02 Valdis.Kletnieks@xxxxxx 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@xxxxxxx>
> 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?

      Thomas


PS: I checked by:
> cat .git/FETCH_HEAD
fc76be434d90bcd57a0ea6b93a2e66a3fec4b664                branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
> git pull
Already up-to-date.
> git branch
* master
> git show 46aeb7430f79cb4d03e17fedd6399884ab3aa697
fatal: bad object 46aeb7430f79cb4d03e17fedd6399884ab3aa697
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/