From owner-freebsd-acpi@FreeBSD.ORG  Wed Jul 26 08:15:06 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 87FA216A4DF;
	Wed, 26 Jul 2006 08:15:06 +0000 (UTC)
	(envelope-from ducrot@poupinou.org)
Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9E4D443D5F;
	Wed, 26 Jul 2006 08:15:05 +0000 (GMT)
	(envelope-from ducrot@poupinou.org)
Received: from ducrot by poup.poupinou.org with local (Exim)
	id 1G5eXo-0004Pt-00; Wed, 26 Jul 2006 10:15:04 +0200
Date: Wed, 26 Jul 2006 10:15:04 +0200
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20060726081504.GV17014@poupinou.org>
References: <20060724215014.GA89464@troutmask.apl.washington.edu>
	<200607241823.24477.jhb@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200607241823.24477.jhb@freebsd.org>
User-Agent: Mutt/1.5.9i
From: Bruno Ducrot <ducrot@poupinou.org>
Cc: freebsd-acpi@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: Alienware acpi problem
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 08:15:06 -0000

Hi,

On Mon, Jul 24, 2006 at 06:23:24PM -0400, John Baldwin wrote:
> On Monday 24 July 2006 17:50, Steve Kargl wrote:
> > ACPI gurus,
> > 
> > My colleague has installed FreeBSD 6.1-table onto his
> > Alienware MJ-12 laptop.  During the boot process, we
> > see
> > 
> > acpi0: [MPSAFE]
> >     ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.PIB_.LNKH] in namespace, 
> AE_NOT_FOUND
> > SearchNode 0xffffff000091c240 StartNode 0xffffff000091c240 ReturnNode 0
> >     ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace, 
> AE_NOT_FOUND
> > SearchNode 0xffffff00009084c0 StartNode 0xffffff00009084c0 ReturnNode 0
> >     ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace, 
> AE_NOT_FOUND
> > SearchNode 0xffffff00008eb200 StartNode 0xffffff00008eb200 ReturnNode 0
> >     ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNKH] in namespace, 
> AE_NOT_FOUND
> > SearchNode 0xffffff0000909d40 StartNode 0xffffff0000909d40 ReturnNode 0
> 
> Well, that's probably why cardbus is broken.  Can you get the output of 
> acpidump?  Specifically I'd be interested in the parts that mention LNKH (as 
> well as where it actually lives in the device tree).
> 

>From the dmesg:

pccard0: <16-bit PCCard bus> on cbb0
pcib0: matched entry for 0.5.INTA
pcib0: slot 5 INTA hardwired to IRQ 18
ioapic0: routing intpin 18 (PCI IRQ 18) to vector 49

Note the INTA which, I think, isn't related to
a Device (LNKH) but maybe a Device (LNKA) from the ASL
pointed from another mail.

I'm not sure at all, though.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.