Date: Mon, 14 Mar 2005 22:05:01 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: alpm0: Could not allocate Bus space Message-ID: <20050314220411.F8240@carver.gumbysoft.com> In-Reply-To: <20050313064722.GG28983@cirb503493.alcatel.com.au> References: <20050308093405.GV57256@cirb503493.alcatel.com.au> <20050313064722.GG28983@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Mar 2005, Peter Jeremy wrote: > No bites from anyone else... > > On Tue, 2005-Mar-08 20:34:05 +1100, Peter Jeremy wrote: > >alpm0: <AcerLabs M15x3 Power Management Unit> at device 3.0 on pci0 > >alpm0: host/noslave 74K > >alpm0: 0x20 bytes of rid 0x14 res 4 failed. > > The request winds up with acpi_alloc_resource() and it returns NULL > because its resource list ( device_get_ivars(alpm0)->ad_rl ) is NULL. > If I disable ACPI then alpm0 attaches correctly. Does this make > sense? Is the SMB interface incompatible with ACPI? In many cases ACPI provides methods for poking at devices on SMB and exports those as ACPI services (i.e., thermal zones). -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050314220411.F8240>