3 ms·
Intel: A Bug and a Pro
- jmclnx 2y agoAbout the F00F bug, and a nice read. Edit: Seems IBM stopping shipment of these buggy PCs forced Intel to fix the problem. I cannot imaging today's IBM doing something like this.
- wglb 2y agoHowever I was quite concerned at the time when they said, quite incorrectly that there was no risk to their users from this bug.
- charcircuit 2y agoWhat is the risk? It seems very small to me.
- wglb 2y agoThe risk is that some divisions will be fully off. If it is a chain of calculations, e.g. some stress analysis, or a spreadsheet involving a chain of calculations for a financial report, it could be bad.
- charcircuit 2y agoDivisions being off isn't the end of the world. Even without the bug the division can be fully off due to it using fixed precision floats. Stress analysis and financial reports are more likely to be wrong due to other sources of error than a division being slightly off. If you really wanted exact numbers you wouldn't be using fixed precision floats anyways.
- wglb 2y agoFrom the wikipedia article: Abrash spent hours tracking down exact conditions needed to produce the bug, which would result in parts of a game level appearing unexpectedly when viewed from certain camera angles.
- charcircuit 2y agoYet, they thought the 1 frame flash was insignificant enough to ship the game with it instead of spending time to workaround the bad division. But thank you for providing an example.
- MBCook 2y agoYeah but when the bug triggered you only got like eight digits worth of floating point. The article says IBM expected normal users to hit it every few days.
- charcircuit 2y agoHitting the bug doesn't mean that it would cause a practical issue for the user.
- hansvm 2y agoAlright, then quantum chemistry simulations. It's very common in the field to have algorithms with known error bounds given a certain floating point size and to choose a size amenable to the scale of simulation you intend to attempt. If some of your computations are at half precision, the results are hosed.
- charcircuit 2y agoMost consumers are not doing quantum chemistry simulations.
- inetknght 2y ago> If you really wanted exact numbers you wouldn't be using fixed precision floats anyways. Let the adults play with things that need to work exactly as documented (such as IEEE 754 floating point representations) and therefore can be relied upon when required. You can go back to building your little unreliable toys that nobody uses.
- charcircuit 2y agoThere is no need to belittle me while not providing a practical example where the average consumer can be harmed by this bug.
- fragmede 2y agotherac 25?
- charcircuit 2y agoThe average consumer with a pentium didn't have it in a radiation therapy machine.
- 2y ago
- insufferable_tw 2y agoThis is a perfect example of "normalization of deviance".
- brookst 2y agoaka six sigma?
- eru 2y agoYou don't need precise numbers to figure out whether your bridge will stand. What you need is a calculation designed to be robust to the errors incurred in measurement and computation. The standard for floats guarantees you specific and precise error bounds that you can use to do an error analysis for your whole calculation. Most likely whatever engineering software you use to check your bridge design, will already have this error analysis baked in. If you introduce some arbitrary other errors, you'd have to redo you error analysis from scratch. And it might not even be tractable, depending on the errors introduced. (The standard floating point error guarantees are designed to behave reasonably well and easily predictably when combined into a larger calculation.)
- colechristensen 2y agoYou just have no idea what you're talking about. People get killed when things go wrong, and this "oh well other problems are probably worse" attitude is dangerous. There's no such thing as exact numbers, but there is such a thing about reliable models. The errors introduced by calculating with numerical methods are studied and well understood, a processor not following exactly the rules it's supposed to is an enormous problem. Here's a little introduction to condition numbers and how they're used to understand floating point error introduced in calculations: https://www.cs.cornell.edu/~bindel/class/cs6210-f12/notes/lec04.pdf https://www.cs.cornell.edu/~bindel/class/cs6210-f12/notes/le...
- charcircuit 2y agoThe FDIV bug is not theoretical. It existed and no one died from it. People love to come up with theoretically how the bug can cause terrible things to happen, but in practice it didn't. The next run of the processor had the fix and the world moved on.
- colechristensen 2y ago1. Intel wasn’t very popular for scientific computing in 1994 2. No one was stupid enough to make life critical calculations on Intel after it was discovered and widely publicized You, on the other hand, are suggesting it was no big deal and acting like people doing important work should have just ignored the bug. The reason bugs like this didn’t kill people in a large disaster is that folks with your disposition weren’t in charge of making decisions that would have led to that. They did a recall that cost Intel a billion dollars adjusted for the present. It wasn’t just ignored.
- charcircuit 2y ago>and acting like people doing important work should have just ignored the bug. No, I am acting like the average consumer could have ignored the bug. There wasn't a need to do a mass recall of every chip as the chip would still be fine for most users. Yes, there was a recall for people who needed it to work correctly, but in practice not everyone needs it.
- wglb 2y agoAnd another note: Locked reads must be paired with locked writes, and the CPU's bus interface enforces this by forbidding other memory accesses until the corresponding writes occur. As none are forthcoming, after performing these bus cycles all CPU activity stops, and the CPU must be reset to recover
- comex 2y agoNo, F00F was a different bug from a few years later.
- pixl97 2y agoYep, locked the PC up dead.
- rbanffy 2y ago> I cannot imaging today's IBM doing something like this. Today's IBM doesn't ship Intel servers, or Intel anything. They sold that part of their business to Lenovo.
- piokoch 2y agoPeople forget that a company known as IBM went bankrupt, was sold and reborn as a consulting enterprise like Accenture or McKinsey. The only thing that remained from the olden days are servers, in particularly z-series, which are modern days equivalents of mainframe solutions (and they are pretty awesome).
- rbanffy 2y agoThey almost went bankrupt. Starting with Lou Gerstner, IBM cut out the least profitable parts (commodity PCs, then, later, commodity servers), and focused on services (which also acts as a sales enabler) and high-margin hardware and software.
- perching_aix 2y agoSounds like you might be personally familiar with (their?) mainframes. Could you explain what's awesome about them, and what even are mainframes? Whenever I tried looking into this, I walked away with "just servers networked together".
- rwmj 2y agoInterestingly Linux uses "Coe's ratio" (4195835/3145727) dating from 1994 to check for the FDIV bug. Coe's ratio: https://people.cs.vt.edu/~naren/Courses/CS3414/assignments/pentium.pdf https://people.cs.vt.edu/~naren/Courses/CS3414/assignments/p... (3rd page) Linux code: https://github.com/torvalds/linux/blob/b0cb56cbbdb4754918c28d6d7c294d56e28a3dd5/arch/x86/kernel/fpu/bugs.c#L14 https://github.com/torvalds/linux/blob/b0cb56cbbdb4754918c28...
- bendercorn 2y agoShould have mentioned that intel marketing and PR launched the User Test Program to make sure advanced users got early PPro systems to make sure there were no lurking fdivs. Nicely was the first recipient. So was John Williams the composer.
- rbanffy 2y agoJohn Williams from Star Wars or John Williams from Sky?
- defrost 2y agorim shot: https://youtu.be/QgbgUrp1a70?t=67 https://youtu.be/QgbgUrp1a70?t=67 FWiW I bought (one of) Kevin Peek's guitar amps in 1982 in Kalamunda (W.Australia) .. it was just an ad in the classifieds, got out there and it was a damn near world class music studio in a one room music cabin in the bush.
- bendercorn 2y ago[dead]
- ankitg12 2y agoRelated discussion sometime back - https://news.ycombinator.com/item?id=42535071 https://news.ycombinator.com/item?id=42535071
- adrian_b 2y agoThe Intel marketing is responsible for a large number of despicable decisions during the years, but I consider that by far the most despicable thing done by them happened when they have segmented their CPU products into Pentium and Pentium Pro. Later, they have dropped the "Pro" naming scheme and the successors of "Pentium Pro" have been branded as "Xeon", until today. IBM had been wise and they had incorporated memory error detection as a standard feature of every IBM PC, so that has also been true for all IBM PC clones. By the early nineties, when the memories packaged in dual-in-line packages have been replaced by memory modules, you could buy complete memory modules with error detection, but there were also slightly cheaper memory modules without error detection, so a computer owner could choose either of them. I am not a gambler, so I have always used only modules with error detection. However that has changed in 1994, when Intel has decided to split their CPUs into Pentium for "consumers" and Pentium Pro for "professional users" who were willing to spend much more for a workstation or server computer. This is when Intel has decided that in order to stimulate their customers to buy overpriced "Pro" CPUs, memory error detection must be removed from their "consumer" CPUs. While in 1993 the first generation of computers with Pentium still had memory error detection, for the second generation in 1994 (with the Triton chipsets), memory error detection was removed, in preparation for the launch of Pentium Pro next year. We will never know the value of the financial losses that have been inflicted worldwide upon naive computer users by this Intel decision. Fortunately for Intel and unfortunately for us, software bugs have always been so frequent that all computer users have been conditioned to assume automatically that whenever the computer crashes or data corruption is discovered, the cause must have been some software bug and it must be difficult or impossible to determine the exact culprit. Despite this common assumption, many of these incidents may be caused by hardware memory errors and besides the noticed incidents there may be many other cases of data corruption that have never been discovered. The claim of Intel that this removal of memory error detection has been done for the benefit of the customers, to reduce the price of the computers, is of course false. After it became impossible to have memory error detection in "consumer" PCs, there was no price reduction in motherboards or memory modules, the prices have remained the same and their vendors had increased profits, so they have supported enthusiastically the initiative of Intel.
- jeffs4271 2y agoI am just shocked to see a MIPs R8000 reference in 2025. It was relatively obscure CPU targeted at HPC and weaker at integer workloads. I worked on a lot of cool stuff, but that project was probably the most fun.
- wuming2 2y agoCare to expand? Also I often wonder what the aggregate statistics of `top` load average and standard deviation looks like over billions of consumer devices over time.