Skylake / Kaby Lake Hyper-threading bug

Discussion in 'Hardware Components and Aftermarket Upgrades' started by Assembler, Jun 26, 2017.

  1. hacktrix2006

    hacktrix2006 Notebook Evangelist

    Reputations:
    120
    Messages:
    408
    Likes Received:
    181
    Trophy Points:
    56
    I have always been respectful when I have stepped out of line I have apologised. When I have placed in support tickets I have been polite. In fact I let them know of the issue as soon as I found out and even pointed them the right way to the information. Unless they have said something to you very differently. Yes things have been heated at times but what was meant to be expected after a promise which was the main reason to purchase there product after years of saving up and nearly a year of research.

    At the same time they can't really leave a system in a flawed state either where data loss can occur.

    I can't sell the system as no one will buy it due the resale value being smashed with the MXM issue(s). So either way for me it seems it's a loose loose.

    Sent from my pa_osprey using Tapatalk
     
    Vasudev and hmscott like this.
  2. Papusan

    Papusan BGA Filthy = That sucks!! STAHP! Dont buy FILTH...

    Reputations:
    5,653
    Messages:
    13,879
    Likes Received:
    18,127
    Trophy Points:
    931
    They all would probably fix it, if the problem was similar as Superfish Vulnerability:rolleyes: Loss of data ain't importent enough!! @hmscott @Phoenix :rolleyes:
     
  3. hacktrix2006

    hacktrix2006 Notebook Evangelist

    Reputations:
    120
    Messages:
    408
    Likes Received:
    181
    Trophy Points:
    56
    @Papusan If it was something like SuperFish it would solely depend if the OEM in question was caught out, in case of Lenovo they was caught out so they had no choice but to patch it out due to the up roar. It also not Lenovo first time either being caught out either with something fishy. Just look at their Whitelisting of Wifi cards and charging a premium for the same card as a standard OEM but with a Lenovo ID in the firmware instead that caused a stink and still does to this day.
     
    Vasudev, hmscott and Papusan like this.
Loading...

Share This Page