Most recent kernel where this bug did not occur: 2.6.12-rc5 Distribution: Ubuntu 5.10 Hardware Environment: Dell Latitude D600 laptop Pentium-M 1.6 GHz 1 GB RAM Software Environment: Default Ubuntu environment, except for stock kernel Problem Description: A while (could be minutes, hours, days) after I boot my laptop, the speedstep control stops working correctly. I usually set the governor to ondemand, but after a while, the speed gets stuck to 600 MHz (instead of 1.6 GHz) and does not increase when necessary. Even if I then switch to "performance", the speed stays at 600 MHz. Both /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq and /proc/cpuinfo indicate 600 MHz, although the gnome cpufreq applet indicates (wrongly) 1.6 GHz. Steps to reproduce: Boot my machine, set policy to "ondemand", wait for a while. I indicated 2.6.12-rc5 as the last kernel where cpufreq worked. While I haven't done much testing for that (it's an intermittent problem), this version corresponds to the last time the kernel worked properly with my laptop. Since 2.6.12-rc6, I've been having the problems described in bugs 6166 and 6266.
Is this problem stll present in kernel 2.6.16.2?
Someone asked me whether the patches are save for backporting to a stable kernel. Not sure whether this had happened. Be sure all 4 patches (stated in bug #6331) get added. I fixed that on a DELL 600. I am quite sure this also fixes other DELL models(DELL 660 - this one, bug #6266 and bug #6166, Dell inspiron 9300 - bug #6331, Dell Latitude D800 - bug #6376). See bug #6331 for further description. I can't mark the bugs as a duplicates, so I will close them all with a note to verify the fix for recent kernels.
Ok, I need to assign it to set it as a duplicate ... *** This bug has been marked as a duplicate of 6331 ***