On 05/30/18 17:50, Glen Barber wrote:
Hi,
Could folks please help boot-test the most recent 12.0-CURRENT amd64
memstick images on various hardware? Note, this is not a request to
install 12.0-CURRENT, only a boot-test with various system knobs
tweaked.
The most recent images are available at:
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-enabl
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 whi
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 iss
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 any
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 chec
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
George Mitchell wrote:
>
> On 06/01/18 21:31, Glen Barber wrote:
> > [...]
> > If you would like to use SVN to do a source based update of an existing=
>
> > system, use the "stable/11" branch.
> > [...]
>
> So what's releng/11.2, chopped liver? -- George
"Chopped liver
On Sun, Jun 3, 2018 at 4:19 PM, Julian H. Stacey wrote:
> George Mitchell wrote:
> >
> > On 06/01/18 21:31, Glen Barber wrote:
> > > [...]
> > > If you would like to use SVN to do a source based update of an
> existing=
> >
> > > system, use the "stable/11" branch.
> > > [...]
> >
> > So what's r
Hello,
Background:
-
System was originally installed with an 11.0 CD. At the time I tried to
get UEFI to work, but ended up booting in legacy/BIOS mode. Upgrading to
11.1 was uneventful. The system has a single SSD with full disk
encryption and ZFS. Again, nothing special, just the
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
04.06.2018 7:59, David Samms wrote:
> Hello,
>
> Background:
> -
> System was originally installed with an 11.0 CD. At the time I tried to get
> UEFI to work, but ended up booting in legacy/BIOS mode. Upgrading to 11.1 was
> uneventful. The system has a single SSD with full disk enc
12 matches
Mail list logo
