Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 14, 2018, at 10:17 PM, Enji Cooper (yaneurabeya) > wrote: ... > Oh yipes. I guess passing in a server socket (a bound and listening socket) > instead of a client socket (connect’ed to a server socket) for `s` will > result in a crash? > > From > https://github.com/ngie-eign/freebs

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 14, 2018, at 10:12 PM, Enji Cooper (yaneurabeya) > wrote: > >> On Oct 14, 2018, at 9:45 PM, Enji Cooper (yaneurabeya) >> mailto:yaneurab...@gmail.com>> wrote: >> >> >> >>> On Oct 14, 2018, at 7:25 PM, Gleb Smirnoff >> > wrote: >>> >>> Hi Enji, >>> >>>

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 14, 2018, at 9:45 PM, Enji Cooper (yaneurabeya) > wrote: > > > >> On Oct 14, 2018, at 7:25 PM, Gleb Smirnoff > > wrote: >> >> Hi Enji, >> >> On Sun, Oct 14, 2018 at 06:51:42PM -0700, Enji Cooper (yaneurabeya) wrote: >> E> Hi, >> E> I’m seeing a semi-

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 14, 2018, at 7:25 PM, Gleb Smirnoff wrote: > > Hi Enji, > > On Sun, Oct 14, 2018 at 06:51:42PM -0700, Enji Cooper (yaneurabeya) wrote: > E> Hi, > E>I’m seeing a semi-deterministic panic on 12.0-ALPHA9 related to > sendfile(2) when running sendfile_test on the host: > https://pa

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

Hi Enji, On Sun, Oct 14, 2018 at 06:51:42PM -0700, Enji Cooper (yaneurabeya) wrote: E> Hi, E> I’m seeing a semi-deterministic panic on 12.0-ALPHA9 related to sendfile(2) when running sendfile_test on the host: https://pastebin.com/raw/6Y7xg0ki; it looks like it’s crashing in the sxlock c

Re: 12.0-ALPHA5 - ZFS default ARC max apparently forcing system to run out of memory

On 9/27/18 9:00 PM, Allan Jude wrote: > > It doesn't appear like ZFS is dominating memory usage there. Using less > than the 8GB you indicated that setting the max to solved the problem... You're right, the problem appeared again despite having limited ZFS: FreeBSD tau.bluestop.org 12.0-ALPHA8

Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

Hi, I’m seeing a semi-deterministic panic on 12.0-ALPHA9 related to sendfile(2) when running sendfile_test on the host: https://pastebin.com/raw/6Y7xg0ki; it looks like it’s crashing in the sxlock code when calling sblock on a sockbuf. Are there any commands in gdb you would like me to

RE: Problem compiling rust: observations on swap

Set TAR in make.conf to gnu tar from ports. Some tarballs will cause bsdtar to exhaust memory and swap. There was discussion a while ago suggesting this is a bug in vmm. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Ap

Re: OpenSSL 1.1.1 Update report (ongoing)

* ptlib; Fails to build, due to C compiler errors arising from source-level incompatibilities. This gets dragged in by opal, which ends up being a dependency of ekiga, which is a dependency of gnome3. Resolved by adding it to the exclude list, which actually does not seem to be breaking the build

Re: OpenSSL 1.1.1 libssl.so version number

On Sun, Oct 14, 2018 at 05:45:30PM +0200, Dirk Meyer wrote: > Don Lewis schrieb:, > > > It looks to me like the base libssl.so version needs to get moved to a > > value that doesn't collide with ports, perhaps 12. These are the > > library version numbers currently used by the various ssl ports:

RE: OpenSSL 1.1.1 libssl.so version number

Not necessarily 12. ports/openssl111 should have the same ABI as HEAD so they should share the same version number. The fact that openssl111 in HEAD and openssl 1.0.2 in ports share the same version number but do not share the same ABI is the problem. --- Sent using a tiny phone keyboard. Apolo

Problem compiling rust: observations on swap

On 06/10/2018 23:41, Rebecca Cran wrote: > On 10/6/18 6:40 AM, Greg V wrote: > >> BTW, this error message doesn't say much, but if cargo fails, you >> might be out of memory. > > I was going to suggest being out of memory too. I've seen the rust build > cause my system to run out of all 32GB RAM a

Re: OpenSSL 1.1.1 libssl.so version number

> On Oct 14, 2018, at 2:00 AM, Don Lewis wrote: > >> On 12 Oct, Don Lewis wrote: >> Prior to the OpenSSL 1.1.1 import, the base OpenSSL library was >> /usr/lib/libssl.so.8. The security/openssl port (1.0.2p) installed >> ${LOCALBASE}/lib/ilbssl.so.9 and the security/openssl-devel port >> (1.1.

Re: Strange panic at boot with vmm in loader.conf vs manually loading it

On 10/14/18, Mike Tancsa wrote: > On 10/13/2018 12:48 PM, Allan Jude wrote: >> >> Strange that your crash is in ZFS here... >> >> Can you take a crash dump? >> >> It looks like something is trying to write to uninitialized memory here. > > I will need to pop in another drive or can I do a netdump

Re: OpenSSL 1.1.1 libssl.so version number

In message <0f7eb379-8c52-478a-aa5a-ac4257e5b...@freebsd.org>, Daniel Eischen w rites: > > > > On Oct 12, 2018, at 10:58 PM, Cy Schubert wrote > : > > > > In message , Don Lewis writes: > >> Prior to the OpenSSL 1.1.1 import, the base OpenSSL library was > >> /usr/lib/libssl.so.8. The security

Re: OpenSSL 1.1.1 Update report (ongoing)

More: * ImageMagick (unrelated to OpenSSL 1.1.1): This fails with the OpenMP option ticked, due to trying to link with the base ld. Can be fixed by setting CC, CXX, LD to a port-installed clang, clang++, lld. The port should probably do this automatically. * compat-linux-c7-base had a signal 11

Re: Strange panic at boot with vmm in loader.conf vs manually loading it

On 10/13/2018 12:48 PM, Allan Jude wrote: > > Strange that your crash is in ZFS here... > > Can you take a crash dump? > > It looks like something is trying to write to uninitialized memory here. I will need to pop in another drive or can I do a netdump at this point ?     ---Mike -- -

Re: nginx introduces extra delay when talking to slow backend (probably FreeBSD kevent specific)

Hello! On Fri, Oct 12, 2018 at 11:31:26PM +0300, Dmitry Marakasov wrote: > * Dmitry Marakasov (amd...@amdmi3.ru) wrote: > > I've gathered ktrace dumps for both cases, and it really looks that > the problem is related to kevent. After nginx sends response back > to client, it calls kevent(2) on c

OpenSSL 1.1.1 Update report (ongoing)

I'm currently in the process of updating my laptop, rebuilding world, then rebuilding *all* ports. I have a large number of ports installed (around 1200), and I tend to select a lot of build options. This report is intended to help shake out issues relating to OpenSSL 1.1.1. I'll be adding to th

Re: OpenSSL 1.1.1 libssl.so version number

On 12 Oct, Don Lewis wrote: > Prior to the OpenSSL 1.1.1 import, the base OpenSSL library was > /usr/lib/libssl.so.8. The security/openssl port (1.0.2p) installed > ${LOCALBASE}/lib/ilbssl.so.9 and the security/openssl-devel port > (1.1.0i) installed ${LOCALBASE}/lib/libssl.so.11. After the impor