Re: HEADS UP: Upgraded clang, llvm and lldb to 3.5.0

2015-01-08 Thread Sulev-Madis Silber (ketas)
Maybe I should add (if no-one noticed it yet) that this is cross-build for ARM. I wouldn't attempt to upgrade host itself over two major versions. I think it's totally insane how you can't build other major versions & arches. 9.x can't make 11.x (well, you can, if using gcc bootstrap), and I heard

buildworld broken on current with WITHOUT_CAPSICUM

2015-01-08 Thread Manfred Antar
On amd64 current build world is broken if defined WITHOUT_CAPSICUM svn revision 276867 here is the error: /usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/tcpdump.c:80:10: fatal error: 'libcapsicum.h' file not found #include ^ 1 error generated. make[5]: stopped in /usr/src/u

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Mark Johnston
On Thu, Jan 8, 2015 at 5:42 PM, Bjoern A. Zeeb wrote: > >> On 08 Jan 2015, at 18:46 , Mark Johnston wrote: >> >> On Thu, Jan 08, 2015 at 07:27:10PM +0100, Dimitry Andric wrote: >>> On 08 Jan 2015, at 16:24, Mark Johnston wrote: On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb w

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Bjoern A. Zeeb
> On 08 Jan 2015, at 18:46 , Mark Johnston wrote: > > On Thu, Jan 08, 2015 at 07:27:10PM +0100, Dimitry Andric wrote: >> On 08 Jan 2015, at 16:24, Mark Johnston wrote: >>> >>> On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote: >> ... It only started 2 nights ago and we are bo

Build failed in Jenkins: FreeBSD_HEAD #2184

2015-01-08 Thread jenkins-admin
See Changes: [jkim] Merge OpenSSL 1.0.1k. [dim] Now compiler-rt has been updated in r276851, bring in the various sanitizer libraries that already work on FreeBSD: * asan:Address Sanitizer * ubsan: Undefined Behavior Sanitizer *

Re: [PATCH] Add support for 64-bit AHCI BAR.

2015-01-08 Thread Konstantin Belousov
On Thu, Jan 08, 2015 at 05:09:23PM +0100, Micha?? Stanek wrote: > Hello all, > > I ran into an issue with AHCI BAR allocation on arm64. The AHCI PCI driver > in sys/dev/ahci/ahci_pci.c assumes that ABAR (AHCI Base Address) register > is located at offset 0x24 (BAR5) in the PCI header. Specificatio

Re: HEADS UP: Upgraded clang, llvm and lldb to 3.5.0

2015-01-08 Thread Mike Tancsa
On 1/8/2015 1:21 PM, Benjamin Kaduk wrote: I have no specific data about this specific case, but the advertised procedure for upgrading between major branches is to update to the tip of the starting branch before attempting the major version jump, i.e., update to the tip of stable/9 before attemp

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Mark Johnston
On Thu, Jan 08, 2015 at 07:27:10PM +0100, Dimitry Andric wrote: > On 08 Jan 2015, at 16:24, Mark Johnston wrote: > > > > On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote: > ... > >> It only started 2 nights ago and we are both doing daily builds. Unlikely > >> that stuff from Nove

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Dimitry Andric
On 08 Jan 2015, at 16:24, Mark Johnston wrote: > > On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote: ... >> It only started 2 nights ago and we are both doing daily builds. Unlikely >> that stuff from November would do it oh so suddenly. >> >> It’s hard to exactly narrow it down

Re: HEADS UP: Upgraded clang, llvm and lldb to 3.5.0

2015-01-08 Thread Benjamin Kaduk
On Thu, 8 Jan 2015, Sulev-Madis Silber (ketas) wrote: > I don't know... if 9.x can't be used to build 11.x / CURRENT anymore, > maybe this should be put to UPDATING (that 9.x is not supported) and I > just upgrade to 10.x... which would solve everything (hopefully). I have no specific data about

Re: Haswell CPU Feature

2015-01-08 Thread Sean Bruno
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/06/15 07:48, John Baldwin wrote: > On 1/6/15 12:44 AM, Jia-Shiun Li wrote: >> On Tue, Jan 6, 2015 at 1:23 PM, Neel Natu >> wrote: >> >>> Hi Sean, >>> >>> On Mon, Jan 5, 2015 at 6:34 PM, Sean Bruno >>> wrote: I'm thinking something like

Re: [PATCH] Add support for 64-bit AHCI BAR.

2015-01-08 Thread Warner Losh
> On Jan 8, 2015, at 9:09 AM, Michał Stanek wrote: > > This looks good to my eyes… Given the ordering of the words in the BAR, you won’t get false positives. It uses the PCI bus code to make the determination, which eliminates duplication of code in drivers… I like it. Warner signature.asc

[PATCH] Add support for 64-bit AHCI BAR.

2015-01-08 Thread Michał Stanek
Hello all, I ran into an issue with AHCI BAR allocation on arm64. The AHCI PCI driver in sys/dev/ahci/ahci_pci.c assumes that ABAR (AHCI Base Address) register is located at offset 0x24 (BAR5) in the PCI header. Specification for AHCI confirms this is indeed the default address of the main BAR. Ho

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Mark Johnston
On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote: > > > On 08 Jan 2015, at 13:37 , ma...@freebsd.org wrote: > > > > On Thu, Jan 08, 2015 at 01:40:11PM +0100, Dimitry Andric wrote: > >> On 08 Jan 2015, at 13:09, Bjoern A. Zeeb > >> wrote: > >>> > On 07 Jan 2015, at 15:02 , Bj

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread David Wolfskill
On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote: > ... > >>> Ok, this continues; I have since seen it four more times. Still > >>> i386.GENERIC only; none of the LINT kernels or other architectures. > >>> > >>> Can someone please investigate what triggers this? > >> > >> Looks l

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Mark Johnston
On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote: > > > On 08 Jan 2015, at 13:37 , ma...@freebsd.org wrote: > > > > On Thu, Jan 08, 2015 at 01:40:11PM +0100, Dimitry Andric wrote: > >> On 08 Jan 2015, at 13:09, Bjoern A. Zeeb > >> wrote: > >>> > On 07 Jan 2015, at 15:02 , Bj

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Bjoern A. Zeeb
> On 08 Jan 2015, at 13:37 , ma...@freebsd.org wrote: > > On Thu, Jan 08, 2015 at 01:40:11PM +0100, Dimitry Andric wrote: >> On 08 Jan 2015, at 13:09, Bjoern A. Zeeb >> wrote: >>> On 07 Jan 2015, at 15:02 , Bjoern A. Zeeb wrote: > On 07 Jan 2015, at 14:13 , Ed Maste wrote: >>>

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread markj
On Thu, Jan 08, 2015 at 01:40:11PM +0100, Dimitry Andric wrote: > On 08 Jan 2015, at 13:09, Bjoern A. Zeeb > wrote: > > > >> On 07 Jan 2015, at 15:02 , Bjoern A. Zeeb > >> wrote: > >>> On 07 Jan 2015, at 14:13 , Ed Maste wrote: > >>> On 7 January 2015 at 08:57, David Wolfskill wrote: >

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Dimitry Andric
On 08 Jan 2015, at 13:09, Bjoern A. Zeeb wrote: > >> On 07 Jan 2015, at 15:02 , Bjoern A. Zeeb >> wrote: >>> On 07 Jan 2015, at 14:13 , Ed Maste wrote: >>> On 7 January 2015 at 08:57, David Wolfskill wrote: --- kernel.debug --- linking kernel.debug ctfmerge -L VERSION -g -o ker

Re: "*** [kernel.debug] Error code 139"?

2015-01-08 Thread Bjoern A. Zeeb
> On 07 Jan 2015, at 15:02 , Bjoern A. Zeeb > wrote: > > >> On 07 Jan 2015, at 14:13 , Ed Maste wrote: >> >> On 7 January 2015 at 08:57, David Wolfskill wrote: >>> --- kernel.debug --- >>> linking kernel.debug >>> ctfmerge -L VERSION -g -o kernel.debug ... >>> Segmentation fault (core dumpe

Re: HEADS UP: Upgraded clang, llvm and lldb to 3.5.0

2015-01-08 Thread Sulev-Madis Silber (ketas)
Hello. I have this issue where it's impossible to get 9.x (9.3) into state where I can build clang 3.5.0 bootstrap of CURRENT. gcc works fine. I've already discussed this with some people in EFNet :: #bsdmips Currently I have this jail, built using: WITH_CLANG_IS_CC WITH_LIBCPLUSPLUS I get s