Re: Current status of Ryzen (non-)support
Sent from my iPhone
> On Oct 22, 2018, at 6:00 PM, Hannes Hauswedell wrote:
>
>> On 21.10.18 19:33, Konstantin Belousov wrote:
>>> On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote:
>>> Hi everyone,
>>>
>>> I wanted to ask what the current status of Ryzen support is and/or
>>> whether any new changes are planned.
>>>
>>> My situation:
>>> * second generation Ryzen: 2600X
>>> * running -CURRENT
>>> * I have done the things described here:
>>> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html
>> This was based on the public errata document for the first gen ryzen.
>> I am not aware of the erratas ('revision guides' in AMD terminology)
>> for the second gen ryzens.
Coming in a little late on this thread, just upgraded my 10 year old system to
an AMD Ryzen 5 2400G. I noticed that the link below, and alluded to in the
above pipermail link, does mention the 2nd gen Ryzen processors. Apologies if
I misunderstood the above response.
https://developer.amd.com/wp-content/resources/55449_1.12.pdf
Also, my cpuid (Id=0x810f10 Family=0x17 Model=0x11) isn't mentioned in the
above errata, so I guess it's not quite up to date for more recent 2nd gen
Ryzen, even though the 2400G was released months before the dated errata.
I've not applied any of the sysctls mentioned in the above email, but have
updated my BIOS to the latest (ASUS X470-PRO). I've not experienced any
problems in several j8 buildworlds or poudriere runs (building roughly 1000
ports).
--
DE
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current status of Ryzen (non-)support
On 21.10.18 19:33, Konstantin Belousov wrote:
> On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote:
>> Hi everyone,
>>
>> I wanted to ask what the current status of Ryzen support is and/or
>> whether any new changes are planned.
>>
>> My situation:
>> * second generation Ryzen: 2600X
>> * running -CURRENT
>> * I have done the things described here:
>> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html
> This was based on the public errata document for the first gen ryzen.
> I am not aware of the erratas ('revision guides' in AMD terminology)
> for the second gen ryzens.
>
> For now you can only get fixes for microcode from your BIOS updates.
>
Thanks for the replies everyone! I ran
stress-ng --vm 12 --vm-bytes 12G --verify -v
and could reproducibly produce memory issues on FreeBSD, but not on Linux.
After updating the BIOS and deactivating swap on FreeBSD they seem to be
gone now, I am still investigating whether turning swap back on brings
them back which would hint at a possible disk problem or whether the
BIOS update changed this behaviour. Disk initially appeared more
plausible, but further tests suggest against it (it's a fairly new SSD,
multiple ZFS scrubs show now errors, there are no smart errors or other
errors reported by the kernel in regard to the disk).
Best regards,
Hannes
--
pgp-key: https://hannes.hauswedell.net/hannes_hauswedell_public_key.asc
fingerprint: EF56 F66A A683 3E32 CE05 3F55 6F9F 2E30 ECB3 7977
signature.asc
Description: OpenPGP digital signature
Re: Current status of Ryzen (non-)support
On Sun, Oct 21, 2018 at 7:09 PM, Hannes Hauswedell wrote: Hi everyone, I wanted to ask what the current status of Ryzen support is and/or whether any new changes are planned. My situation: * second generation Ryzen: 2600X * running -CURRENT * I have done the things described here: https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html * no full system freezes, but under load, e.g. building with 12 threads, programs start to segfault. * memtest86 ran through without issues * on a Linux dual boot I haven't had any issues Is this a known problem? Anythings I can do about it? I thought the Ryzen problem were only supposed to happen with first generation CPUs... First gen (R7 1700) here, overclocked to 3.9GHz, also running CURRENT — never had any unexpected segfaults, even when building with 16 threads. The only bug is that the bottom (chipset) PCIe slot breaks when an NVMe SSD is installed / chipset USB3 ports don't work: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231923 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current status of Ryzen (non-)support
On Sun, 21 Oct 2018 18:09:50 +0200 Hannes Hauswedell wrote: > I wanted to ask what the current status of Ryzen support is and/or > whether any new changes are planned. > > My situation: > * second generation Ryzen: 2600X > * running -CURRENT > * I have done the things described here: > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > * no full system freezes, but under load, e.g. building with 12 > threads, programs start to segfault. > * memtest86 ran through without issues > * on a Linux dual boot I haven't had any issues > > 1300X (25 week), 2200G, 2700X - OK on 11.2 I do not apply any fixes provided by @kib in "Ryzen public erratas". Mine FreeBSD configs and tunings: http://www.netlab.linkpc.net/download/software/os_cfg/FBSD/11.2/base/ http://www.netlab.linkpc.net/download/software/os_cfg/FBSD/11.2/wks/ Asrock Taichi x370 have strange proublems with PCI-e devices on BIOS ver > 4.60: after load any smbus drivers pcie stop work or do it very strange. Also with PinnaclePI-AM4_1.0.0.5 mine amdtemp driver read strange temperature, @cem should know more about this. http://forum.asrock.com/forum_posts.asp?TID=9833=56770 Last time I have segfaults on bad mem modules contacts (fix: clean and reinstall) and mine coller do many pressure. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current status of Ryzen (non-)support
On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote:
> Hi everyone,
>
> I wanted to ask what the current status of Ryzen support is and/or
> whether any new changes are planned.
>
> My situation:
> * second generation Ryzen: 2600X
> * running -CURRENT
> * I have done the things described here:
> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html
This was based on the public errata document for the first gen ryzen.
I am not aware of the erratas ('revision guides' in AMD terminology)
for the second gen ryzens.
For now you can only get fixes for microcode from your BIOS updates.
> * no full system freezes, but under load, e.g. building with 12 threads,
> programs start to segfault.
> * memtest86 ran through without issues
> * on a Linux dual boot I haven't had any issues
Or look at the Linux sources and see if any workarounds are applied
and chicken bits are set for your CPU.
>
> Is this a known problem? Anythings I can do about it? I thought the
> Ryzen problem were only supposed to happen with first generation CPUs...
>
> Thanks and regards,
> Hannes
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Current status of Ryzen (non-)support
Hi everyone, I wanted to ask what the current status of Ryzen support is and/or whether any new changes are planned. My situation: * second generation Ryzen: 2600X * running -CURRENT * I have done the things described here: https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html * no full system freezes, but under load, e.g. building with 12 threads, programs start to segfault. * memtest86 ran through without issues * on a Linux dual boot I haven't had any issues Is this a known problem? Anythings I can do about it? I thought the Ryzen problem were only supposed to happen with first generation CPUs... Thanks and regards, Hannes signature.asc Description: OpenPGP digital signature
