Re: process killed: text file modification

2017-03-19 Thread Gergely Czuczy
On 2017. 03. 19. 21:52, Rick Macklem wrote: Kostik wrote: [stuff snipped] Dirty pages are flushed by writes, so if we have a set of dirty pages and async vm_object_page_clean() is called on the vnode' vm_object, we get a bunch of delayed-write AKA dirty buffers. This is possible even after VO

Re: process killed: text file modification

2017-03-19 Thread Rick Macklem
Kostik wrote: [stuff snipped] >> >> Dirty pages are flushed by writes, so if we have a set of dirty pages and >> >> async vm_object_page_clean() is called on the vnode' vm_object, we get >> >> a bunch of delayed-write AKA dirty buffers. This is possible even after >> >> VOP_CLOSE() was done, e.g.

Re: Delivery Status Notification (Failure)

2017-03-19 Thread Roberto Rodriguez Jr
Hi all, My latest findings... Revision: 315577 Last Changed Author: ian Last Changed Rev: 315577 Last Changed Date: 2017-03-19 18:50:03 + (Sun, 19 Mar 2017) FreeBSD krsna 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315577: Sun Mar 19 19:22:52 UTC 2017 # make -j5 buildworld --- libc.a --- ranlib -D

Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3

2017-03-19 Thread Slawa Olhovchenkov
On Sun, Mar 19, 2017 at 06:07:33PM +0200, Konstantin Belousov wrote: > On Sun, Mar 19, 2017 at 04:58:40PM +0100, Dimitry Andric wrote: > > On 19 Mar 2017, at 13:36, Rozhuk Ivan wrote: > > > > > > On Fri, 17 Mar 2017 17:53:24 +0100 > > > "O. Hartmann" wrote: > > > > > >>> Other OS detect AES-NI

Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3

2017-03-19 Thread Konstantin Belousov
On Sun, Mar 19, 2017 at 04:58:40PM +0100, Dimitry Andric wrote: > On 19 Mar 2017, at 13:36, Rozhuk Ivan wrote: > > > > On Fri, 17 Mar 2017 17:53:24 +0100 > > "O. Hartmann" wrote: > > > >>> Other OS detect AES-NI on this server? > >> > >> I havn't ried so far, the box is in heavy use. I'd like

Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3

2017-03-19 Thread Slawa Olhovchenkov
On Sun, Mar 19, 2017 at 04:58:40PM +0100, Dimitry Andric wrote: > On 19 Mar 2017, at 13:36, Rozhuk Ivan wrote: > > > > On Fri, 17 Mar 2017 17:53:24 +0100 > > "O. Hartmann" wrote: > > > >>> Other OS detect AES-NI on this server? > >> > >> I havn't ried so far, the box is in heavy use. I'd like

Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3

2017-03-19 Thread Dimitry Andric
On 19 Mar 2017, at 13:36, Rozhuk Ivan wrote: > > On Fri, 17 Mar 2017 17:53:24 +0100 > "O. Hartmann" wrote: > >>> Other OS detect AES-NI on this server? >> >> I havn't ried so far, the box is in heavy use. I'd like to check with >> some live USB drive versions and report later. >> > > You can

Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3

2017-03-19 Thread Rozhuk Ivan
On Fri, 17 Mar 2017 17:53:24 +0100 "O. Hartmann" wrote: > > Other OS detect AES-NI on this server? > > I havn't ried so far, the box is in heavy use. I'd like to check with > some live USB drive versions and report later. > You can write or find some program that read and decode CPUID and ch

Duplicate? dmesg backtrace, ignore if useless please.

2017-03-19 Thread Jeffrey Bouquet
A.M. security periodic output: hostname, pkg audit etc, redacted... backtrace-17-dmesg-maybe-i386-r313487-12C-1200020.txt the above filename explains the build, platform... sort of... kernel log messages: +Expensive timeout(9) function: 0xb55a7b40(0xbe67c000) 0.034612848 s +Expensive timeout

cross compiling freebsd-head is sigh, now broken - thanks libllvm

2017-03-19 Thread Adrian Chadd
===> lib/clang (all) ===> lib/clang/libllvm (all) In file included from /usr/home/adrian/work/freebsd/head-embedded/obj/mips_ap/mips.mips/usr/home/adrian/work/freebsd/head-embedded/src/tmp/usr/include/c++/v1/math.h:309:0, from /usr/home/adrian/work/freebsd/head-embedded/obj/mips_ap