https://bugzilla.kernel.org/show_bug.cgi?id=23412 Thomas Renninger <trenn@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P5 Severity|normal |enhancement --- Comment #7 from Thomas Renninger <trenn@xxxxxxx> 2010-12-20 09:20:27 --- > I have found a BIOS feature "Andvanced power management" Sounds related. > I don't really know what is this feature for Yep, finding out why the BIOS sets the frequency limit can be cumbersome. Still, it's not a kernel, but a BIOS/platform issue. As said, all initial BIOS limits were ignored by the kernel for quite some time and this got fixed. Have you looked for BIOS updates and their changelogs already? If not, this would be the next step. If this also does not help, please attach acpidump output (with the new BIOS!). Be aware that this is very low prio bug, as it's very likely that the culprit (most likely this is even intended) comes from the BIOS. --- Comment #8 from Vladimir <v_2e@xxxxxxx> 2010-12-20 09:46:30 --- (In reply to comment #7) > > I have found a BIOS feature "Andvanced power management" > Sounds related. Well, I thik so too, but I tried to switch this option on/off several times, and naven't noticed any changes in anything. This feature is also not documented in the User's Manual for my laptop. > Still, it's not a kernel, but a BIOS/platform issue. Yes. Now I'm sure this isn't a kernel issue. I tried to add the "processor.ignore_ppc=1" string to the kernel parameters at startup, just like you suggested, and it really gave me access for all the CPU frequencies, which is just great! Thank you for this tip! :) > As said, all initial BIOS limits were ignored by the kernel for quite some time > and this got fixed. Have you looked for BIOS updates and their changelogs > already? If not, this would be the next step. Yes, I have looked for the BIOS updates, but there are no updates to fix this strange behaviour. Moreover, I have been searching trough some fora these days and I see people saying that MSI (my laptop vendor) knows about this problem and says that "this is a company design policy of this model". This means they refuse to fix the bug in their BIOS and release an update, I guess. There are also many Windows users who experience the same problem and they found some software to tweak this on Windows too. > If this also does not help, please attach acpidump output (with the new BIOS!). > Be aware that this is very low prio bug, as it's very likely that the culprit > (most likely this is even intended) comes from the BIOS. Well, now it certainly is BIOS to blame. Thus it seems to me this bug may be closed already. I think that now it is a question of spreading the information about "processor.ignore_ppc" parameter. At least for operating systems using Linux as their kernel. Oh, and by the way, I have found on some Debian-related forum that this behaviour may be tweaked during run-time also by executing the following command: echo 1 > /sys/module/processor/parameters/ignore_ppc -- Configure bugmail: https://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
