On Saturday 18 March 2006 19:53, Andrew Morton wrote:
> I might stick a once-off WARN_ON() in there so someone gets in
> and works out why we keep on having to graft mysterious null-pointer
> avoidances into cpufreq.
cpufreq_conservative should be marked broken on SMP - I have used it on UP
boxes without trouble but I can't even safely modprobe it on SMP - it nearly
ate my filesystem.
And there seem to be multiple different problems with it - I get different
oopses depending upon whether or not I have loaded it before or after the
ondemand module. Weird enough - cpufreq_conservative shares much of it's
code with cpufreq_ondemand, which works without any problem.
Let me know if anyone has objection to marking cpufreq_conservative
depends !SMP - I am planning to submit a patch soon.
Parag
-
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]
