Re: Strange issue after early AP startup

2017-01-18 Thread Cy Schubert
In message <1922021.4hjeqfj...@ralph.baldwin.cx>, John Baldwin writes: > On Tuesday, January 17, 2017 05:08:58 PM Cy Schubert wrote: > > In message <1492450.xzfnz8z...@ralph.baldwin.cx>, John Baldwin writes: > > > On Tuesday, January 17, 2017 12:53:19 PM Cy Schubert wrote: > > > > In message

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread Matthias Apitz
El día Wednesday, January 18, 2017 a las 08:00:04PM -0500, Allan Jude escribió: > On 2017-01-18 14:37, O. Hartmann wrote: > > Am Wed, 18 Jan 2017 16:38:32 +0100 > > Matthias Apitz schrieb: > > > >> Why you do not just boot from USB some mem stick image, mount some disk > >>

Re: recent change to vim defaults?

2017-01-18 Thread Julian Elischer
On 19/01/2017 11:18 AM, Julian Elischer wrote: On 19/01/2017 1:37 AM, Adam Weinberger wrote: On 18 Jan, 2017, at 10:35, Julian Elischer wrote: On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon,

Re: recent change to vim defaults?

2017-01-18 Thread Julian Elischer
On 19/01/2017 1:37 AM, Adam Weinberger wrote: On 18 Jan, 2017, at 10:35, Julian Elischer wrote: On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread Allan Jude
On 2017-01-18 14:37, O. Hartmann wrote: > Am Wed, 18 Jan 2017 16:38:32 +0100 > Matthias Apitz schrieb: > >> Why you do not just boot from USB some mem stick image, mount some disk >> space to /mnt, svn checkout CURRENT to /mnt and build a booteable system >> (world and kernel)

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread Polytropon
On Wed, 18 Jan 2017 20:37:26 +0100, O. Hartmann wrote: > Am Wed, 18 Jan 2017 16:38:32 +0100 > Matthias Apitz schrieb: > > > Why you do not just boot from USB some mem stick image, mount some disk > > space to /mnt, svn checkout CURRENT to /mnt and build a booteable system > >

Re: Build failure 'wmmintrin.h' file not found

2017-01-18 Thread Warner Losh
On Wed, Jan 18, 2017 at 1:21 PM, Dimitry Andric wrote: > On 18 Jan 2017, at 14:42, Magnus Ringman wrote: >> >> On Wed, Jan 18, 2017 at 2:16 PM, Hans Petter Selasky >> wrote: > ... >>> And the error popped out. I'm not observing this error

Re: ASLR

2017-01-18 Thread Piotr Kubaj
It should also be stated properly that this patch doesn't implement ASLR, but ASR. signature.asc Description: PGP signature

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread Matthias Apitz
(I adjuested To/cc) El día Wednesday, January 18, 2017 a las 08:37:26PM +0100, O. Hartmann escribió: > Wow! > > As I initially stated, that is EXACTLY what I was inclined to do except the > fact that I > had already an intact /usr/obj and usr/src with a complete compiled system. > > I booted

Re: Build failure 'wmmintrin.h' file not found

2017-01-18 Thread Dimitry Andric
On 18 Jan 2017, at 14:42, Magnus Ringman wrote: > > On Wed, Jan 18, 2017 at 2:16 PM, Hans Petter Selasky > wrote: ... >> And the error popped out. I'm not observing this error when building a >> 12-current kernel from an 11-stable install. > > > Isn't it all

Re: Build failure 'wmmintrin.h' file not found

2017-01-18 Thread Dimitry Andric
On 18 Jan 2017, at 14:16, Hans Petter Selasky wrote: > > On 01/18/17 14:13, Dimitry Andric wrote: >> On 18 Jan 2017, at 13:36, Hans Petter Selasky wrote: >>> >>> I'm seeing the following build-error trying to build 12-current from >>> 10-stable: >>> >>>

Re: crash in iflib_fast_intr

2017-01-18 Thread Shawn Webb
On Wed, Jan 18, 2017 at 07:31:12AM -0700, Sean Bruno wrote: > > > On 01/18/17 03:37, peter.b...@bsd4all.org wrote: > > Hi, > > > > A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr. Since > > GENERIC now has EARLY_AP_STARTUP, this probably got unnoticed. Problem is > >

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread O. Hartmann
Am Wed, 18 Jan 2017 16:38:32 +0100 Matthias Apitz schrieb: > Why you do not just boot from USB some mem stick image, mount some disk > space to /mnt, svn checkout CURRENT to /mnt and build a booteable system > (world and kernel) and install to DESTDIR=/mnt ? > > I do not

Re: r311568 makes freerdp very slow

2017-01-18 Thread Ultima
I have been affected by this issue as well, just updated to r312388 and it is fixed. Thanks On Wed, Jan 18, 2017 at 1:29 PM, John Baldwin wrote: > On Tuesday, January 17, 2017 01:46:31 PM Jakob Alvermark wrote: > > On Fri, January 13, 2017 22:46, Jakob Alvermark wrote: > > >

Re: recent change to vim defaults?

2017-01-18 Thread Pete Wright
On 1/18/17 10:24 AM, Alexander Kabaev wrote: On Wed, 18 Jan 2017 10:06:55 -0800 Pete Wright wrote: On 1/18/17 10:01 AM, Julian Elischer wrote: On 18/01/2017 5:03 PM, Raimund Sacherer wrote: I have to put mouse=v to get the behavior I am used to. Best doesn't really

Re: ASLR

2017-01-18 Thread Conrad Meyer
On Wed, Jan 18, 2017 at 9:53 AM, Johannes Lundberg wrote: > Hi > > What is the status of ASLR? > > https://reviews.freebsd.org/D5603 > > The thread has been silent for a couple of months. I'm happy to test if > needed. Hi Johannes, I think we were waiting on some review, but

Re: r311568 makes freerdp very slow

2017-01-18 Thread John Baldwin
On Tuesday, January 17, 2017 01:46:31 PM Jakob Alvermark wrote: > On Fri, January 13, 2017 22:46, Jakob Alvermark wrote: > > On Fri, January 13, 2017 19:44, John Baldwin wrote: > > > >> On Friday, January 13, 2017 09:58:01 AM Jakob Alvermark wrote: > >> > >> > >>> On Thu, January 12, 2017 19:26,

Re: recent change to vim defaults?

2017-01-18 Thread Alexander Kabaev
On Wed, 18 Jan 2017 10:06:55 -0800 Pete Wright wrote: > On 1/18/17 10:01 AM, Julian Elischer wrote: > > On 18/01/2017 5:03 PM, Raimund Sacherer wrote: > >> I have to put mouse=v to get the behavior I am used to. > >> > >> Best > > > > doesn't really work for me. > > > >

Re: recent change to vim defaults?

2017-01-18 Thread Pete Wright
On 1/18/17 10:01 AM, Julian Elischer wrote: On 18/01/2017 5:03 PM, Raimund Sacherer wrote: I have to put mouse=v to get the behavior I am used to. Best doesn't really work for me. vim is still taking mouse events kinda feel like it we need a "classic" vim port that is from the v7.x

Re: recent change to vim defaults?

2017-01-18 Thread Adam Weinberger
> On 18 Jan, 2017, at 10:35, Julian Elischer wrote: > > On 17/01/2017 1:23 AM, Adam Weinberger wrote: >>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: >>> >>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that

Re: recent change to vim defaults?

2017-01-18 Thread Julian Elischer
On 18/01/2017 5:03 PM, Raimund Sacherer wrote: I have to put mouse=v to get the behavior I am used to. Best doesn't really work for me. vim is still taking mouse events ___ freebsd-current@freebsd.org mailing list

ASLR

2017-01-18 Thread Johannes Lundberg
Hi What is the status of ASLR? https://reviews.freebsd.org/D5603 The thread has been silent for a couple of months. I'm happy to test if needed. I'm also interested in KASLR. Is that also on the roadmap? If someone involved could share some info I'd be grateful.

Re: recent change to vim defaults?

2017-01-18 Thread Baptiste Daroussin
On Wed, Jan 18, 2017 at 10:37:32AM -0700, Adam Weinberger wrote: > > On 18 Jan, 2017, at 10:35, Julian Elischer wrote: > > > > On 17/01/2017 1:23 AM, Adam Weinberger wrote: > >>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: > >>> > >>> On Mon, Jan

Re: recent change to vim defaults?

2017-01-18 Thread Julian Elischer
On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific

Re: Strange issue after early AP startup

2017-01-18 Thread John Baldwin
On Wednesday, January 18, 2017 09:00:52 AM Hans Petter Selasky wrote: > On 01/18/17 02:18, John Baldwin wrote: > > You might still want to adjust 'nextevent' to schedule the next interrupt > > to be sooner than 'timerperiod' though. You could just set 'nextevent' to > > 'now' in that case instead

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-18 Thread O. Hartmann
On Wed, 18 Jan 2017 07:59:17 -0700 Sean Bruno wrote: > On 01/18/17 07:41, Sean Bruno wrote: > > > > > > On 01/18/17 00:34, O. Hartmann wrote: > >> On Thu, 5 Jan 2017 20:17:56 -0700 > >> Sean Bruno wrote: > >>> > >> On a Fujitsu Celsius M740, the

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread Matthias Apitz
Why you do not just boot from USB some mem stick image, mount some disk space to /mnt, svn checkout CURRENT to /mnt and build a booteable system (world and kernel) and install to DESTDIR=/mnt ? I do not understand all this hassle? matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂

Re: crash in iflib_fast_intr

2017-01-18 Thread peter . blok
This is with an igb interface. Peter > On 18 Jan 2017, at 15:31, Sean Bruno wrote: > > > > On 01/18/17 03:37, peter.b...@bsd4all.org > wrote: >> Hi, >> >> A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr. Since >>

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-18 Thread Sean Bruno
On 01/18/17 08:20, O. Hartmann wrote: > On Wed, 18 Jan 2017 07:59:17 -0700 > Sean Bruno wrote: > >> On 01/18/17 07:41, Sean Bruno wrote: >>> >>> >>> On 01/18/17 00:34, O. Hartmann wrote: On Thu, 5 Jan 2017 20:17:56 -0700 Sean Bruno wrote:

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-18 Thread Sean Bruno
On 01/18/17 07:41, Sean Bruno wrote: > > > On 01/18/17 00:34, O. Hartmann wrote: >> On Thu, 5 Jan 2017 20:17:56 -0700 >> Sean Bruno wrote: >>> >> On a Fujitsu Celsius M740, the "em0" device gets stuck on heavy I/O. I can >> still trigger this behaviour on recent CURRENT

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-18 Thread Sean Bruno
On 01/18/17 00:34, O. Hartmann wrote: > On Thu, 5 Jan 2017 20:17:56 -0700 > Sean Bruno wrote: > >> tl;dr --> igbX devices will become emX devices >> >> We're about to commit an update to sys/dev/e1000 that will implement and >> activate IFLIB for em(4), lem(4) & igb(4) and

Re: crash in iflib_fast_intr

2017-01-18 Thread Sean Bruno
On 01/18/17 03:37, peter.b...@bsd4all.org wrote: > Hi, > > A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr. Since > GENERIC now has EARLY_AP_STARTUP, this probably got unnoticed. Problem is > reproducible. > > KDB: stack backtrace: > #0 0x805cec97 at

Re: Build failure 'wmmintrin.h' file not found

2017-01-18 Thread Magnus Ringman
On Wed, Jan 18, 2017 at 2:16 PM, Hans Petter Selasky wrote: > On 01/18/17 14:13, Dimitry Andric wrote: > >> On 18 Jan 2017, at 13:36, Hans Petter Selasky wrote: >> >>> >>> I'm seeing the following build-error trying to build 12-current from >>> 10-stable: >>>

Re: Build failure 'wmmintrin.h' file not found

2017-01-18 Thread Hans Petter Selasky
On 01/18/17 14:13, Dimitry Andric wrote: On 18 Jan 2017, at 13:36, Hans Petter Selasky wrote: I'm seeing the following build-error trying to build 12-current from 10-stable: xxx/freebsd/sys/crypto/aesni/aesni_ghash.c:75:10: fatal error: 'wmmintrin.h' file not found

Re: Build failure 'wmmintrin.h' file not found

2017-01-18 Thread Dimitry Andric
On 18 Jan 2017, at 13:36, Hans Petter Selasky wrote: > > I'm seeing the following build-error trying to build 12-current from > 10-stable: > > xxx/freebsd/sys/crypto/aesni/aesni_ghash.c:75:10: fatal error: 'wmmintrin.h' > file not found > #include > > Missing header

Build failure 'wmmintrin.h' file not found

2017-01-18 Thread Hans Petter Selasky
Hi, I'm seeing the following build-error trying to build 12-current from 10-stable: xxx/freebsd/sys/crypto/aesni/aesni_ghash.c:75:10: fatal error: 'wmmintrin.h' file not found #include Missing header exists: xxx/freebsd/contrib/llvm/tools/clang/lib/Headers/wmmintrin.h Missing include

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread Slawa Olhovchenkov
On Wed, Jan 18, 2017 at 10:19:15AM +0100, O. Hartmann wrote: > Hello Daniel, > > thank you very much for responding! > > I just looked into "makeing release". I have a lot of NanoBSD images and build > environments for our purpose at work, but I always strip off the compiler, > too :-( > > I

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread O. Hartmann
On Wed, 18 Jan 2017 10:43:58 +0200 Daniel Kalchev wrote: > I never use the pre-built ISO images for tasks like this. Here is a script I > use to build my own USB boot drive. The drive contains the full OS to boot > and also a copy used to create a new system. I make these boot

Re: recent change to vim defaults?

2017-01-18 Thread Raimund Sacherer
I have to put mouse=v to get the behavior I am used to. Best⁣ Sent from TypeApp ​ On Jan 18, 2017, 08:46, at 08:46, Julian Elischer wrote: >On 17/01/2017 12:07 AM, ohauer wrote: >> I suspect you mean the /usr/local/etc/vim/vimrc and gvimrc files. >> That was the first place

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-18 Thread O. Hartmann
On Thu, 5 Jan 2017 20:17:56 -0700 Sean Bruno wrote: > tl;dr --> igbX devices will become emX devices > > We're about to commit an update to sys/dev/e1000 that will implement and > activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all folks > who can test and

crash in iflib_fast_intr

2017-01-18 Thread peter . blok
Hi, A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr. Since GENERIC now has EARLY_AP_STARTUP, this probably got unnoticed. Problem is reproducible. KDB: stack backtrace: #0 0x805cec97 at kdb_backtrace+0x67 #1 0x80584816 at vpanic+0x186 #2 0x80584683

Re: ISO image: where is the CLANG compiler?

2017-01-18 Thread Daniel Kalchev
I never use the pre-built ISO images for tasks like this. Here is a script I use to build my own USB boot drive. The drive contains the full OS to boot and also a copy used to create a new system. I make these boot drives from time to time, to stay current. Please note the script is few years

Re: Strange issue after early AP startup

2017-01-18 Thread Hans Petter Selasky
On 01/18/17 02:18, John Baldwin wrote: You might still want to adjust 'nextevent' to schedule the next interrupt to be sooner than 'timerperiod' though. You could just set 'nextevent' to 'now' in that case instead of 'next'. Right, I'll give that a spin. Would have to be "now + 1" instead of

Re: Strange issue after early AP startup

2017-01-18 Thread Hans Petter Selasky
On 01/18/17 02:18, John Baldwin wrote: Note that 'nextevent' remains a full 'timerperiod' out (now + timerperiod) and so the first clock interrupt is still 'timerperiod' time away and any callouts are delayed by that amount of time. Also, I think you could set nextcallopt to 'now' rather than