News for hackers. Stuff that matters.
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by ohaal on Thursday January 04, 2018 @08:07AM (#16070040)
Related talk (relevant part starts at 38:43) https://www.youtube.com/watch?v=KrksBdWcZgQ

Quote from the talk: I don't want to make it sound like the sky is falling. This was found on one very esoteric processor that is not used in widespread production. I think it's mostly interesting from an academic perspective that we have a tool that is able to find these kinds of things now.

Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by baybal2 on Thursday January 04, 2018 @08:21AM (#16070124)
Sorry for the typo, it is p. 155.

For quite a few days, people were suspecting that to be an Intel bug. The desktop shown in the video was a Dell Precision one, which means Core or a Xeon.

Another suspected cpu is said to be Intel X1000, if the demo was not running on the desktop. This was because Intel has issued a non-public errata just for major embedded partners before.

From myself, I will add that another suspect is Intel 80579 which is a still sold Pentium M/Core 1 SoC

Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by dschuetz on Thursday January 04, 2018 @08:39AM (#16070219)
While the title is a bit misleading, the presentation suggests enough to say that common CPU designs and architectures should be revised. Undocumented alone should always raise red flags. Imagine your average safe or door lock has undocumented keys or means to be opened without you noticing. Or your car having undocumented extras.
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by phoe-krk on Thursday January 04, 2018 @07:59AM (#16069986)
Page 154 says nothing about Intel. Kindly stop feeding the FUD.
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by coldtea on Thursday January 04, 2018 @08:11AM (#16070065)
Check the next page. Page numbers are not always reported faithfully on all PDF readers.

Besides, a 150+ page document of processor bugs and arcana is hardly FUD.

Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by dschuetz on Thursday January 04, 2018 @08:29AM (#16070169)
I second that. CPU bugs are the worst you can have. Means that are able to provide insight into instruction space of common CPUs are more valuable then your average particle collider.
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by angled on Thursday January 04, 2018 @08:14AM (#16070084)
I assume OP is meaning p156 (title slide, author slide, +154). That said, is this not so new news?

https://twitter.com/xoreaxeaxeax/status/888702029744324608?l...

https://www.theregister.co.uk/2015/08/11/memory_hole_roots_i...

Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by dirtbox on Thursday January 04, 2018 @08:10AM (#16070054)
Here's the page for all who wondered.

https://image.prntscr.com/image/KDuFv8gRQYeLJG3pO8wwmQ.png

Within the context of the prior and subsequent pages, it appears to be talking about AMD.

Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by eleitl on Thursday January 04, 2018 @08:14AM (#16070079)
It's the page after that. And, no, it doesn't seem to be AMD when looking at the side of the grey bar censoring the vendor.
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by eleitl on Thursday January 04, 2018 @08:13AM (#16070070)
It's page 155 and they've blanked out the vendor.

The bar is too short for Transmeta and too broad for AMD. It could well be Intel, judging from their other slide using Intel in the same location and font.

Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by contrarian_ on Thursday January 04, 2018 @08:15AM (#16070086)
The bar is just the right width for "(redacted)", I wouldn't read into it.
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by seba_dos1 on Thursday January 04, 2018 @08:14AM (#16070081)
The length of the bar tells you nothing, as it simply covers the "(redacted)" text underneath.
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by Certhas on Thursday January 04, 2018 @08:27AM (#16070161)
Presumably it hasn't been disclosed yet which systems are affected?
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by aceoflala on Thursday January 04, 2018 @08:07AM (#16070039)
155 probably
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by saas_co_de on Thursday January 04, 2018 @08:09AM (#16070048)
It looks like it says a Transmeta bug ... wtf is that? who cares?
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by contrarian_ on Thursday January 04, 2018 @08:10AM (#16070057)
One page later: (redacted) hardware bugs.

Sounds like something that would be hopefully fixable in microcode.

Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by seba_dos1 on Thursday January 04, 2018 @08:11AM (#16070063)
If it's really about Intel here, at least this seems like something that could be mitigated with microcode update.
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by wolfgke on Thursday January 04, 2018 @08:11AM (#16070064)
Assuming that you mean page 155: What is your evidence that it is a bug on Intel Core?
Re:A CPU bug with undocumented opcodes, possibly Intel (scro... by FLUX-YOU on Thursday January 04, 2018 @08:38AM (#16070213)
This is misleading. The author of the talk has not revealed the vendor.