From owner-freebsd-current@FreeBSD.ORG  Wed May  5 12:19:06 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 7978C106566C
	for <current@freebsd.org>; Wed,  5 May 2010 12:19:06 +0000 (UTC)
	(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
	[41.161.16.135])
	by mx1.freebsd.org (Postfix) with ESMTP id 0FBE68FC1D
	for <current@freebsd.org>; Wed,  5 May 2010 12:19:05 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
	by inbound01.jnb1.gp-online.net with esmtpsa
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
	(envelope-from <ianf@clue.co.za>) id 1O9dZ8-00016L-5B
	for current@freebsd.org; Wed, 05 May 2010 14:19:02 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
	by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <ianf@clue.co.za>) id 1O9dYv-0000Y2-1N
	for current@freebsd.org; Wed, 05 May 2010 14:18:49 +0200
To: current@freebsd.org
From: "Ian FREISLICH" <ianf@clue.co.za>
X-Attribution: BOFH
Date: Wed, 05 May 2010 14:18:49 +0200
Message-Id: <E1O9dYv-0000Y2-1N@clue.co.za>
Cc: 
Subject: acpi_hp fails attach at boot
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 May 2010 12:19:06 -0000

Hi

acpi_hp fails attach at boot, but if I load it manually in multi-user
it does attach.  I think this is because the acpi_hp module tries
to attach very early on before acpi_wmi which it depends on has
completed its attach:

[mini] ~ # grep ^acpi dmesg
acpi0: <061909 RSDT0044> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi_hp0: <HP ACPI-WMI Mapping> iomem 0xfed13000-0xfed19fff on acpi0
acpi_hp0: Couldn't find acpi_wmi device
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 7f700000 (3) failed
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_hp0: <HP ACPI-WMI Mapping> iomem 0xfed13000-0xfed19fff on acpi0
acpi_hp0: Couldn't find acpi_wmi device
acpi_ec0: <Embedded Controller: GPE 0x17> port 0x62,0x66 on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
acpi_button0: <Sleep Button> on acpi0
acpi_wmi0: <ACPI-WMI mapping> on acpi0
acpi_button1: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_acad0: <AC Adapter> on acpi0

If I 'kldload acpi_hp' once the system is booted I get:

acpi_wmi0: <ACPI-WMI mapping> on acpi0
acpi_hp0: <HP ACPI-WMI Mapping> on acpi0
acpi_hp0: HP event GUID detected, installing event handler
acpi_hp0: HP CMI GUID detected

acpi_wmi obviously waits for the right time before it attempts to
probe or attach.  How can I make acpi_hp do the same?

Ian

--
Ian Freislich