Date: Thu, 22 Aug 2002 19:29:31 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.ORG, Tomas Hodan <tomas@hodan.sk>, Andy Sparrow <spadger@best.com> Subject: Re: install crash on hp omnibook 6100 Message-ID: <20020822192553.U33737-100000@carver.gumbysoft.com> In-Reply-To: <XFMail.20020822110817.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Aug 2002, John Baldwin wrote: > > There is an issue with the HP laptop DSDT and our ACPI code. They > > initialize some child devices before initializing their parents, causing > > an infinite loop. The acpi-jp list doesn't seem interested in changing > > the way we do initialization, and theres no docs on the part it's > > initializing to rewrite the DSDT. > > Hmm, could you clarify. What child devices is it initializing first? Its trying to fetch some data from the cardbus controller before its been initialized, but its trying to do it in its own _REG routine or something... look for FDS_._REG; the CSID() function is what initiates the loop. Last time I looked at this was april, so I might have the exact details correct .. I have tracebacks and other data at http://people.freebsd.org/~dwhite/hp6000/ if you want to poke at it. (The 6000 and 6100 use the same ACPI code, I checked.) I attempted to post a note to the acpi-jp list in april asking about our architecture model but it appears to have never made it. We may need to revisit our assumption that ACPI can be initialized top-down. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020822192553.U33737-100000>