The Odd Story of Factory-Downgraded 486s (2020)
x86.fr
x86.fr
In 1998 a had a summer job, as a programmer, in a little shop that built computers. At the time there was a short of Pentium II 300Mhz chips. One day the logistics guy mentioned they had gotten a batch of Pentium II 300Mhz marked with an operating voltage of 2.0V, instead of the usual 2.8V. Hmm.
Intel had taken a bunch of their most expensive CPUs, PII-450Mhz, using the brand new 250nm process and rebranded them as the cheapest CPUs which were at the time built with a 350nm process. You could just take this, stick in a motherboard an change the base frequency and you'd have the best CPU Intel could make.
We never sold any of those CPU to customers. We all bought ourselves new CPUs that day.
I was trying to confirm this, but he didn't claim credit for that in this interview: https://www.tomshardware.com/reviews/20-year-anniversary,455...
P.S.
Also, some twenty years ago another MD rewrote the Linux scheduler, because he wanted better interactive performance: https://en.wikipedia.org/wiki/Con_Kolivas
While from an objective amount 50-150mhz is peanuts in today's terms, that was a huge step up relative to the original speed.
Sandy Bridge and Sandy Bridge-E were fantastic overclockers too with many samples going to 4.7 GHz (even on HEDT!).
Broadwell-E, too, could hit some solid clocks if you were willing to push more voltage... a lot of people got later samples to 4.7 GHz despite the numbers being closer to 4.3 in SiliconLottery's tests. Probably an uncomfortable amount of voltage and heat, but, Broadwell itself wasn't as bad as people took it to be, just the prices, and the L4 cache on Broadwell-C limiting the core clocks.
https://en.wikipedia.org/wiki/List_of_Intel_Core_i7_processo...
https://siliconlottery.com/pages/statistics
This is somewhat of a function of Intel not really pushing clocks in those days. 3.3 GHz all-core turbo is nowhere near what the silicon could deliver - generally I would punch in 4.1 GHz all-core on my 5820K and that would be stable without any other (explicit) settings adjustments.
And that is a factor of the TDPs - in those days TDP on desktop was expected to cover your max boost under a (reasonably) worst-case load. It has been a thing for a long time in laptops, but the desktop market was different. AMD was actually the one who introduced the "boost TDP is higher than box TDP" concept (aka PPT) to the desktop market with Ryzen 1000 - and then Intel started following suit once they started ramping up core counts and clocks with the 8700K/9900K.
But 140W is actually plenty for a hexacore or even octocore running at 3.3 GHz and even under a worst-case load scenario... and 91W is plenty for a quad-core running at max turbo too. The numbers weren't as phony back then.
https://www.anandtech.com/show/10968/the-intel-core-i7-7700k...
https://www.anandtech.com/show/8426/the-intel-haswell-e-cpu-...
Tells you a lot of CPU production economics.
You could tell (at least initially, I'm not sure if Intel changed this later) from part of the product code that you definitely had one of the units from a batch that tested fine at the higher speeds, so it wasn't that much of a gamble either.
We referred to them as Silly-ron CPUs.
Of course now every CPU is its own multiprocessor machine, but back then it was a real screamer, and unless you could get multi-CPU Windows it was a real reason to poke around with Linux.
[1] This is from the era before the memory controller / northbridge was integrated with the CPU.
[2] https://datasheet.octopart.com/FW82443BX-Intel-datasheet-533... - page 12 has the basic system diagram
I remember having an older Pentium Pro motherboard with dual sockets.
It worked great from about 1999-2002 when I upgraded to an Athlon 1700, then an Athlon 64. I finally had 2 CPU cores again with the Athlon 64 X2 around 2005.
CPU economics are weird.
https://www.hwcooling.net/en/not-every-core-i5-13400f-is-the...
Same goes for silicon. The dies are largely the same. Only later in the process, they get binned to a lower spec cpu by selectively disabling features. Generally, this is because the chip doesn't meet some spec, but there are cases where this is simple done to meet demand.
>Go buy 1000 5% resistors and test them. Instead of a normal distribution of tolerances, you'll find that there's an interesting trough around -2% to +2%.
EEVBLog tested the 1% ones and it had gaussian https://www.youtube.com/watch?v=1WAhTdWErrU which means it couldn't really be 5% but binned
Also 5% are usually carbon while 1% are metal film so no, try again.
That said, it's neat when it works!
[0] https://www.tomshardware.com/reviews/glossary-binning-defini...
I hadn't heard about this, I think this is what's being discussed here:
https://groups.google.com/g/comp.arch/c/qm7FVR_YV4A/m/P97XlC...
> Contrary to industry speculation, the 80386 multiplier errors result from a layout problem, not from an error in logic design. "We didn't allow enough margin to catch the worst-case pattern in the multiplier at the corners of our process," explains Dana Krelle, Intel's 80386 marketing manager. "As a result, some chips, at some temperature/ voltage/frequency points, will produce errors from particular combinations of 32-bit operands." The error, apparently due to unintentional coupling between adjacent cells in the multiplier, escaped Intel's simulation and chip verification process until it was spotted in a subsequent stress-testing program.'
What do you think, could it be factories or corporations that have critical processes running on ancient software that requires very specific hardware to run, and which nobody wants to pay to rewrite for modern hardware? Young me would have said "don't be silly", but I've seen some crazy things, man.
I seem to recall a video running a Control, maxed out on a 22" Flat CRT at 1280x1024 that looked better than a 4k display sitting next to it, let alone the performance differences.
I know I held on to my pro grade CRTs until I had to move them 3x one summer... man they were heavy. Had a permanent bow in my desk.
For the record I needed to downscale Doom to about a 1/2 window (running in DOS) to have it run at a decent framerate. Can't have been 100MHz, right? Does anyone here have a comparable benchmark of a "true" 100MHz 486 I can compare with?
Thus began my fascination with computers. Booting up DOS in some low-memory mode in order to squeeze every CPU cycle out of that thing. Working within constraints taught me a lot.
I didn't have internet at the time, but this thing had a 14.4k modem that I tried to get running. When the modem was in use, the mouse froze (and vice-versa). They were on the same IRQ interrupt jumper I think. I ended up frying the motherboard trying to fix this issue. I didn't have a computer for a while, but after lots of pleading and my parents seeing that I was serious about this, they eventually got me a Pentium 2 (450MHz or so!). But alas, it had a Voodoo Banshee video card (which had notoriously-bad drivers which often simply hard crashed). Alas, working within another constraint...
Obviously these cards were meant for use in Pentiums with their extra processing power. But some stingy integrators coughPackardBellcough would slap together the lowest cost components without regard to if it'd actually work properly.
A Pentium is much faster than a 486 at the same clock speed, so that shouldn't be surprising.
They were able to use CPUs that they would otherwise have to discard, due to defects, by disabling the faulty core.
Didn't Intel physically burn out perfectly functional fpus to make SX's?