From owner-freebsd-current@FreeBSD.ORG Mon Apr 30 16:22:23 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 DEF1C16A404 for ; Mon, 30 Apr 2007 16:22:23 +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 176B913C46A for ; Mon, 30 Apr 2007 16:22:22 +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 l3UGLuHn014907; Mon, 30 Apr 2007 12:22:08 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Lars Engels Date: Mon, 30 Apr 2007 12:08:58 -0400 User-Agent: KMail/1.9.6 References: <20070423193112.GU46992@e.0x20.net> <200704261745.51595.jhb@freebsd.org> <20070427205752.GC96044@e.0x20.net> In-Reply-To: <20070427205752.GC96044@e.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704301208.59312.jhb@freebsd.org> 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 12:22:09 -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.3 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 16:22:24 -0000 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: > > On Monday 23 April 2007 04:14:34 pm Lars Engels wrote: > > > On Mon, Apr 23, 2007 at 01:03:00PM -0700, Kevin Oberman wrote: > > > > > Date: Mon, 23 Apr 2007 21:31:12 +0200 > > > > > From: Lars Engels > > > > > Sender: owner-freebsd-current@freebsd.org > > > > > > > > > > Hello, > > > > > > > > > > like I already described in another mail some weeks ago on my Samsung > > > > > Q35 notebook cards inserted into the pcmcia slot do not get powered=20 > > > > > with a kernel newer than from january.=20 > > > > > I now selected the option "Boot FreeBSD in Safe Mode" and the card is > > > > > powered and recognized. > > > > > After playing around in beastie.4th, disabling the entries > > > > > hint.acpi.0.disabled > > > > > loader.acpi_disabled_by_user > > > > > hint.apic.0.disabled > > > > > are causing the card to work. > > > > > > > > > > However, it does not work when I select "Boot with ACPI disabled". > > > > > > > > "Boot with ACPI disabled" only disables ACPI. Safe mode also disables > > > > APIC. > > > > > > > > Does the system boot correctly in safe mode? Does it boot with only APIC > > > > disabled but ACPI enabled? > > > > > > > > > Yes, it boots correctly with only APIC disabled and ACPI enabled. But > > > then I again have the cardbus problem. > > > > So it always boots ok? Which combinations of ACPI on/off and APIC on/off > > allow the cardbus card to work? > > Now the situation is: > > ACPI enabled, APIC enabled: works fine > ACPI disabled, APIC disabled: not recognized > ACPI disabled, APIC enabled: not recognized > ACPI enabled, APIC disabled: not recognized > > 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. -- John Baldwin