--+svXpSx+RSEd8UhP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 08, 2006 at 06:35:58PM +0100, Thomas Klausner wrote:
> Hi!
>=20
> With a kernel from 2006/02/07 ~0000 UTC with PCI_INTR_FIXUP,
> ACPI_VERBOSE, and ACPI_ACTIVATE_DEV I get:
                    ^^^^^^^^^^^^^^^^^
You should avoid using that one.

> acpi0 at mainbus0
> acpi0: using Intel ACPI CA subsystem version 20060113
> acpi0: X/RSDT: OemId <ASUS  ,A7V600-X,42302e31>, AslId <MSFT,31313031>
> acpi0: SCI interrupting at int 9
> acpi0: fixed-feature power button present
> acpi0: fixing up intr link \_SB_.LNKC
> acpi_allocate_resources: res=3D7
> acpi0: interrupt allocation failed \_SB_.LNKC
[...]
> What are these "interrupt allocation failed" messages about?

It is a direct consequence of the line right before it, a case our
code doesn't handle.  That code is very naive, anyway.

Do you actually need PCI_INTR_FIXUP to fix anything?

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--+svXpSx+RSEd8UhP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBQ+owMdgoQloHrPnoAQKCVAf/bN9Lj6FG2BGdxVjkDjfXqPdUm+8mm5RD
mLprsHqinQ3NCqg0hvuu7Ku7w6kN1ejY8GxFUX3WfIa1WWBZl7Cwa0ocz14rMClN
c5KIO5JfeybeenSBGghjYC57GT3Ho3xWJKxKadrjZbSUpdT+nPbN3f+ZYHTl/6mv
8Vk5m+NB6Cu5MU3wFCkO3m5RUNz/BiJYJXM7dvxt+kUnMffAI+61dwKYc6IQtHhR
g4DsPTt465nP6Jyfp1FGtvCdBRNNt8x2bOh8d4zkGOhH1nI9D5/MJQUJdkYp04RI
IF18eBL63T/3ytTqYnuTPsHtWeUOQMoXxxmzSJ0yfzxLedB2nK9Uiw==
=JPqU
-----END PGP SIGNATURE-----

--+svXpSx+RSEd8UhP--