To: ShadowAce; SunkenCiv
Debian believes all OS affected!
That would be windows and Macs!
A microcode problem of some sort.
To: Ernest_at_the_Beach
Some of my reading suggests that it is mainly a laboratory bug not being seen in the wild.
To: Ernest_at_the_Beach
So now we can use the excuse.... THE COMPUTER MADE A MISTAKE ?
4 posted on
06/26/2017 8:51:44 AM PDT by
UCANSEE2
(Lost my tagline on Flight MH370. Sorry for the inconvenience.)
To: Ernest_at_the_Beach; Swordmaker
The Debian Operating System is free — sometimes you get what you pay for.
5 posted on
06/26/2017 8:51:58 AM PDT by
House Atreides
(Send BOTH Hillary & Bill to prison.)
To: Ernest_at_the_Beach
how do you tell what processor you have? Mine is a couple years old- 6 or 8 core- can’t remember which- hpelite 190t- how do i find out wehat core?
10 posted on
06/26/2017 9:12:15 AM PDT by
Bob434
To: Ernest_at_the_Beach
I checked, my PC (running on Debian derivative, Linux Mint) has a Sandy Bridge 2nd gen i3. Three generations back.
Linux users can find their processor info at /proc/cpuinfo
To: Ernest_at_the_Beach
The fact that Intel has released microcode updates to both Skylake and Kaby Lake CPU's means that we may not see this problem if you're running Windows 10, since Intel will likely offer a patch for Windows 10 users to correct this problem which might be pushed out under the Windows Update system.
15 posted on
06/26/2017 9:34:01 AM PDT by
RayChuang88
(FairTax: America's Economic Cure)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson