Same thing happening to me here.
Problem persist even after multiple resets.
Definitely a Daylights savings time bug.
Problem persist even after multiple resets.
Definitely a Daylights savings time bug.
Seriously, people, is it really a big deal? I mean, a bump up on CPU one hour every YEAR, at midnight. Apparently, the system was just confused since it had gone through the same hour over again. Seems like the end of the world in this forum.
Mine's a unibody, so there might be some difference in fan speeds. But, 70c isn't "hot". Maximum ratings are 100 or over, depending on the specific model part. My fans don't start spinning up until the temp reaches >87c, but I'm sure the curves are different on the unibody. From the looks, they try to let the giant heatseak of the topcase do its job, keep the machine quiet, then once it's done as much as it can, throw some fan into the equation.
All clocks synced, and computer's happy - off to bed for me.![]()
I know it's not that hot, but without ramping the fans up I was getting to mid 80's. Thats a whole lot hotter than the normal 55ish I have ran at for 3.5 years.
I just did a clean instal of SL and the problem was still there. Next thing I am trying is rebuilding my entire spotlight index as that was acting strange.
I didn't encounter any problems, and many others haven't, either.
In any case it makes no difference now.
After a new install and reindexing Spotlight, it seems I have solved the problem. Not sure what was going on there, or why it decided to pop up when it did.
Thanks to those who helped me get through it.
I didn't encounter any problems, and many others haven't, either.
In any case it makes no difference now.