Re: Can't cross-compile HEAD

2020-01-09 Thread Pavel Timofeev
чт, 9 янв. 2020 г. в 16:52, Pavel Timofeev : > > Hello > > I'm trying to cross-compile HEAD r356551 for mips on my FreeBSD-12.1 amd64. > I'm using mips-gcc6-6.5.0 and this > https://github.com/freebsd/freebsd-wifi-build nice project to build > image for my tl-wdr3600 > > The error I'm getting is: >

Re: how to use the ktls

2020-01-09 Thread Rick Macklem
John Baldwin wrote: >On 1/7/20 3:02 PM, Rick Macklem wrote: >> Hi, >> >> Now that I've completed NFSv4.2 I'm on to the next project, which is making >> NFS >> work over TLS. >> Of course, I know absolutely nothing about TLS, which will make this an >> interesting >> exercise for me. >> I did find

Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-09 Thread Hans Petter Selasky
On 2020-01-09 16:16, Mark Johnston wrote: Sorry, I committed a different patch in r356555 before seeing this. I thought of your version first too. You can decide, I think my version is more clean. --HPS ___ freebsd-current@freebsd.org mailing list h

Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-09 Thread Hans Petter Selasky
On 2020-01-09 16:16, Mark Johnston wrote: Also you should audit the code for zero-sized allocations, because upon alloc, zero-sized is not counted, while on free it is. Can you explain further? A zero-sized allocation should be rounded up to 16 bytes in all paths. If the zero-sized allocatio

Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-09 Thread Mark Johnston
On Thu, Jan 09, 2020 at 12:58:28PM +0100, Hans Petter Selasky wrote: > Hi Jeff and Konstantin, > > You have a logical breakage after the domainset patches for malloc. The size > used for allocation statistics is not the same like for freeing causing > messed up "vmstat -m". Sorry, I committed a d

Can't cross-compile HEAD

2020-01-09 Thread Pavel Timofeev
Hello I'm trying to cross-compile HEAD r356551 for mips on my FreeBSD-12.1 amd64. I'm using mips-gcc6-6.5.0 and this https://github.com/freebsd/freebsd-wifi-build nice project to build image for my tl-wdr3600 The error I'm getting is: ... ===> usr.sbin/fmtree (all) ===> usr.bin/vi (all) ===> usr.

Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-09 Thread Gary Jennejohn
On Thu, 9 Jan 2020 12:58:28 +0100 Hans Petter Selasky wrote: > Hi Jeff and Konstantin, > > You have a logical breakage after the domainset patches for malloc. The size > used for allocation statistics is not the same like for freeing causing > messed up "vmstat -m". > > Also you should audit

Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-09 Thread Hans Petter Selasky
Hi Jeff and Konstantin, You have a logical breakage after the domainset patches for malloc. The size used for allocation statistics is not the same like for freeing causing messed up "vmstat -m". Also you should audit the code for zero-sized allocations, because upon alloc, zero-sized is not

Building -CURRENT on -STABLE

2020-01-09 Thread Gordon Bergling
Hi, I am currently about to setup an -CURRENT system, which should gets updated via a build server that’s runs on -STABLE and shares the src and obj directories via NFS to -CURRENT system. While doing a „make -s -j 4 buildworld buildkernel“ the builds fails randomly with the following error. ---

Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-09 Thread Hans Petter Selasky
On 2020-01-09 11:12, Hans Petter Selasky wrote: On 2020-01-09 10:59, Poul-Henning Kamp wrote: I noticed yesterday that M_TEMP stats are screwed up, and rebooted my laptop for reasons of safety. However, it's back again now: critter phk> vmstat -m | grep temp temp 18446744073709546036

Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-09 Thread Hans Petter Selasky
On 2020-01-09 10:59, Poul-Henning Kamp wrote: I noticed yesterday that M_TEMP stats are screwed up, and rebooted my laptop for reasons of safety. However, it's back again now: critter phk> vmstat -m | grep temp temp 18446744073709546036 18014398509476380K - 963239 16,32,64,1

M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-09 Thread Poul-Henning Kamp
I noticed yesterday that M_TEMP stats are screwed up, and rebooted my laptop for reasons of safety. However, it's back again now: critter phk> vmstat -m | grep temp temp 18446744073709546036 18014398509476380K - 963239 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536