'make buildworld' failure

2017-01-04 Thread Oleg V. Nauman
===> usr.sbin/inetd (all) cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp - B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march=nehalem -DLOGIN_CAP -DIPSEC - g -MD -MF.depend.inetd.o -MTinetd.o -std=gnu99 -fstack-protector-strong - Wsystem-headers -Werror -Wall -Wno-format-y2k -W

Re: 'make buildworld' failure

2017-01-04 Thread hiren panchasara
+ hrs@ On 01/04/17 at 12:43P, Oleg V. Nauman wrote: > ===> usr.sbin/inetd (all) > cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp - > B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march=nehalem -DLOGIN_CAP -DIPSEC - > g -MD -MF.depend.inetd.o -MTinetd.o -std=gnu99 -fstack-protect

Re: How many CPU cores does FreeBSD support?

2017-01-04 Thread Eric Joyner
Adding freebsd-current, because that's a good idea. I see these lines in the beginning of dmesg: MADT: Ignoring local APIC ID 256 (too high) [907/911] MADT: Ignoring local APIC ID 260 (too high) [906/911] MADT: Ignoring local APIC ID 264 (too high) [905/911] MADT: Ignoring

Re: How many CPU cores does FreeBSD support?

2017-01-04 Thread Steve O'Hara-Smith
On Wed, 04 Jan 2017 18:53:23 + Eric Joyner wrote: > MADT: Ignoring local APIC ID 303 (too high) Hmm you said this machine has 272 cores so clearly the IDs have gaps (I have no idea why there are gaps or where these IDs are allocated though). I expect you'll find that 223 of the cores

x2APIC support (Re: How many CPU cores does FreeBSD support?)

2017-01-04 Thread Ian FREISLICH
Hi I think your issue relates to x2APIC support and I don't think that full support for parsing x2APIC MADT entries and doing interrupts remapping has been committed yet from my very brief search of the source and commit messages. I've copied Andriy Gapon and Konstantin Belousov who particip

Re: How many CPU cores does FreeBSD support?

2017-01-04 Thread Konstantin Belousov
On Wed, Jan 04, 2017 at 06:53:23PM +, Eric Joyner wrote: > Adding freebsd-current, because that's a good idea. > > I see these lines in the beginning of dmesg: > > MADT: Ignoring local APIC ID 256 (too high) > > > [907/911] > MADT: Ignoring local APIC ID 260 (too high) > > > [

Re: How many CPU cores does FreeBSD support?

2017-01-04 Thread Eric Joyner
Ok; I will try that and will report back. - Eric On Wed, Jan 4, 2017 at 11:59 AM Konstantin Belousov wrote: > On Wed, Jan 04, 2017 at 06:53:23PM +, Eric Joyner wrote: > > Adding freebsd-current, because that's a good idea. > > > > I see these lines in the beginning of dmesg: > > > > MADT: I

Re: How many CPU cores does FreeBSD support?

2017-01-04 Thread Eric Joyner
I started off with a snapshot of 12-CURRENT, but I got a kernel panic on boot that complained about a duplicate local APIC ID. For now, disabling Hyper Threading gets rid of that panic. I think there's a KASSERT that wasn't getting hit on my 11.0-RELEASE install. On Wed, Jan 4, 2017 at 2:00 PM Eri

Re: 'make buildworld' failure

2017-01-04 Thread Hiroki Sato
hiren panchasara wrote in <20170104180954.gv17...@strugglingcoder.info>: hi> + hrs@ hi> On 01/04/17 at 12:43P, Oleg V. Nauman wrote: hi> > ===> usr.sbin/inetd (all) hi> > cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp - hi> > B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march

Re: PQ_LAUNDRY: unexpected behaviour

2017-01-04 Thread Matthew Macy
On Mon, 02 Jan 2017 06:01:50 -0800 Jonathan Anderson wrote > Hi all, > > I'm seeing some unexpected PQ_LAUNDRY behaviour on something fairly close > to -CURRENT (drm-next-4.7 with an IFC on 26 Dec). Aside from the use of > not-quite-CURRENT, it's also very possible that I