Re: Help

2016-12-14 Thread Hans Petter Selasky
On 12/13/16 05:08, Lewis ingraham wrote: 4. Another potential problem with usb drive detection as well. Usb ports work just fine in something like windows and linux but not FreeBSD. Can you show dmesg of failed enumerations? Did you try to set some device quirks? --HPS __

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Konstantin Belousov
On Tue, Dec 13, 2016 at 08:43:45PM +0300, Slawa Olhovchenkov wrote: > On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote: > > > This is not what I expected. > > Also, I realized that I mis-read the memory test code. It does not > > obliterate memory, old content is preserved. > >

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Konstantin Belousov
On Wed, Dec 14, 2016 at 11:53:50AM +0200, Konstantin Belousov wrote: > On Tue, Dec 13, 2016 at 08:43:45PM +0300, Slawa Olhovchenkov wrote: > > On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote: > > > > > This is not what I expected. > > > Also, I realized that I mis-read the memo

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Slawa Olhovchenkov
On Wed, Dec 14, 2016 at 12:27:11PM +0200, Konstantin Belousov wrote: > On Wed, Dec 14, 2016 at 11:53:50AM +0200, Konstantin Belousov wrote: > > On Tue, Dec 13, 2016 at 08:43:45PM +0300, Slawa Olhovchenkov wrote: > > > On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote: > > > > >

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Konstantin Belousov
On Wed, Dec 14, 2016 at 01:52:11PM +0300, Slawa Olhovchenkov wrote: > Booting... > KDB: debugger backends: ddb > KDB: current backend: ddb > SMAP type=01 base= len=00099c00 > SMAP type=02 base=00099c00 len=6400 > SMAP type=02 base=000e len=000

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Slawa Olhovchenkov
On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote: > In other words, it is almost certainly the hang and not a fault causing > hang. This means that the machine is not compliant with the IA32 > architecture, in particular, the region reported as normal memory by > E820 BIOS servi

FreeBSD_HEAD_amd64_gcc - Build #1732 - Still Failing

2016-12-14 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc - Build #1732 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1732/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1732/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1732/c

FreeBSD_HEAD_i386 - Build #4383 - Failure

2016-12-14 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #4383 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4383/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4383/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4383/console Change summaries: 3

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Konstantin Belousov
On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote: > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote: > > > In other words, it is almost certainly the hang and not a fault causing > > hang. This means that the machine is not compliant with the IA32 > > architec

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Slawa Olhovchenkov
On Wed, Dec 14, 2016 at 04:40:33PM +0200, Konstantin Belousov wrote: > On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote: > > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote: > > > > > In other words, it is almost certainly the hang and not a fault causing > >

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Slawa Olhovchenkov
On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote: > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote: > > > In other words, it is almost certainly the hang and not a fault causing > > hang. This means that the machine is not compliant with the IA32 > > archite

FreeBSD_HEAD_i386 - Build #4384 - Fixed

2016-12-14 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #4384 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4384/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4384/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4384/console Change summaries: 310

Re: [RFC/RFT] projects/ipsec

2016-12-14 Thread Eugene M. Zheganin
Hi, On 11.12.2016 4:07, Andrey V. Elsukov wrote: Hi All, I am pleased to announce that projects/ipsec, that I started several months ago is ready for testing and review. The main goals were: * rework locking to make IPsec code more friendly for concurrent processing; * make lookup in

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Konstantin Belousov
On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote: > On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote: > > > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote: > > > > > In other words, it is almost certainly the hang and not a fault causing >

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Slawa Olhovchenkov
On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote: > On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote: > > On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote: > > > > > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote: > > >

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Konstantin Belousov
On Wed, Dec 14, 2016 at 10:29:43PM +0300, Slawa Olhovchenkov wrote: > On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote: > > > On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote: > > > For test hardware setup (NUMA+interleave), what ISO I can try to boot? > > Didn

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread Slawa Olhovchenkov
On Wed, Dec 14, 2016 at 09:43:24PM +0200, Konstantin Belousov wrote: > On Wed, Dec 14, 2016 at 10:29:43PM +0300, Slawa Olhovchenkov wrote: > > On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote: > > > > > On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote: > > > >

Re: Revision 309657 to stack_machdep.c renders unbootable system

2016-12-14 Thread Mark Johnston
On Wed, Dec 14, 2016 at 11:49:26AM -0800, Steven G. Kargl wrote: > Well, after 3 days of bisection, I finally found the commit > that renders my system unbootable. The system does not panic. > It simply gets stuck in some state. Nonfunctional keyboard, > so can't break into debugger. No serial c

Re: Revision 309657 to stack_machdep.c renders unbootable system

2016-12-14 Thread Mark Johnston
On Wed, Dec 14, 2016 at 12:14:16PM -0800, Mark Johnston wrote: > On Wed, Dec 14, 2016 at 11:49:26AM -0800, Steven G. Kargl wrote: > > Well, after 3 days of bisection, I finally found the commit > > that renders my system unbootable. The system does not panic. > > It simply gets stuck in some state

Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-14 Thread A. Wilcox
On 14/12/16 13:48, Slawa Olhovchenkov wrote: > On Wed, Dec 14, 2016 at 09:43:24PM +0200, Konstantin Belousov wrote: > >> On Wed, Dec 14, 2016 at 10:29:43PM +0300, Slawa Olhovchenkov wrote: >>> On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote: >>> On Wed, Dec 14, 2016 at 06:

Re: Revision 309657 to stack_machdep.c renders unbootable system

2016-12-14 Thread Mark Johnston
On Wed, Dec 14, 2016 at 03:48:04PM -0800, Steven G. Kargl wrote: > On Wed, Dec 14, 2016 at 02:10:48PM -0800, Mark Johnston wrote: > > On Wed, Dec 14, 2016 at 12:14:16PM -0800, Mark Johnston wrote: > > > On Wed, Dec 14, 2016 at 11:49:26AM -0800, Steven G. Kargl wrote: > > > > Well, after 3 days of b

Revision 309657 to stack_machdep.c renders unbootable system

2016-12-14 Thread Steven G. Kargl
Well, after 3 days of bisection, I finally found the commit that renders my system unbootable. The system does not panic. It simply gets stuck in some state. Nonfunctional keyboard, so can't break into debugger. No serial console available. The verbose dmesg.boot for a working kernel from revisi

Re: Revision 309657 to stack_machdep.c renders unbootable system

2016-12-14 Thread Steven G. Kargl
On Wed, Dec 14, 2016 at 02:10:48PM -0800, Mark Johnston wrote: > On Wed, Dec 14, 2016 at 12:14:16PM -0800, Mark Johnston wrote: > > On Wed, Dec 14, 2016 at 11:49:26AM -0800, Steven G. Kargl wrote: > > > Well, after 3 days of bisection, I finally found the commit > > > that renders my system unboota

Re: Revision 309657 to stack_machdep.c renders unbootable system

2016-12-14 Thread Steven G. Kargl
On Wed, Dec 14, 2016 at 04:50:21PM -0800, Mark Johnston wrote: > On Wed, Dec 14, 2016 at 03:48:04PM -0800, Steven G. Kargl wrote: > > On Wed, Dec 14, 2016 at 02:10:48PM -0800, Mark Johnston wrote: > > > On Wed, Dec 14, 2016 at 12:14:16PM -0800, Mark Johnston wrote: > > > > On Wed, Dec 14, 2016 at 1