From owner-freebsd-current@FreeBSD.ORG Mon Apr 30 17:38:07 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2111016A400 for ; Mon, 30 Apr 2007 17:38:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id BE46B13C45A for ; Mon, 30 Apr 2007 17:38:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l3UHbobS015350; Mon, 30 Apr 2007 13:37:52 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Lars Engels Date: Mon, 30 Apr 2007 13:36:41 -0400 User-Agent: KMail/1.9.6 References: <20070423193112.GU46992@e.0x20.net> <200704301208.59312.jhb@freebsd.org> <20070430170204.GA88409@e.0x20.net> In-Reply-To: <20070430170204.GA88409@e.0x20.net> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200704301336.41897.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 30 Apr 2007 13:37:58 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3184/Mon Apr 30 09:51:57 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org Subject: Re: cardbus not powered when ACPI is enabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2007 17:38:07 -0000 On Monday 30 April 2007 01:02:04 pm Lars Engels wrote: > On Mon, Apr 30, 2007 at 12:08:58PM -0400, John Baldwin wrote: > > On Friday 27 April 2007 04:57:52 pm Lars Engels wrote: > > > On Thu, Apr 26, 2007 at 05:45:50PM -0400, John Baldwin wrote: > > > > > > I also encountered occasional "Panic: failed to create swap zone" when > > > CPU #1 was launched just before the disks get mounted. Could that be > > > related? > > > > Ok, so for the default setup, the only problem is that panic? That sounds > > like running out of kvm possibly as the swapzone is preallocated from kmem. > > The system may be allocating too much for the swapzone, in which case you can > > explicitly set the size via the 'kern.maxswzone' tunable. One possible > > formula for this is: > > > > maxswzone = (swap + 1024) * 1024 * 9 / 2 > > > > Where 'swap' is the amount of swap in megabytes. > > I added kern.maxswzone=13953024 (2004 MB swap) to loader.conf but after > a reboot the oid is still unknown. Do I need to set it somewhere else? Unfortunately, it's just a tunable, there isn't a sysctl to see the current setting. You can, however, look at the 'vmstat -z' output. You can figure out the current swap zone size by multiplying the size and limit columns for 'SWAPMETA'. Something like this: vmstat -z | awk '/^SWAPMETA/ { printf "%d\n", $2 * $3 }' | bc -- John Baldwin