http://bugzilla.kernel.org/show_bug.cgi?id=13780 --- Comment #7 from Mark Langsdorf <mark.langsdorf@xxxxxxx> 2009-07-21 22:58:47 --- At a guess, the failure is occurring here (lines 1291). The oops reports the error at powernow_cpu_init+0x30d, and the math to set the transition latency that precedes this is pretty clearly at powernow_cpu_init+0x2df: /* only run on specific CPU from here on */ oldmask = current->cpus_allowed; set_cpus_allowed_ptr(current, &cpumask_of_cpu(pol->cpu)); There's a patch series already in 2.6.31 that completely redoes this logic because of potential NULL pointer issues. Could you see if you still experience the problem on 2.6.31-rc3? If you don't, that would confirm the problem and the solution in 2.6.31. I'll also try to think of a way to fix it for 2.6.30. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- 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
