Date: Mon, 23 May 2011 16:35:55 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org>, freebsd-acpi@FreeBSD.org Subject: Re: acpi resources problem potentially because of new pcib code Message-ID: <4DDA62BB.1080808@FreeBSD.org> In-Reply-To: <4DDA16FF.8080802@FreeBSD.org> References: <4DDA16FF.8080802@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 23/05/2011 11:12 Andriy Gapon said the following: > > John, > > it seems that possibly your recent changes for PCI bridges could have broken > something for my old 440BX/PIIX4/PIII type test machine. > Looks like now some I/O resources get assigned to a PCI bridge instead of ACPI. > > Some highlights follow: > ... > acpi_timer0: couldn't allocate resource (port 0x4008) > ... > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 > ... > device_attach: acpi_throttle0 attach returned 6 > > More data here: > http://people.freebsd.org/~avg/ms6163/ > > I see that _CRS of the Host-PCI bridge indeed claims that 0x4000 range, so I > realize that this is a BIOS bug, but I think that perhaps we could have some > quirk there to leave this range to ACPI. I fixed this for myself by creating a custom dsdt override where I moved the following resource from _CRS of Device PCI0 (PNP0A03) to that of Device SYSR (PNP0C02): IO (Decode16, 0x4000, // Range Minimum 0x4000, // Range Maximum 0x01, // Alignment 0x42, // Length ) Maybe this could help other people with similarly broken BIOSes. I hope that not too many systems with that hardware survived to these days, because it seems that almost all of them shared a lot of common bugs in their BIOS (and good luck getting any fixes for those systems from their vendors now). -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DDA62BB.1080808>