Re:Reverse-engineering the classic MK4116 16-kilobit DRAM chip
by drfuchs on Saturday November 14, 2020 @01:23PM
(#25094311)
Great! Question: When 64K DRAM first appeared, I remember a cover article in EDN(?) claiming that nothing denser could ever be built, because cosmic radiation would zap individual electrons, and thus flip bits too frequently, and there was nothing you could do to protect from it. So, how was that thinking wrong?
[ Parent
| on HN ]
Re:Reverse-engineering the classic MK4116 16-kilobit DRAM chip
by kens on Saturday November 14, 2020 @01:43PM
(#25094492)
They discovered that most of the DRAM soft errors were due to alpha particles from the ceramic packaging. Changing the packaging solved most of the problem.
There are still bit flips due to cosmic rays but the rate is low enough that most people don't care. ECC memory can be used if errors are a problem.
More details on Wikipedia: https://en.wikipedia.org/wiki/Soft_error#Alpha_particles_fro...
Re:Reverse-engineering the classic MK4116 16-kilobit DRAM chip
by askvictor on Saturday November 14, 2020 @10:53PM
(#25098103)
At least they weren't due to radioactive cows: https://www.jakepoz.com/debugging-behind-the-iron-curtain/
Re:Reverse-engineering the classic MK4116 16-kilobit DRAM chip
by formerly_proven on Saturday November 14, 2020 @04:27PM
(#25095787)
Some of Sun's servers famously suffered big reliability problems due to using IBM SRAM as caches, which is said to have had elevated error rates due to more alpha-emitting contaminants in their particular package filler.
Re:Reverse-engineering the classic MK4116 16-kilobit DRAM chip
by kens on Saturday November 14, 2020 @04:39PM
(#25095882)
I was at Sun at the time (although not working on that), and these memory errors were a catastrophic problem for Sun. Customers were paying a lot of money for Sun's reliability and then systems started mysteriously having problems and Sun couldn't figure out why.
Re:Reverse-engineering the classic MK4116 16-kilobit DRAM chip
by lokedhs on Saturday November 14, 2020 @10:29PM
(#25097982)
I was there too. That would be the ecache problem, right?
I was in the service division at the time, and yes, it was a serious issue. However, if I recall correctly it was limited to the E10K. It was the flagship machine, so of course it got all the attention, but most customers didn't suffer from it.