*had* the same problem
it just so happened that, soon after I noticed it, a kernel update became available and I no longer have that problem.

since I don't use my laptop all that often I have no idea how long the problem existed.

FWIW (OT), I have at least 7 working Core2Duo CPUs. Every one of them runs on a motherboard that incorporates an *Lake chipset. Yours probably does too.

You're clearly refering to something here - why don't you just spit it out? Afraid to get off your high horse?

Glad to see those reporting this as fixed. Indeed, I am not trying to run the latest kernel here - I've been sticking with the old LTS kernels, but once I tried out 4.14 I noticed this in a big way (otherwise 4.14 seems fine, as it *finally* fixes i915 on one of my laptops). So those jumping from 4.4.x to 4.19.x and beyond may never have noticed it.

There's no high horse here - I just care about openness and reproducibility. I get upset when people think that all "modern" computing necessitates > i3 processors which can't be used without management engines and other malicious nonsense, and it seems that's what the kernel developers must use personally or else bugs like this never would have gotten out. Likewise there is much effort for gpu drivers that are nowadays almost all cryptographically signed. So this newfangled Linux kernel, if you can call it that, is getting farther and farther away from it's first and foremost role as the kernel for the GNU operating system which has clearly different goals.

Not to mention, the performance increase from Core 2 Duo to i-whatever isn't necessarily that noticeable on most tasks, except that you get more cores and less power consumption.

Chromebooks which can be operated without any of this (like those usable with libreboot) are probably fine, but I just see that as a cell phone in a laptop case.

As for being reproducible, and I digress here, I first became slightly aware of its need a number of years ago in one of my mathematical programming classes. A graduate student pressed the professor on the appearance of a particular graph being projected on the wall. After going around and around, the professor threw up his hands and said "Mathematica says so." That's not acceptable in any mathematical sense. Likewise, I see even professional photographers yanking "exposure" sliders around freely in certain Adobe programs. This is mathematical nonsense, because all of these sliders are in-house, closed-source non-linear transformations. In documenting what you do, you can only say "In program X, version Y, move slider A from a to b." Regardless of whether libre programs like Gimp exist in the next millennium or can run on whatever hardware exists then, if you can write down what steps you used to manipulate an image, the mathematical instructions are transparent and can be ported over.

At least in principle with a libreboot bios, clean/sane kernel, open userspace programs, and honest (human) users, the steps to complete a task can be mathematically reproduced back to the moment the power button was pressed. In this sense these nowadays older chips that at least in principle could be used with libreboot and friends HAVE to work - these should be considered bench marks like the Sevres meter sticks and the like.

1 members found this post helpful.

So it is fixed now?

In principle I agree here (I currently experience something similar with pango dropping support for Type 1 bitmap fonts), but OTOH I always thought that using hardware that is much older than 10 years is kinda pointless - well, at least that was my opinion when I started using Linux and tried A LOT of hand-me-down laptops. But then again, my 2008 32-bit laptop is still running strong as a server. I have never noticed any CPU issues (I would hear if the fan span constantly). But that one is just on the other side of the IME divide, unfortunately.

Well we're just now getting to the point that 10 year old hardware isn't that much different - when I got my first "new" laptop (up to 4 GB RAM, dual core, etc), I was replacing a desktop that initially came with 64 MB (which I upgraded to 256) and a 6 GB hard drive. Contrast 10 years prior to that, when Windows 2.1 was current.

Didn't know about the pango situation - looks like trouble on the line for my next BLFS build.

so i did google for you because you may not be able to do this by yourself:
https://ark.intel.com/content/www/us...6-mhz-fsb.html

you should have read this:
ever heard of kernel modules ? this is a KERNEL subthread ...

is it rearly to hard to read DOCUMENTS ???
or the answers witch are given to you ?

why dont you use the right DRIVER ??

I also noticed recently that there's one or two active (not the old ones seen below) threads on very similar topics. "frequency scaling" might find them.