Re:When Solid State Drives Are Not That Solid
by jjawssd on Tuesday June 16, 2015 @03:11AM
(#9724213)
If you think CPUs do not come with a shit-ton of hardware bugs YOU ARE GRAVELY MISTAKEN.
Google up the Intel errata for the i7
The list goes on and on.
Re:When Solid State Drives Are Not That Solid
by ptaipale on Tuesday June 16, 2015 @03:16AM
(#9724226)
I didn't see him thinking that. Just that CPUs do not have as many bugs as other hardware - which I think is quite true. With CPUs a larger portion of bugs are found, and smaller bugs matter because they are not hidden by proprietary drivers.
Re:When Solid State Drives Are Not That Solid
by notacoward on Tuesday June 16, 2015 @08:47AM
(#9725323)
FWIW, memory has plenty of bugs too. With respect to the original point, these are usually not visible to drivers (unless you count EDAC) because they're handled at the chipset level. However, for certain kinds of systems - especially embedded - that don't have chipsets these issues can become painfully visible. My own exposure to this was at SiCortex, where the memory logic was directly on the same single die as everything else that comprised a node.
Re:When Solid State Drives Are Not That Solid
by digi_owl on Tuesday June 16, 2015 @03:40AM
(#9724279)
Heh, i still recall my early encounters with Linux and reading the bootup messages.
One of them contained a line related to having found a CPU bug and having put a workaround in place.
I am not entirely sure, but i think it may have been the F00F bug.
Ha. Reminded me of the Pentium Floating Point Bug from the 90s. First (only?) time a CPU bug has been an international press story?
So another way of putting what you said would be "on Linux there's no working driver for that piece of hardware, unlike on Windows where the 'proprietor' went to the trouble of supplying such a driver."