Live data from Hacker News

Intel Security Issue Update: Addressing Reboot Issues

newsroom.intel.com

41–50 of 129 posts

Re: Intel Security Issue Update: Addressing Reboot Issues

#41
post #11

I just had a hard crash/reboot on a Dell running Windows 10 on an AMD processor, followed by a couple of auto updates. There was no indication of updates being available before the crash.

Out of curiosity, how do you suppose an Intel microcode update caused a blue screen on your system running an AMD processor?

These issues aren't limited to Intel, and the people developing the mitigations are probably sharing ideas with each other.

Re: Intel Security Issue Update: Addressing Reboot Issues

#42
post #16

This is -- to say the least -- frustrating. First, the busted microcode is still available on the Intel Download Center[1], without any warning that they recommend that you not, in fact, install it. Second, the press release is still being evasive: they have not merely "received reports"; they in fact know that it's causing issues, and the press release is avoiding the much stronger language that Intel is giving priv…

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.

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

Re: Intel Security Issue Update: Addressing Reboot Issues

#44

Earlier quoted context omitted.

The fixes weren't widely run until this week.

presumably because Intel does not have access to the necessary hardware configurations to test the fixes on?

I highly doubt this, given how much hardware they appear have lying around to throw at the Linux 0day Test Bot (which does full kernel compiles, boots, and integration tests for dozens of hardware configurations for every patch sent to most LKML lists).

Re: Intel Security Issue Update: Addressing Reboot Issues

#45
post #39
post #37

Earlier quoted context omitted.

>Between Intel's numerous CPU bugs that they refused to refund customers for How do you propose this could work? Are side channel vulnerabilities in CPUs really bugs?

They promise modern process isolation and fail to deliver it. Their fixes reduce performance significantly. IANAL, but that sounds like a defective product.

>They promise modern process isolation and fail to deliver it.

Modern process isolation is not flawless, therefore it is not modern process isolation.

Re: Intel Security Issue Update: Addressing Reboot Issues

#46
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.

They are literally no better.

Re: Intel Security Issue Update: Addressing Reboot Issues

#47
Uhm, what a mess. This, just when Linux vendors began pushing updated intel-microcode packages (Ubuntu just released intel-microcode 3.20180108.0). Should we put the update on hold until this issue is hopefully resolved, or should we still update as suggested in the last paragraph of this Intel press release, somehow believing that the random reboots don't apply to "end users"?

Re: Intel Security Issue Update: Addressing Reboot Issues

#48
post #31
post #15

Earlier quoted context omitted.

more frequent

With the implication that random reboots of a lesser, but non-zero frequency are okay, it's at least expected? Odd wording for sure.

If you have Intel wireless or display drivers installed then it is perfectly normal for a computer to randomly reboot.

Re: Intel Security Issue Update: Addressing Reboot Issues

#49
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.

I'm thinking of building an AMD dev box. For enterprise consumers, if they're using 1U or blade servers, they could make the choice to switch to AMD for future nodes.

Re: Intel Security Issue Update: Addressing Reboot Issues

#50

Earlier quoted context omitted.

The fixes weren't widely run until this week.

presumably because Intel does not have access to the necessary hardware configurations to test the fixes on?

I couldn't accept this as an excuse when you have possibly the worst CPU bug in x86 history, or perhaps all CPU history, with ample of man power and resources, along with 6 months time frame.

Rush isn't a word I would use.

Post reply on HN