panic: UMA: Increase vm.boot_pages with 32 CPUs

2013-08-12 Thread Colin Percival
Hi all, A HEAD@254238 kernel fails to boot in EC2 with panic: UMA: Increase vm.boot_pages on 32-CPU instances. Instances with up to 16 CPUs boot fine. I know there has been some mucking about with VM recently -- anyone want to claim this, or should I start doing a binary search? -- Colin

Re: control of order of inet devices

2013-08-12 Thread Brooks Davis
On Mon, Aug 05, 2013 at 11:16:03AM +0200, Willy Offermans wrote: Hello Brooks, On Wed, Apr 17, 2013 at 03:01:27PM -0500, Brooks Davis wrote: On Wed, Apr 17, 2013 at 04:27:44AM -0500, Joshua Isom wrote: On 4/17/2013 4:14 AM, Willy Offermans wrote: This is what I read in some of the

Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread David Wolfskill
I first noticed this on my laptop on 08 Aug, after having built booted FreeBSD 10.0-CURRENT #975 r253985M/253985:141: Tue Aug 6 05:28:39 PDT 2013 root@localhost:/common/S4/obj/usr/src/sys/CANARY i386 OK. I'm away from home, and Internet access is a bit flaky, so initially, I

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread Davide Italiano
On Mon, Aug 12, 2013 at 8:13 AM, David Wolfskill da...@catwhisker.org wrote: I first noticed this on my laptop on 08 Aug, after having built booted FreeBSD 10.0-CURRENT #975 r253985M/253985:141: Tue Aug 6 05:28:39 PDT 2013 root@localhost:/common/S4/obj/usr/src/sys/CANARY i386

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread David Wolfskill
On Mon, Aug 12, 2013 at 08:30:15AM -0700, Davide Italiano wrote: ... Booting... GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread Davide Italiano
On Mon, Aug 12, 2013 at 9:01 AM, David Wolfskill da...@catwhisker.org wrote: On Mon, Aug 12, 2013 at 08:30:15AM -0700, Davide Italiano wrote: ... Booting... GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2013 The FreeBSD Project.

i386 panic

2013-08-12 Thread Sean Bruno
http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? Sean

make[6]: stopped in /usr/src/lib/bind/dns

2013-08-12 Thread AN
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #78 r253966: Mon Aug 5 14:42:05 CDT 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root:

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread David Wolfskill
On Mon, Aug 12, 2013 at 09:10:55AM -0700, Davide Italiano wrote: ... OK, I'm not sure I can make an immediate guess on where's the problem now (without access to my main workstation), so I think you need to wait tomorrow unless someone beats me to the punch. The best I can say is that maybe

Re: i386 panic

2013-08-12 Thread Super Bisquit
You need to enable PAE in the kernel to access that memory. I could be wrong. On Mon, Aug 12, 2013 at 3:43 PM, Sean Bruno sean_br...@yahoo.com wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly

Re: i386 panic

2013-08-12 Thread Sean Bruno
Yah, I don't want to access the RAM, I just want the ridiculous box to boot. I'm content, for this test settting, to nerf myself to 4G rams. Sean On Mon, 2013-08-12 at 17:59 -0400, Super Bisquit wrote: You need to enable PAE in the kernel to access that memory. I could be wrong. On

Re: i386 panic

2013-08-12 Thread Sean Bruno
On Mon, 2013-08-12 at 12:43 -0700, Sean Bruno wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to

Re: i386 panic

2013-08-12 Thread Super Bisquit
Download the source and build the PAE kernel. Do the build world. On Mon, Aug 12, 2013 at 7:02 PM, Sean Bruno sean_br...@yahoo.com wrote: On Mon, 2013-08-12 at 12:43 -0700, Sean Bruno wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is

Re: quick hack to support option VIMAGE on USB Ethernet

2013-08-12 Thread Craig Rodrigues
Shigeru shig...@iij.ad.jp wrote: Hi all, I hope to use option VIMAGE on RaspberryPi. So, I try to make a patch. http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff #There is a SD image for RaspberryPi at same place. But, I only test

Re: Notebook, Geforce Gtx 660M and ibtel HD

2013-08-12 Thread Paulo Henrique - BSDs Brasil
On 11/08/2013 16:37, Nenhum_de_Nos wrote: Hail, I am back to desktoo and FreeBSD, but I cant pass the simple test to make X alive. Xorg -configure detects two vga and two displays, but neither seems to work. On 9.2rc I got to show X, but deadlock soon after. Now I installed head, and

Re: i386 panic

2013-08-12 Thread Scott Long
On Aug 12, 2013, at 1:43 PM, Sean Bruno sean_br...@yahoo.com wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and

Re: quick hack to support option VIMAGE on USB Ethernet

2013-08-12 Thread YAMAMOTO Shigeru
Hi all, From: Craig Rodrigues rodr...@freebsd.org Subject: Re: quick hack to support option VIMAGE on USB Ethernet Date: Mon, 12 Aug 2013 17:52:39 -0700 I do not have a USB Ethernet device, and do not fully understand VIMAGE yet. Is your patch still necessary in CURRENT, after this patch was

Re: i386 panic

2013-08-12 Thread Sean Bruno
On Mon, 2013-08-12 at 21:36 -0600, Scott Long wrote: On Aug 12, 2013, at 1:43 PM, Sean Bruno sean_br...@yahoo.com wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386

Re: i386 panic

2013-08-12 Thread Adrian Chadd
... bug peter. And alfred. Alfred broke this stuff. :) -adrian On 12 August 2013 21:33, Sean Bruno sean_br...@yahoo.com wrote: On Mon, 2013-08-12 at 21:36 -0600, Scott Long wrote: On Aug 12, 2013, at 1:43 PM, Sean Bruno sean_br...@yahoo.com wrote:

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread Konstantin Belousov
On Mon, Aug 12, 2013 at 02:44:35PM -0700, David Wolfskill wrote: On Mon, Aug 12, 2013 at 09:10:55AM -0700, Davide Italiano wrote: ... OK, I'm not sure I can make an immediate guess on where's the problem now (without access to my main workstation), so I think you need to wait tomorrow

Re: i386 panic

2013-08-12 Thread Konstantin Belousov
On Mon, Aug 12, 2013 at 12:43:02PM -0700, Sean Bruno wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the