DailyDirt: Lies My Computer Told Me...
from the urls-we-dig-up dept
We trust automated solutions to perform all kinds of critical tasks, but how often do we verify that we're actually getting the right results? We survived the Y2K bug, but there are plenty of other examples of software and hardware flaws that could be much more (deadly) serious. Here are just a few disturbing computer glitches that you might have missed.- Recently, it's been discovered that some Xerox machines don't make exact copies, and in an effort to "clean up" images, they can introduce egregious errors that can swap numbers. The scary thing about this is that you might never notice that the photocopier changed your numbers around for you.... #youonlyhadonejob! [url]
- Intel sold millions of defective Pentium chips that didn't quite perform calculations correctly, and a math professor (Thomas Nicely) discovered the problem while he was working on a computational number theory project. Intel ultimately recalled the processors, but it publicly stated that the flaw would only affect a typical PC user with a spreadsheet less than 1 time every 27,000 years. [url]
- In the mid-1980s, the Therac-25 medical accelerator had a software problem that killed at least 5 people and others were seriously injured from radiation overexposure. A race condition in the Therac-25's operating system that allowed the device to turn on an electron beam even when its metal X-ray target was out of position. [url]
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: bug, computer, defective, error, flaw, glitch, mistake, pentium bug, photocopier, race condition, software, therac-25, thomas nicely, y2k
Companies: intel, xerox
Reader Comments
Subscribe: RSS
View by: Time | Thread
Intel Pentium Bug
That is, since the problem showed up in the fifth or sixth significant figure, there were no practical calculations in which the bug mattered.
Now, let's see if my beautiful, sacred theory survives contact with profane reality. (Grin)
[ link to this | view in thread ]
Therac-25
The case became a standard safety failure example in the design of programmable logic control ladders.
[ link to this | view in thread ]
Re: Therac-25
[ link to this | view in thread ]
Re: Intel Pentium Bug
Amateur astronomers need accurate ephemerides
Electronic hobbyists need accurate circuit simulation
Who knows, you might want to calculate some standard deviation
......
[ link to this | view in thread ]
[ link to this | view in thread ]
Intel sold millions of defective Pentium chips...
*Except on a Pentium
[ link to this | view in thread ]
Serious Bug - just wait
2147483647 - Mon, 18 Jan 2038 22:14:07 -0500
The next second is -Fri, 13 Dec 1901 15:45:52 -0500
Much more serious than the Y2K problem.
BTW: both DEW and some Gov. agencies were down for several days, but they kept it quiet.
[ link to this | view in thread ]
Re: Serious Bug - just wait
I wouldn't bring up Y2K in relation to this, for two reasons. First, it's a different kind of problem and second, the unbelievable overhyping of Y2K was crying wolf. If we want the Unix rollover to be taken seriously, the best thing we could do is to distance it as far as possible from the BS that was Y2K.
[ link to this | view in thread ]
[ link to this | view in thread ]
[ link to this | view in thread ]
[ link to this | view in thread ]
[ link to this | view in thread ]
[ link to this | view in thread ]