Article 6HRHK Ryzen News from A to GPU

Ryzen News from A to GPU

by
hubie
from SoylentNews on (#6HRHK)
Ryzen Cpu Bug Crashes PCs Using Firewire Devices, But A Fix Is On The Way

Arthur T Knackerbracket has processed the following story:

A strange bug involving AMD's modern Ryzen CPUs and the old Firewire standard

A Linux patch is on the way to solve crashing issues when attempting to use Firewire devices on PCs running Ryzen CPUs and Linux (via Phoronix). The unlikely hardware combination has enough Linux users to get attention from the community, and even a fix coming out with Linux 6.7 will be backported to prior Linux kernel releases.

Despite all that, Linux developer Takashi Sakamoto has pledged to keep Firewire support on Linux alive until 2029. Sakamoto is already making good on his promise with his latest patch, which solves an issue that uniquely affected PCs running AMD Ryzen CPUs. It would seem incredibly unlikely that anyone would be combining two pieces of hardware with nearly a decade between them, but those people certainly exist. They reported an unusually high amount of crashes.

Without getting too technical, Firewire and Ryzen users would often see their PCs crash if the "isochronous cycle timer" register on the CPU was accessed. This register would be accessed if a user ever plugged in a Firewire device or was using software that required constant access to the register.

[...] Although crashes are no longer a problem for Firewire-Ryzen PCs, the patch is a double-edged sword and "brings apparent disadvantage since time-aware application programs require it," according to Sakamoto. Linux users with this hardware combination might have to switch to Intel or even downgrade to one of AMD's pre-Ryzen CPUs, as neither exhibit the same problems seen on Ryzen-powered PCs.

Read more of this story at SoylentNews.

External Content
Source RSS or Atom Feed
Feed Location https://soylentnews.org/index.rss
Feed Title SoylentNews
Feed Link https://soylentnews.org/
Feed Copyright Copyright 2014, SoylentNews
Reply 0 comments