Re: Ryzen issues on FreeBSD ? (with sort of workaround)

Hi! > Well, another lockup. This time after ~ 10 days of uptime. Box was idle > at the time and just a solid freeze. Here's another datapoint: No lockups/problems with: AMD Ryzen Threadripper 2950X Board: PRIME X399-A (not the -PRO) BIOS from 10/12/2018 running: 13.0-CURRENT r340445 up 19 days,

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 04/12/2018 18:26, Mike Tancsa wrote: I think I will downgrade the box that was having issues to RELENG11 to see if the problem is there too.  Unfortunately, the issue took ~ 10 days to show itself My issues showed up on releng 11 as well as releng 12 - I didnt ry the last 11 stable for

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 12/4/2018 12:39 PM, Nimrod Levy wrote: > Just to throw another datapoint out there, I've been running on my > Asus prime b350+ ryzen 5 and I've been stable since the microcode > updates over the summer. I believe I returned all the bios settings > (cstates, memory timing, etc..) back to stock.

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

Just to throw another datapoint out there, I've been running on my Asus prime b350+ ryzen 5 and I've been stable since the microcode updates over the summer. I believe I returned all the bios settings (cstates, memory timing, etc..) back to stock. I've had to shutdown and relocate (and reconfigure

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 04/12/2018 15:04, Mike Tancsa wrote: Well, another lockup. This time after ~ 10 days of uptime. Box was idle at the time and just a solid freeze. This is an ASUS PRIME X370-PRO running BIOS from 09/07/2018 (latest).  Not sure if BIOS related or OS related. I have another motherboard (MSI)

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 11/26/2018 11:30 AM, Mike Tancsa wrote: > On 11/26/2018 11:25 AM, Pete French wrote: >> Foolwing up an old thread I know, but my ssystem ahs been pretty >> stable until recently, when it started locking up about one a week at >> least. This co-incided with me doing two things to it: >> >

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 26/11/2018 16:30, Mike Tancsa wrote: Interesting, I too have noticed my one test box have the odd lockup.  I think it started around the BETA series. Is it possible something "undid" one of the fixes ? I brought the box in question upto 12.0-PRERELEASE FreeBSD 12.0-PRERELEASE r340724 and

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 26/11/2018 16:28, Eric van Gyzen wrote: My Ryzen has never run 11, but I have never seen a single problem on 12. As you suggest, it's probably due to the particular hardware combination. If updating the BIOS doesn't help, I agree that lowering the memory clock is the best next step. I

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 11/26/2018 11:25 AM, Pete French wrote: > Foolwing up an old thread I know, but my ssystem ahs been pretty > stable until recently, when it started locking up about one a week at > least. This co-incided with me doing two things to it: > Interesting, I too have noticed my one test box have the

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 11/26/18 10:25 AM, Pete French wrote: > Foolwing up an old thread I know, but my ssystem ahs been pretty stable > until recently, when it started locking up about one a week at least. > This co-incided with me doing two things to it: > > 1) Doubling the amount of RAM in it to 16 gig, using RAM

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

Foolwing up an old thread I know, but my ssystem ahs been pretty stable until recently, when it started locking up about one a week at least. This co-incided with me doing two things to it: 1) Doubling the amount of RAM in it to 16 gig, using RAM which runs a bit faster than the original

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

So, having been stable for quite sme time, I have had three lockups on my Ryzen in the last week. two were whilst I was in X11, but one happened over the weekend whilst I was looged out, and thus I could get a screenshot of what was on the console when I got in this morning:

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

I just brought everything upto date and re-tested and same issue. FreeBSD 11.2-STABLE #1 r336761 # mount | grep -v zfs devfs on /dev (devfs, local, multilabel) linprocfs on /compat/linux/proc (linprocfs, local) linsysfs on /compat/linux/sys (linsysfs, local) tmpfs on /compat/linux/dev/shm

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 7/27/2018 10:38 AM, Konstantin Belousov wrote: >> >> This is stock FreeBSD image r335560. > By stock you mean that no patches were applied, right ? > Correct, just the regular tree, no patches and nothing in /etc/sysctl.conf and loader.conf just has # cat /boot/loader.conf

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Fri, Jul 27, 2018 at 10:09:35AM -0400, Mike Tancsa wrote: > On 7/27/2018 10:00 AM, Pete French wrote: > > pkg install linux_base-c7 > > Same deal here > > 0{ryzenbsd11}# /compat/linux/bin/bash > Segmentation fault (core dumped) > 139{ryzenbsd11}# > > > This is stock FreeBSD image r335560.

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 7/27/2018 10:00 AM, Pete French wrote: > pkg install linux_base-c7 Same deal here 0{ryzenbsd11}# /compat/linux/bin/bash Segmentation fault (core dumped) 139{ryzenbsd11}# This is stock FreeBSD image r335560. 0{ryzenbsd11}# /compat/linux/bin/bash Segmentation fault (core dumped)

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 27/07/2018 14:10, Mike Tancsa wrote: I havent used the linux emulator in ages. What is the easiest way to try this out ? in rc.conf have linux_enable="YES" when you boot. then pkg install linux_base-c7 /compat/linux/bin/bash and you should see a bash pprompt

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

I highly doubt that this can be related. Well, yes, it suroprised me too :-) Admittedly I dont have a very big samle set - I nly have one Ryzen box and a pair of Epyc boxes in Azure. but I cant make it run on any of them. I take the same OS and run it on Intel and its fine (literally I am

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 7/27/2018 7:01 AM, Pete French wrote: > So, I have been running the patched kernel for quiet a while now, and it > works fine for me, but last night I did hit a surprising issue - the > Linux emulator does not work on Ryzen / Epyc. I tried this on two > machines (both with the patches) and it

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Fri, Jul 27, 2018 at 12:01:09PM +0100, Pete French wrote: > So, I have been running the patched kernel for quiet a while now, and it > works fine for me, but last night I did hit a surprising issue - the > Linux emulator does not work on Ryzen / Epyc. I tried this on two > machines (both

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

So, I have been running the patched kernel for quiet a while now, and it works fine for me, but last night I did hit a surprising issue - the Linux emulator does not work on Ryzen / Epyc. I tried this on two machines (both with the patches) and it coredumps when simply running bash on both of

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Thu, Jul 05, 2018 at 02:58:29PM +0100, Pete French wrote: > > Which other files ? > > sys/x86/include/specialreg.h and sys/x86/x86/cpu_machdep.c > > Those are in your original patch as well as the change > to sys/amd64/amd64/initcpu.c, but your email earlier only > patches

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> This is true, but absolutely irrelevant. > > Modern CPUs have hundreds, if not thousands, MSR registers. Only some of > them define architectural state, and saved/restored on the context switches. > Chicken bits are global knobs not relevant to the vmm entry. That actually makes far more

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Thu, Jul 05, 2018 at 02:23:15PM +0100, Pete French wrote: > > > On 05/07/2018 11:47, Konstantin Belousov wrote: > > Why do you state that they are saved/restored ? What is the evidence ? > > >

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 05/07/2018 11:47, Konstantin Belousov wrote: Why do you state that they are saved/restored ? What is the evidence ? https://software.intel.com/en-us/blogs/2009/06/25/virtualization-and-performance-understanding-vm-exits specificly... 3) "Save MSRs in the VM-exit MSR-store area." and

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Thu, Jul 05, 2018 at 11:43:29AM +0100, Pete French wrote: > > It does not make any sense to even try to access the chicken bits > > MSRs when running under virtualization. It is the duty of the > > hypervisor to configure hardware. > > I would tend to agree with you :-) I was kind of

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> It does not make any sense to even try to access the chicken bits > MSRs when running under virtualization. It is the duty of the > hypervisor to configure hardware. I would tend to agree with you :-) I was kind of surprised to read that they are actually saved and restored as part of a VM

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Thu, Jul 05, 2018 at 11:13:10AM +0100, Pete French wrote: > So, I got my first lockup in weeks, testing with the latest stable > and the patch which sets the kernel bits. But I cant say it its > Ryzen related or not. > > Meanwhile I also got access to an Epyc server in Azure. Am also > runing

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

So, I got my first lockup in weeks, testing with the latest stable and the patch which sets the kernel bits. But I cant say it its Ryzen related or not. Meanwhile I also got access to an Epyc server in Azure. Am also runing the latest STABLE on that tp see how it goes. Interesting thing there is

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 03/07/2018 11:09, Konstantin Belousov wrote: On Tue, Jul 03, 2018 at 10:27:06AM +0100, Pete French wrote: It is very likely that the latest microcode sets the chicken bits for the known erratas already. AFAIK, this is the best that a ucode update can typically do anyway. I just did

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Tue, Jul 03, 2018 at 10:27:06AM +0100, Pete French wrote: > > > It is very likely that the latest microcode sets the chicken bits for the > > known erratas already. AFAIK, this is the best that a ucode update > > can typically do anyway. > > > > I just did some testing - it does do these

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

It is very likely that the latest microcode sets the chicken bits for the known erratas already. AFAIK, this is the best that a ucode update can typically do anyway. I just did some testing - it does do these bits: cpucontrol -m '0xc0011029|=0x2000' $x cpucontrol -m

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Sun, Jul 01, 2018 at 11:15:56AM +0100, Pete French wrote: > > This should be the kernel patch equivalent to the script. > > Ah, thankyou. I shall give this a try on tuesday when I am > physically back in front of the machine. I have been trying without > the oath as you asked by the way, and

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> This should be the kernel patch equivalent to the script. Ah, thankyou. I shall give this a try on tuesday when I am physically back in front of the machine. I have been trying without the oath as you asked by the way, and with the latest microcode update (0x8001137) it also seems stable,

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> % sudo x86info -a | grep Microcode > Microcode patch level: 0x8001136 > > Without that script, the system would lockup up to 5-6 times a day. > Now running without any lockup at all for 3 days, with all kinds > of workload from idle to torture tests. Too early to tell, but it > looks good for

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Tue, Jun 26, 2018 at 01:32:01PM +0100, Pete French wrote: > the dmesg wraps around if I boot verbosely, but heres the contnets of > /var/log/messages from the time it starts to where it stops > talking about CPU specific stuff... if you need something else then > let me know - this is an easy

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 06/26/18 13:29, Konstantin Belousov wrote: > On Tue, Jun 26, 2018 at 11:31:26AM +0100, Pete French wrote: >>> On 06/18/2018 09:34, Pete French wrote: Preseumably in the slightly longer term these workarounds go into the actual kernel if it detects Ryzen ? >>> >>> Yes, Kostik said he

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

Gah! I my memory said it was /var/boot - so close :-) Thanks! On 26/06/2018 15:22, Freddie Cash wrote: On Tue, Jun 26, 2018, 5:33 AM Pete French, > wrote: > Also, please show the 100 first lines of the verbose boot dmesg on this > machine.

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Tue, Jun 26, 2018, 5:33 AM Pete French, wrote: > > > Also, please show the 100 first lines of the verbose boot dmesg on this > > machine. > > the dmesg wraps around if I boot verbosely, but heres the contnets of > /var/log/messages from the time it starts to where it stops > talking about CPU

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> If you run without the script, with the same settings, do you experience > problems ? I have not tried this since the last BIOPS update which brought with it the latest AEGSA version. Previously the machine would lock uop if I enabled SMT though which is why looking at those settings and cross

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Tue, Jun 26, 2018 at 11:31:26AM +0100, Pete French wrote: > > On 06/18/2018 09:34, Pete French wrote: > > > Preseumably in the slightly longer term these workarounds go into the > > > actual kernel if it detects Ryzen ? > > > > Yes, Kostik said he would code this into the kernel after he gets

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> On 06/18/2018 09:34, Pete French wrote: > > Preseumably in the slightly longer term these workarounds go into the > > actual kernel if it detects Ryzen ? > > Yes, Kostik said he would code this into the kernel after he gets enough > feedback. So, I've been running with the sysctl and cputl

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 06/18/2018 09:34, Pete French wrote: > Preseumably in the slightly longer term these workarounds go into the > actual kernel if it detects Ryzen ? Yes, Kostik said he would code this into the kernel after he gets enough feedback. Eric ___

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 18/06/2018 14:59, Mike Tancsa wrote: FYI, both my Epyc and Ryzen system have been running 2+ days with the tests that would normally hard lock the system in 5-60 min. The combo of Microcode updates and system settings Thats for the update - I turned all the default motherboard settings

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 6/14/2018 6:30 AM, Pete French wrote: >> Check out this thread on current. I re-ran the tests I did in Feb to >> lockup the Ryzen box, and they are ok now with the latest micro code >> updates from AMD. I will let the tests run a good 48hrs, but in the >> past it would only take 5-10 min to

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> Check out this thread on current. I re-ran the tests I did in Feb to > lockup the Ryzen box, and they are ok now with the latest micro code > updates from AMD. I will let the tests run a good 48hrs, but in the > past it would only take 5-10 min to cause a hard lockup > >

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

Any idea when that microcode was published? I updated to the latest BIOS last time I saw a lockup and I've been stable for 30 days which I think is a new record for this system. I installed the port to update the microcode and it showed that I already had the latest version, so I assume it came

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 6/2/2018 4:53 AM, Pete French wrote: > So,I notice that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 was > closes as fixed. I cant remember if there was another bug report for ongoing > Ryzen issues at all - I have been experimenting and have re-enabled most of > the BIOS setting

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 03/06/2018 18:49, Mike Tancsa wrote: I have c-states disabled on the ryzen both for FreeBSD and Linux. To disable SMP on the Epyc doesnt seem to be possible. But then again kill off 31 cores is a heavy cost to pay for stability :( When I am back at the office, I will see if a recent

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 6/3/2018 1:10 PM, Pete French wrote: > >> The compile bug has been fixed for me.  However, last I checked I can >> still freeze a system by generating a lot of network traffic between VMs >> in either bhyve or virtbox.  Its been a while since I tested (couple of >> months) but I dont recall

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

The compile bug has been fixed for me. However, last I checked I can still freeze a system by generating a lot of network traffic between VMs in either bhyve or virtbox. Its been a while since I tested (couple of months) but I dont recall anything obviously committed that highlighted that

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

For my case, it's been a while since I fiddled with any thing. From memory, the last time I worked on this, I updated to the latest BIOS on the Asus prime b350+ leaving the settings we've talked about here at stock (c-states, memory clock, etc...), updated to 11-stable, and let things run for a

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 6/2/2018 7:48 PM, Don Lewis wrote: > On 2 Jun, Pete French wrote: >> So,I notice that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 was >> closes as fixed. I cant remember if there was another bug report for ongoing >> Ryzen issues at all - I have been experimenting and have

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 2 Jun, Pete French wrote: > So,I notice that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 was > closes as fixed. I cant remember if there was another bug report for ongoing > Ryzen issues at all - I have been experimenting and have re-enabled most of > the BIOS setting and tweaks

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

So,I notice that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 was closes as fixed. I cant remember if there was another bug report for ongoing Ryzen issues at all - I have been experimenting and have re-enabled most of the BIOS setting and tweaks fne, but I still need SMP disbled or it

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 4/24/2018 8:04 PM, Don Lewis wrote: >> >> I was able to lock it up with vbox. bhyve was just a little easier to >> script and also I figured would be good to get VBox out of the mix in >> case it was something specific to VBox. I dont recall if I tried it >> with SMT disabled. Regardless, on

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

It would be interesting to test other AMD CPUs. I think AMD and Intel have some differences in the virtualization implementations. I've been using AMD CPU's pretty extensively since the early 90's - back then I was running NeXTStep and out of the three Intel alternatives it was the only

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 24 Apr, Mike Tancsa wrote: > On 4/24/2018 10:01 AM, Pete French wrote: >> >> Well, I ranh the iperf tests between real machine for 24 hours and that >> worked fine. I also then spun up a Virtualbox with Win10 in it, and ran >> iuperf to there at the same time as doing it betwene real machines,

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

yes, I too think its definitely a Ryzen isssue with FreeBSD - is there a way you could try it (at least on the Desktop) with SMT off ? I havbe the following options tunred off: SMT Glocal C states Cool-n-quiet Core boost The last few obviously tweak

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 4/24/2018 10:01 AM, Pete French wrote: > > Well, I ranh the iperf tests between real machine for 24 hours and that > worked fine. I also then spun up a Virtualbox with Win10 in it, and ran > iuperf to there at the same time as doing it betwene real machines, and > also did a full virus scan to

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 24/04/2018 14:56, Mike Tancsa wrote: I was doing the tests with bhyve, and the iperf tests were between VMs on the same box. That seems to trigger it fairly quickly. The Epyc took a bit more work, but I could reliable do it there too. Well, I ranh the iperf tests between real machine for

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 4/23/2018 8:19 AM, Pete French wrote: > > All worked fine until just no,w when it did lockup. But the lockup > happened when I fired up VirtualBox as well on the Ryzen machine, had that > doing a lot of disc activity and also did a lot of ZFS activity on the box > itself. Which I find

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 23 Apr, Mike Tancsa wrote: > On 4/22/2018 5:29 PM, Don Lewis wrote: >> Pretty much all of my BIOS settings are the defaults. >> >> I suspect that the idle hang issues are motherboard and/or BIOS >> specific. For the record my motherboard is a Gigabyte >> GA-AX370-Gaming 5. > Hi Don, >

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 4/22/2018 5:29 PM, Don Lewis wrote: > Pretty much all of my BIOS settings are the defaults. > > I suspect that the idle hang issues are motherboard and/or BIOS > specific. For the record my motherboard is a Gigabyte > GA-AX370-Gaming 5. Hi Don, Any chance you could try that bhyve test

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> fairly pleased with that. Am going to try the test case that Mike Tancsa > posted to see if I can get it to lockup today though,. now that I am in > front of it to reset of required. Will report results either way... So, I have been ran the iperf scripts all day (about 4 hours now) with the

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> I have a Ryzen system > parts: https://pcpartpicker.com/list/HhycYT > dmesg: http://dmesgd.nycbug.org/index.cgi?do=view=3516 > > which I have been using for months without issue and on completely > default settings. Thats encouranging -= and I think you are the first person to report that

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> And of course now that we say something about it, I get a lockup > overnight... Sods law I guess. Mine survived the weekend quite happily though, so am fairly pleased with that. Am going to try the test case that Mike Tancsa posted to see if I can get it to lockup today though,. now that I am

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 20 Apr, Pete French wrote: > So, resurrecting the thread from a few weeks ago, as I finally found > time yesterday to out together the Ryzen machine I bought the parts for in > Jaunary (busy year at work). All went smoothl;y, checked it > booted up, used it for 15 minutes, was impressed by

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

And of course now that we say something about it, I get a lockup overnight... -- Nimrod On Fri, Apr 20, 2018 at 7:48 AM Nimrod Levy wrote: > I'm really glad to see that I'm not the only one still interested in this > thread. I don't really have anything new to contribute.

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 20 April 2018 at 04:15, Pete French wrote: > So, resurrecting the thread from a few weeks ago, as I finally found > time yesterday to out together the Ryzen machine I bought the parts for in > Jaunary (busy year at work). All went smoothl;y, checked it > booted

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

> Its not just the Ryzen, I can lock up Epyc CPUs as well. They take a bit > longer, but its not that hard to repeat. Unfortunately, I had to > allocate this hardware over the Linux where it works reliably under all > workloads without any such lock ups with all the default BIOS settings :( AH,

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

Its not just the Ryzen, I can lock up Epyc CPUs as well. They take a bit longer, but its not that hard to repeat. Unfortunately, I had to allocate this hardware over the Linux where it works reliably under all workloads without any such lock ups with all the default BIOS settings :( Here is a

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

To be honest, I can't remember for certain what's set in the BIOS right now. The last post I made was from 3/17 and it says I have the memory clock lowered and c-states disabled. I don't think I've changed anything but the build of stable since then. -- Nimrod On Fri, Apr 20, 2018 at 7:55 AM

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 20/04/2018 12:48, Nimrod Levy wrote: I'm really glad to see that I'm not the only one still interested in this thread.  I don't really have anything new to contribute. I've been getting about a week or so uptime out of my box. My habit has been to see if it hangs, then reboot and rebuild

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

I'm really glad to see that I'm not the only one still interested in this thread. I don't really have anything new to contribute. I've been getting about a week or so uptime out of my box. My habit has been to see if it hangs, then reboot and rebuild latest stable and reboot and run that for a

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

So, resurrecting the thread from a few weeks ago, as I finally found time yesterday to out together the Ryzen machine I bought the parts for in Jaunary (busy year at work). All went smoothl;y, checked it booted up, used it for 15 minutes, was impressed by the speed and went home. ...and by

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 02/12/2018 21:54, Peter Moody wrote: >> I'm having really good luck with the kernel patch attached to this >> message: >> https://docs.freebsd.org/cgi/getmsg.cgi?fetch=417183+0+archive/2018/freebsd-hackers/20180211.freebsd-hackers > > I'm new to this; what are the chances that this gets into

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On Mon, Feb 12, 2018 at 1:49 PM, Don Lewis wrote: > On 31 Jan, Eugene Grosbein wrote: >> 31.01.2018 4:36, Mike Tancsa пишет: >>> On 1/30/2018 2:51 PM, Mike Tancsa wrote: And sadly, I am still able to hang the compile in about the same place. However, if I set

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 2/12/2018 4:49 PM, Don Lewis wrote: > On 31 Jan, Eugene Grosbein wrote: >> 31.01.2018 4:36, Mike Tancsa пишет: >>> On 1/30/2018 2:51 PM, Mike Tancsa wrote: And sadly, I am still able to hang the compile in about the same place. However, if I set >>> >>> >>> OK, here is a sort of

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 31 Jan, Eugene Grosbein wrote: > 31.01.2018 4:36, Mike Tancsa пишет: >> On 1/30/2018 2:51 PM, Mike Tancsa wrote: >>> >>> And sadly, I am still able to hang the compile in about the same place. >>> However, if I set >> >> >> OK, here is a sort of work around. If I have the box a little more

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

Mine was running so well. I had almost 3 weeks of uptime before it locked up twice last night. On Thu, Feb 8, 2018 at 10:24 PM Peter Moody wrote: > to close the loop on this thread (for me at least); I replaced the > asrock ab350 with an msi x370 and things now, just work

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

to close the loop on this thread (for me at least); I replaced the asrock ab350 with an msi x370 and things now, just work (c). the msi detects the memory as 2133 (rather than the 3000 mhz it was sold as). i'm not sure if this because it really is 2133 mhz, or because the msi just likes that

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 2/1/2018 1:49 PM, Mike Tancsa wrote: > On 2/1/2018 1:40 PM, Ed Maste wrote: >>> root@amdtestr12:/home/mdtancsa # procstat -kk 6067 >>> PIDTID COMMTDNAME KSTACK >>> >>> 6067 100865 python2.7 - ??+0 ??+0 ??+0 ??+0 >>> ??+0 ??+0 ??+0

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 2/1/2018 1:40 PM, Ed Maste wrote: >> root@amdtestr12:/home/mdtancsa # procstat -kk 6067 >> PIDTID COMMTDNAME KSTACK >> >> 6067 100865 python2.7 - ??+0 ??+0 ??+0 ??+0 >> ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > > I think this part is due to

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 30 January 2018 at 19:48, Mike Tancsa wrote: >> > I also just tried upgrading to the latest HEAD with a generic kernel and > same / similar lockups although procstat -kk gives some odd results > > > root@amdtestr12:/home/mdtancsa # procstat -kk 6067 > PIDTID COMM

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 1/31/2018 8:33 AM, Eugene Grosbein wrote: > 31.01.2018 4:36, Mike Tancsa пишет: >> On 1/30/2018 2:51 PM, Mike Tancsa wrote: >>> >>> And sadly, I am still able to hang the compile in about the same place. >>> However, if I set >> >> >> OK, here is a sort of work around. If I have the box a

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

31.01.2018 4:36, Mike Tancsa пишет: > On 1/30/2018 2:51 PM, Mike Tancsa wrote: >> >> And sadly, I am still able to hang the compile in about the same place. >> However, if I set > > > OK, here is a sort of work around. If I have the box a little more busy, > I can avoid whatever deadlock is

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

If you want to use an operating system that takes advantage of CPU to memory optimizations without taking steps backwards you have to pay a price. Sent from my Verizon, Samsung Galaxy smartphone Original message From: Don Lewis Date: 1/30/18 4:58 PM

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 30 Jan, Mike Tancsa wrote: > On 1/30/2018 5:23 PM, Nimrod Levy wrote: >> That's really strange. I never saw those kinds of deadlocks, but I did >> notice that if I kept the cpu busy using distributed.net >> I could keep the full system lockups away for >> at least a

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 1/30/2018 5:23 PM, Nimrod Levy wrote: > That's really strange. I never saw those kinds of deadlocks, but I did > notice that if I kept the cpu busy using distributed.net > I could keep the full system lockups away for > at least a week if not longer. > > Not to keep

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 30 Jan, Mike Tancsa wrote: > On 1/30/2018 2:51 PM, Mike Tancsa wrote: >> >> And sadly, I am still able to hang the compile in about the same place. >> However, if I set > > > OK, here is a sort of work around. If I have the box a little more busy, > I can avoid whatever deadlock is going on.

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

That's really strange. I never saw those kinds of deadlocks, but I did notice that if I kept the cpu busy using distributed.net I could keep the full system lockups away for at least a week if not longer. Not to keep harping on it, but what worked for me was lowering the memory speed. I'm at 11

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 1/30/2018 2:51 PM, Mike Tancsa wrote: > > And sadly, I am still able to hang the compile in about the same place. > However, if I set OK, here is a sort of work around. If I have the box a little more busy, I can avoid whatever deadlock is going on. In another console I have cat