CPU speed does not throttle down

[borgit]

Hi guys, I have a t42p 2373ktu, and recently i've noticed that every time i resume from standby mode, the cpu speed goes all the way back up to 2000mhz and does not come down to 600mhz, even though i am in super battery savior mode, which calls for "slow" cpu speed. So it is like it is ignoring the power savings mode. I've only noticed this after resuming from standby mode. Also, i am running the latest version of the IBM battery maximiser utility. Does anyone have any idea as to what could be going on? Thanks for any info.

[brewt]

Check IBM's site for any suspend related bios or driver updates.

PS: My T42 2378FVU throttles back to 600MHz after resume fine.

[eriqesque]

My X40 Does this as well.
Also It will not go into Hibernation by itself after a given time while on battery. It will standby but then will not continue through and hibernate afterwards.
I think it's all related to SP2

[borgit]

It seems like my problem only happens sometimes, that is, sometimes upon returing from a standby, the cpu speed is fine (at 600), but sometimes it goes all the way up to 2Gig, even with the highest power savings on. I think all my drivers are up to date. The battery maximiser is latest, the bios as well as power management are latest as well. One last important thing, i use CPU-Z to check my cpu speed. In windows, for some strange reason, when you right click on my computer, it shows 179mhz when it is really running at 600, and 597 when it is running at 2gigahertz. I think maybe alot of you guys also experience this behavoir but not all of you notice it since there is no easy way to tell the exact cpu speed in windows itself, you really need a 3rd party utility. So if some of you are interested, get cpu-z its a free utility, and see what happens after you resume from standby. I would be interested in the result. Thanks alot for the input.

[Moroner]

I noticed the exact same problem on my new T42p that came with a November image. It looks like there is a workaround: When I switched to a max power profile, and then back to my battery saver profile I actually want to use, the CPU speed comes back down to 600 MHz.

In other words, some programmer forgot to check for the possibility that the CPU speed might change because of standby/sleep mode, and happily uses his wrong cached value