From owner-freebsd-stable@FreeBSD.ORG  Tue Mar 15 06:05:02 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3504A16A4CE
	for <freebsd-stable@freebsd.org>;
	Tue, 15 Mar 2005 06:05:02 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C415043D5E
	for <freebsd-stable@freebsd.org>;
	Tue, 15 Mar 2005 06:05:01 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id B20D672DDB; Mon, 14 Mar 2005 22:05:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id B055D72DD9;
	Mon, 14 Mar 2005 22:05:01 -0800 (PST)
Date: Mon, 14 Mar 2005 22:05:01 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: Peter Jeremy <PeterJeremy@optushome.com.au>
In-Reply-To: <20050313064722.GG28983@cirb503493.alcatel.com.au>
Message-ID: <20050314220411.F8240@carver.gumbysoft.com>
References: <20050308093405.GV57256@cirb503493.alcatel.com.au>
 <20050313064722.GG28983@cirb503493.alcatel.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-stable@freebsd.org
Subject: Re: alpm0: Could not allocate Bus space
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2005 06:05:02 -0000

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