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)

> 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)

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)

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, >

What should do in chrooted environment?

Hi, all I've make buildworld in chrooted environment. But failed at 'stage 4.2: building libraries' [1]: objcopy --only-keep-debug libproc.so.3.full libproc.so.3.debug objcopy --strip-debug --add-gnu-debuglink=libproc.so.3.debug libproc.so.3.full libproc.so.3 sh /usr/src/tools/install.sh -C

Re: What should do in chrooted environment?

On Tue, Apr 24, 2018 at 07:28:06AM +0900, KIRIYAMA Kazuhiko wrote: > Hi, all > > I've make buildworld in chrooted environment. But failed at > 'stage 4.2: building libraries' [1]: > > objcopy --only-keep-debug libproc.so.3.full libproc.so.3.debug > objcopy --strip-debug

Re: What should do in chrooted environment?

> On 24 Apr 2018, at 08:14, Glen Barber wrote: > I think you might not have the devfs mount in the image. With the paths > provided above, I think this should fix it: > > # mount -t devfs devfs /mnt/dev I wonder if it's worth doing a basic sanity check that /dev/null and

Two USB 4 disk enclosure and a panic

Hi, I would like to know how to debug this. I have two 4 disk enclosures: Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure – USB 3.0 & eSATA (HF2-SU3S2) NexStar HX4 - NST-640SU3-BK and both have 4 disk on them, and not all disk are equal. The issue comes when I plug the probox usb3 enclosure on