Re: cardbus not powered when ACPI is enabled

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 <lars.engels_at_0x20.net>
> > > > > Sender: owner-freebsd-current_at_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