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,
The lmc(4) driver supports hardware for a number of legacy interfaces,
including EIA612/613, T1/E1, T3, etc. The driver's license is ambiguous
and attempts to contact the author failed.
I would like to remove this driver from 12.0, and have a deprecation
notice in review D15182 [1]; I would
> On 24 Apr 2018, at 23:39, Marc Branchaud wrote:
> On 2018-04-24 09:24 AM, Glen Barber wrote:
>> There are additional nits regarding jail(8) that chroot(8) does not have
>> the same limitations. Setting/unsetting the immutable flag on something
>> like /sbin/init, for
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
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
On Tue, Apr 24, 2018 at 10:09:40AM -0400, Marc Branchaud wrote:
> On 2018-04-24 09:24 AM, Glen Barber wrote:
> > There are additional nits regarding jail(8) that chroot(8) does not have
> > the same limitations. Setting/unsetting the immutable flag on something
> > like /sbin/init, for example,
On 2018-04-24 09:24 AM, Glen Barber wrote:
There are additional nits regarding jail(8) that chroot(8) does not have
the same limitations. Setting/unsetting the immutable flag on something
like /sbin/init, for example, comes to mind.
Try
allow.chflags
in your jail.conf.
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
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
There are additional nits regarding jail(8) that chroot(8) does not have
the same limitations. Setting/unsetting the immutable flag on something
like /sbin/init, for example, comes to mind.
Glen
On Tue, Apr 24, 2018 at 11:49:46AM +0100, krad wrote:
> wouldn't it just be easier to do this in a
wouldn't it just be easier to do this in a jail, and then all of these
little bits would be taken care of?
On 24 April 2018 at 01:48, O'Connor, Daniel wrote:
>
>
> > On 24 Apr 2018, at 08:14, Glen Barber wrote:
> > I think you might not have the devfs
11 matches
Mail list logo