It seems to be confirmed as a hardware problem. See:
I have entered in contact with AMD and am doing an RMA of my CPU in the
next days. From what I could grasp the bug is usual in the first batches
of Ryzen, so there might be many affected CPUs in the wild. AMD is not
issuing a recall, it will treat with it in a case by case basis.
Anyone can check if their CPU has the problem by running the kill-
ryzen.sh script described in the original bug report. If your CPU has
the problem contact AMD technical support using the link in the Phoronix
article linked above.
Maybe I should mark this bug as invalid? At least the bug report will
remain here so that other affected Ubuntu users may find out how to
** Tags added: kernel-bug-exists-upstream
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Long, multi-threaded compilations, segfault in Ryzen
Status in linux package in Ubuntu:
I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM
(Corsair LPX 2400). If I do a very intensive multi-threaded
compilation session sometimes I get a segfault. This seems to be a
problem with Ryzen it self nad maybe it is related to the bug
described in bug #1690085 but I believe it is not the same. This bug
affects many Linux users with Ryzen, see for example this thread in
the AMD forum:
https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo
Wiki that talks about this problem in the Troubleshoting section of
their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting
It is also very easy to verify if you have a processor with the
problem. Fortunately some smart people have created a simple script
that always shows the problem in my system and in the systems of the
other people of the thread. The script can be found in
You just have to clone the repository using git, move to the ryzen-
test directory and run ./kill_ryzen.sh. It is a very simple script, it
downloads gcc-7.1 source code into a vram disk and start #processors
simultaneous compilation of it. If any compilation fails it writes a
message in the console saying how long it took to get the failure.
After a few minutes, the build in my system fails unless I turn off
SMT. With SMT off it can take many hours, but still fails in less than
I am opening this bug report because I believe we should try to verify if
this is a widespread problem and inform potential users of the problems.
Hopefully AMD or the Kernel developers can find a workaround. I have also
already opened a bug report in the Linux Kernel Bugzilla
(https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is
not calling the attention of the kernel developers.
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id',
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path',
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c',
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p',
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p',
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-05-30 (63 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
enp33s0 no wireless extensions.
lo no wireless extensions.
MachineType: Micro-Star International Co., Ltd MS-7A34
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash
ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Uname: Linux 4.10.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video
dmi.bios.vendor: American Megatrends Inc.
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 TOMAHAWK (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.sys.vendor: Micro-Star International Co., Ltd
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp