Live data from Hacker News

Intel Security Issue Update: Addressing Reboot Issues

newsroom.intel.com

71–80 of 129 posts

Re: Intel Security Issue Update: Addressing Reboot Issues

#71
post #66

Earlier quoted context omitted.

Intel's greatest PR success in this mess has been to conflate Meltdown with Spectre. Only Intel is affected by Meltdown because of their design, and it is a more easily exploited bug.

Meltdown is not only Intel. Some ARM and Apple designed ARM processors are affected by Meltdown as well. https://en.wikipedia.org/wiki/Meltdown_(security_vulnerabili...

There are no products on the market shipping with the one ARM-designed processor affected by Meltdown.

Re: Intel Security Issue Update: Addressing Reboot Issues

#72
To be fair, it can well be that some sloppy OEM drivers take too many assumptions on reserved bits in registers (which the new microcode may be legitimately changing) or on undocumented timing side-effects related to some instructions (which the new microcode may affect, being that the root problem in the first place!).

These symptoms are also the classic ones you get when you install an OS on a new-generation, well-functioning CPU.

Re: Intel Security Issue Update: Addressing Reboot Issues

#73
probably related news from Dell: "NOTE 1: 13G, select 12G, and select DSS server BIOS files have been pulled from http://dell.com/support. This note and article will be updated as soon as more information is available" [1]

the pulled out BIOS update files for 13th gen were released on 5th of Jan.

[1] http://www.dell.com/support/article/us/en/04/sln308588/micro...

Re: Intel Security Issue Update: Addressing Reboot Issues

#74
post #71

Earlier quoted context omitted.

Meltdown is not only Intel. Some ARM and Apple designed ARM processors are affected by Meltdown as well. https://en.wikipedia.org/wiki/Meltdown_(security_vulnerabili...

There are no products on the market shipping with the one ARM-designed processor affected by Meltdown.

I think that's mainly out of luck. If the exploit had been discovered two years later, the story would likely be different. Apple has been much more ambitious with their ARM processor designs and has shipping iOS and AppleTV products affected by Meltdown.

Shipping or not, it illustrates, that Intel was not unique.

Re: Intel Security Issue Update: Addressing Reboot Issues

#75

My broadwell (i5-2500k) windows desktop has started blue screening like crazy if I do large continous network transfers (i.e. saturating gigabit ethernet). I didn't have this problem before I rebooted for my most recent update. I thought it might be memory, but an 8+ hour memory scan (windows internal one, not the normal linux one) didn't tickle any bad bits and its not erorring in any unique component, each time, it…

> My broadwell (i5-2500k)

That's Sandy Bridge, 3 generations older than Broadwell.

Re: Intel Security Issue Update: Addressing Reboot Issues

#76
post #16

Earlier quoted context omitted.

Why should they bother communicating clearly with their customers? Who are those customers going to turn to? AMD? ARM? Between Intel's numerous CPU bugs that they refused to refund customers for and ME, it's crystal clear what Intel thinks about their customers.

Customers actually could turn to AMD... their offerings are very competitive right now.

As an avid fan of AMD going back to the late 80s they have always been a cheaper and better alternative. I am still bitter about rdram in regards to Intel

Re: Intel Security Issue Update: Addressing Reboot Issues

#77
post #71

Earlier quoted context omitted.

There are no products on the market shipping with the one ARM-designed processor affected by Meltdown.

I think that's mainly out of luck. If the exploit had been discovered two years later, the story would likely be different. Apple has been much more ambitious with their ARM processor designs and has shipping iOS and AppleTV products affected by Meltdown. Shipping or not, it illustrates, that Intel was not unique.

Now can you argue that the given faulty design was not directly influenced by Intel conscious and deliberate bad decisions ?

Re: Intel Security Issue Update: Addressing Reboot Issues

#78
post #55

Earlier quoted context omitted.

Wow, that's a good point. "...the exploits uncovered by Google Project Zero" would be much, much more appropriate.

The "Intel CPU fundamental design defects uncovered by Google" is more like it.

"Intel CPU deliberate design defects now uncovered by Google"

Re: Intel Security Issue Update: Addressing Reboot Issues

#79
post #61

Earlier quoted context omitted.

There are issues with this 'laptop' (don't put it on your lap is one), but AMD is a viable option I think.. https://imgur.com/Qsodtxv

> There are issues with this 'laptop' (don't put it on your lap is one) ouch, that is definitiv not a good issue... but well my mbp late 2013" gets hot as well.

Hm? The screenshot was merely showing the good parts (8 cores, 16 virtual).

It's not getting particularly hot in general, entirely depends on the use case. When I max out the cores or run a game? Quite hot. Otherwise: Mostly fine..

It's just unwieldy, big and heavy, hence not really useful on a lap..

Re: Intel Security Issue Update: Addressing Reboot Issues

#80

Earlier quoted context omitted.

I think that's mainly out of luck. If the exploit had been discovered two years later, the story would likely be different. Apple has been much more ambitious with their ARM processor designs and has shipping iOS and AppleTV products affected by Meltdown. Shipping or not, it illustrates, that Intel was not unique.

Now can you argue that the given faulty design was not directly influenced by Intel conscious and deliberate bad decisions ?

I'm not sure what kind of answer you are expecting. All I am saying is that Intel is not uniquely in the wrong here. There is a whole industry of bad decisions. Whether the decisions were conscious, or only obvious in hindsight I can't say.
Post reply on HN