On Tue, 13 Apr 2021 17:18:42 -0400
Mark Johnston wrote:
> > P.S.
> > I have not been running any virtual machines.
> > I do use nvidia graphics driver.
>
In past I had report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238698
Now I switch to AMD and got only ~1Gb memory allocated by x
Master of origin;-)
--
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de
geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail
verzoeken wij u dit direct door te geven aan de verzender door middel van
een reply e-mail en de ontvangen e-mail uit uw systemen te
On Mon, Apr 19, 2021 at 7:12 AM Rodney W. Grimes <
freebsd-...@gndrsh.dnsmgr.net> wrote:
> > On Sun, Apr 18, 2021 at 07:07:44PM -0400, Ed Maste wrote:
> > > On Fri, 16 Apr 2021 at 16:22, Warner Losh wrote:
> > > >
> > > > > > As well as "Origin".
> > > > >
> > > > > (Single) Source of Truth, mayb
> On 19 Apr 2021, at 17:03, Rick Macklem wrote:
>
> Olav Gjerde wrote:
>> I have tried D29690 patch and reverting back to r367492 this weekend.
>> Neither made any difference for my system.
For me, reverting the patch in r367492, solved all the problems.
In addition, I also turned off LRO and
Olav Gjerde wrote:
>I have tried D29690 patch and reverting back to r367492 this weekend. Neither
>made any difference for my system.
Just to clarify it, I meant "revert the patch in r367492" and not
"revert to revision r367492". I've attached the patch that
backs out the changes made by the patch
I have tried D29690 patch and reverting back to r367492 this weekend.
Neither made any difference for my system.
There is also a reddit thread about this
https://www.reddit.com/r/freebsd/comments/mqol4o/nfs_issues_since_upgrading_to_13release/
On Sat, Apr 17, 2021 at 1:10 AM Rick Macklem wrote:
> On Sun, Apr 18, 2021 at 07:07:44PM -0400, Ed Maste wrote:
> > On Fri, 16 Apr 2021 at 16:22, Warner Losh wrote:
> > >
> > > > > As well as "Origin".
> > > >
> > > > (Single) Source of Truth, maybe?
> > >
> > > s/Master, p/P/ also makes sense.
> >
> > IMO instead of lightly rewording the existing
Hi!
> ZFS: out of temporary buffer space
>
> Any ideas on how to fix this ?
Ok, fix was this:
Using the same memstick, I wrote a new efi partition as a copy
from the efi partition on the memstick.
gpart (simplified) showed this:
=>40 2000409184 nvd0 GPT (954G)
40 40
Hi!
Upgrading a c256294-g2cf84258922f kernel (14.0 from 27th of January)
to a more recent version displays this error on reboot:
ZFS: out of temporary buffer space
Any ideas on how to fix this ?
I've tried the fix as described in
https://old.reddit.com/r/freebsd/comments/mtx5cf/freebsd_130_upg
On Mon, Apr 19, 2021 at 10:06:28AM +0100, Alexander Richardson wrote:
> On Sun, 18 Apr 2021 at 20:58, Александр Недоцуков wrote:
> >
> > Hi All,
> >
> > After supposed locking fixes done in this commit:
> > 5245bf7b92b74e556527b4916a8deba386fe5772
> > we have a broken nsdispatch(3) when system ha
On Sun, 18 Apr 2021 at 20:58, Александр Недоцуков wrote:
>
> Hi All,
>
> After supposed locking fixes done in this commit:
> 5245bf7b92b74e556527b4916a8deba386fe5772
> we have a broken nsdispatch(3) when system has a threaded nss module plugged
> in.
>
> To illustrate the problem:
>
> $id bland
On Sun, Apr 18, 2021 at 07:07:44PM -0400, Ed Maste wrote:
> On Fri, 16 Apr 2021 at 16:22, Warner Losh wrote:
> >
> > > > As well as "Origin".
> > >
> > > (Single) Source of Truth, maybe?
> >
> > s/Master, p/P/ also makes sense.
>
> IMO instead of lightly rewording the existing comment we could ju
12 matches
Mail list logo