On 03/30/10 22:49, Dave Jones wrote:
On Fri, Mar 26, 2010 at 08:34:15AM +0100, Jes Sorensen wrote: > On 03/25/10 16:45, Dave Jones wrote: > > On Thu, Mar 25, 2010 at 04:06:45PM +0100, Jes Sorensen wrote: > > > Hi Dave, > > > > > > I get this one regularly when I boot my test box which is running the > > > current F13 beta. > > > > > > Not sure if you have already seen it, in which case feel free to just > > > ignore this. > > > > New one to me, and nothing queued for .34 that could fix it. > > I'll poke at it later. Ugh, cpufreq vs sysfs locking is always a mess. > > Ok, it seems pretty easy for me to regenerate this, so if you need > access to the box, just let me know. I just merged this patch that I had forgotten about into my 'for .34' tree, which should fix this. Dave
Looks promising! I'll watch for an F13 kernel update and see if it still happens! Thanks! Jes -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
