Author

Topic: Intel Skylake bug causes PCs to freeze during complex workloads (Read 385 times)

legendary
Activity: 1049
Merit: 1006


How to test your PC for the Skylake bug

http://www.pcworld.com/article/3021023/hardware/how-to-test-your-pc-for-the-skylake-bug.html[/size]

Intel has confirmed a bug in some Skylake CPUs could cause them to lock up under "complex workload conditions" but noted that a fix is on the way. The bug initially was reported only with the Core i7-6700K desktop CPU with Hyper-Threading enabled, but Intel’s confirmation seems to indicates it impacts more CPUs in the lineup.

In a post on Intel's forums, an Intel community manager wrote: "Intel has identified an issue that potentially affects the 6th Gen Intel Core family of products. This issue only occurs under certain complex workload conditions, like those that may be encountered when running applications like Prime95. In those cases, the processor may hang or cause unpredictable system behavior. Intel has identified and released a fix and is working with external business partners to get the fix deployed through BIOS."

The bug has apparently been stewing for weeks on forums at hardwareluxx.de and then Mersenne.org which created the software, Prime95, that is used to induce the bug. Prime95 is used to find prime numbers and is also very popular with performance and the overclocking community as a stress and performance test.

(Read the full article at PCWorld.com to know how to test your PC for this bug.)

Source: PCWorld
legendary
Activity: 1049
Merit: 1006


Intel Skylake bug causes PCs to freeze during complex workloads

http://arstechnica.com/gadgets/2016/01/intel-skylake-bug-causes-pcs-to-freeze-during-complex-workloads/

Intel has confirmed that its Skylake processors suffer from a bug that can cause a system to freeze when performing complex workloads. Discovered by mathematicians at the Great Internet Mersenne Prime Search (GIMPS), the bug occurs when using the GIMPS Prime95 application to find Mersenne primes. We've been informed that the bug was reportedly discovered and tested by the the community at hardwareluxx.de before being passed onto GIMPS, which conducted further testing. Both groups passed their findings onto Intel.

"Intel has identified an issue that potentially affects the 6th Gen Intel Core family of products. This issue only occurs under certain complex workload conditions, like those that may be encountered when running applications like Prime95. In those cases, the processor may hang or cause unpredictable system behaviour."

Intel has developed a fix, and is working with hardware partners to distribute it via a BIOS update. No reason has been given as to why the bug occurs, but it's confirmed to affect both Linux and Windows-based systems. Prime95, which has historically been used to benchmark and stress-test computers, uses Fast Fourier Transforms to multiply extremely large numbers. A particular exponent size, 14,942,209, has been found to cause the system crashes. While the bug was discovered using Prime95, it could affect other industries that rely on complex computational workloads, such as scientific and financial institutions. GIMPS noted that its Prime95 software "works perfectly normal" on all other Intel processors of past generations.

While this particular bug can be fixed via a BIOS update, we are reminded of another famous bug that plagued Intel's original Pentium processor that couldn't be so easily rectified. The Pentium FDIV bug - discovered by Thomas Nicely, a professor of mathematics, on October 19, 1994 - was a floating-point divide problem caused by a circuit design error. While the flaw would rarely have been encountered by average users, extensive media coverage ultimately led to Intel recalling the defective processors.

Mostly recently, Intel's Haswell and early Broadwell processors suffered from a TSX (Transactional Synchronization Extensions) bug. Rather than recall the parts, Intel disabled the TSX instructions via a microcode update delivered via new motherboard firmware.

Source: Ars Technica
Jump to: