Date: Wed, 30 Dec 2009 11:22:28 -0500 From: John Baldwin <jhb@freebsd.org> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-acpi@freebsd.org Subject: Re: FreeBSD 8.0 hangs on boot with ACPI enabled Message-ID: <200912301122.28030.jhb@freebsd.org> In-Reply-To: <20091230143943.GA1616@uriah.heep.sax.de> References: <20091230082556.GD1637@uriah.heep.sax.de> <200912300839.47463.jhb@freebsd.org> <20091230143943.GA1616@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 30 December 2009 9:39:43 am Joerg Wunsch wrote: > As John Baldwin wrote: > > > I'm guessing that ahc0 doesn't like the the I/O port resource range > > it was assigned in the ACPI case. No idea why ACPI would clobber > > that BAR. > > Hmm, indeed, I've been using a differen HBA in the past. Do you think > it would make sense using another HBA, like a Tekram one? I could > easily swap them. > > Anyway, the ahc0 at least can still find the attached drives while the > BIOS is running (otherwise it wouldn't boot at all). Isn't it using > the very same IO addresses then as FreeBSD with ACPI enabled? No, when ACPI is enabled the BAR is getting reset to 0 for some reason after the boot has started and FreeBSD tries to guess at an address to use. Unfortunately it picks an address that doesn't work. This is fixable, it's just part of the much larger PCI resource management problem. OTOH, I'm not sure why initializing ACPI is trashing the BAR. If you want, you can try to narrow down at what point the BAR gets reset to 0. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200912301122.28030.jhb>