Looks like Intel has done it again! Who needs uid == root when you can just run on an Intel proc and take a peek at protected memory anytime you like, cuz the silicon's fucked? http://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ OS VM layers are being rapidly rewritten, performance hits will accrue, and who knows what else is broke...
On Wednesday, January 3, 2018, 12:34:55 AM PST, John Newman <jnn@synfin.org> wrote:
Looks like Intel has done it again!
Who needs uid == root when you can just run on an Intel proc and take a peek at protected memory anytime you like, cuz the silicon's fucked?
http://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/
OS VM layers are being rapidly rewritten, performance hits will accrue, and who knows what else is broke...
For some reason, I'm reminded of the 486 math processor screwup of 1992 (?). As I vaguely recall, the math coprocessor might have errors in the fourth digit of significance. Intel offered to replace the affected chips. Jim Bell
On Wed, Jan 03, 2018 at 08:48:12AM +0000, jim bell wrote:
For some reason, I'm reminded of the 486 math processor screwup of 1992 (?). As I vaguely recall, the math coprocessor might have errors in the fourth digit of significance. Intel offered to replace the affected chips.
I think it is the Pentium FDIV bug. IIRC only the server CPU was replaced in the whole office, don't remember why. From TFA: microcode can't fix it, lol. AMD is not affected. Shouldn't Intel do recall again?
On January 3, 2018 5:31:39 AM EST, Georgi Guninski <guninski@guninski.com> wrote:
On Wed, Jan 03, 2018 at 08:48:12AM +0000, jim bell wrote:
For some reason, I'm reminded of the 486 math processor screwup of 1992 (?). As I vaguely recall, the math coprocessor might have errors in the fourth digit of significance. Intel offered to replace the affected chips.
I think it is the Pentium FDIV bug. IIRC only the server CPU was replaced in the whole office, don't remember why.
From TFA: microcode can't fix it, lol. AMD is not affected. Shouldn't Intel do recall again?
I think they might go bankrupt ;) And think of all the work for sysadmins swapping CPUs & swapping systems... I think we are going to be stuck with OS level fixes that are potentially very bad for performance. People are already grumbling about the potential impact on AWS & other cloud providers... Speculation about a 30% performance hit?! https://www.reddit.com/r/technology/comments/7npcgu/kernel_memory_leaking_in...
On Wed, 03 Jan 2018 06:42:43 -0500 John Newman <jnn@synfin.org> wrote:
On January 3, 2018 5:31:39 AM EST, Georgi Guninski <guninski@guninski.com> wrote:
On Wed, Jan 03, 2018 at 08:48:12AM +0000, jim bell wrote:
For some reason, I'm reminded of the 486 math processor screwup of 1992 (?). As I vaguely recall, the math coprocessor might have errors in the fourth digit of significance. Intel offered to replace the affected chips.
I think it is the Pentium FDIV bug. IIRC only the server CPU was replaced in the whole office, don't remember why.
From TFA: microcode can't fix it, lol. AMD is not affected. Shouldn't Intel do recall again?
I think they might go bankrupt ;)
haha I wish. If people tried to sue intel, the US govt would throw the plaintiffs in jail. Oh, and here's another Pretty Good One https://arxiv.org/pdf/1710.00551 looks like all RAM is fucked hahaha
And think of all the work for sysadmins swapping CPUs & swapping systems... I think we are going to be stuck with OS level fixes that are potentially very bad for performance. People are already grumbling about the potential impact on AWS & other cloud providers... Speculation about a 30% performance hit?!
https://www.reddit.com/r/technology/comments/7npcgu/kernel_memory_leaking_in...
On Wednesday, January 3, 2018, 2:31:44 AM PST, Georgi Guninski <guninski@guninski.com> wrote: On Wed, Jan 03, 2018 at 08:48:12AM +0000, jim bell wrote:
For some reason, I'm reminded of the 486 math processor screwup of 1992 (?). As I vaguely recall, the math coprocessor might have errors in the fourth digit of significance. Intel offered to replace the affected chips.
I think it is the Pentium FDIV bug. IIRC only the server CPU was replaced in the whole office, don't remember why.
While doing a Google search, I saw reference to the Pentium problems, but there definitely was a 486 problem too. In fact, it came with a joke: The drug "RU486" had been relatively recently been released, and the joke was that the 486 "prevented you from multiplying". The corrected, replacement CPU was given a double-sigma after the 486, although I just found that a similar double-sigma was used for the replacement for a 386 bug as well.
From TFA: microcode can't fix it, lol. AMD is not affected. Shouldn't Intel do recall again?
Presumably, yes, especially due to the performance hit. I'm satisfied with AMD, but the people who insist on Intel processors claim that it's worth the extra money. But that argument gets destroyed if "fixing" the problem produces more than a small hit. Jim Bell
participants (4)
-
Georgi Guninski -
jim bell -
John Newman -
juan