• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Got my RMA'd Ryzen up and going

I was getting segfaults (vsyscall errors) on my 2700x on YAFU and NFS@Home but the issue is not unique to AMD processors. Both projects run apps that are several years old and compiled with "old" versions of gcc. I had installed the most recent version of antergos linux [4.17.3-1-ARCH] and noticed the apps errored out immediately with vsyscall errors (segfaults). I installed the latest version of Linux Mint 19 [4.15.0-24-generic| and did not see the errors. The 1 key thread where this problem was diagnosed and solved is here. Also see this thread on the NFS forum.

The most recent ARCH linux kernels are compiled with the option CONFIG_LEGACY_VSYSCALL_EMULATE=n whereas the most recent ubuntu and mint kernels are compiled with option CONFIG_LEGACY_VSYSCALL_EMULATE=y. To get around this issue on ARCH you can recompile the kernel with CONFIG_LEGACY_VSYSCALL_EMULATE=y or configure the bootloader to use the kernel parameter "vsyscall=emulate".

The reason I was experimenting with different linux distros running the most recent kernels was to simply monitor cpu temperature accurately on my 2700x. The latest kernel on linux mint 19 finally gives me that information. 🙂

mark@x16-linux:~$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +54.2°C (high = +70.0°C)

If you want to stress test your Ryzen check out this link.
 
If you're doing the current sprint project, Universe@Home, I get periodic computation errors there even on the most stable machines.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top