Date: Wed, 6 Jan 2010 13:43:16 -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: <201001061343.16098.jhb@freebsd.org> In-Reply-To: <20100105213907.GX1616@uriah.heep.sax.de> References: <20091230082556.GD1637@uriah.heep.sax.de> <201001050839.57199.jhb@freebsd.org> <20100105213907.GX1616@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 05 January 2010 4:39:07 pm Joerg Wunsch wrote: > As John Baldwin wrote: > > > So this is actually way too early. The specific issue I'm referring > > to is ACPI setting the BAR to zero when ACPI is initialized long > > before we ever get to this point. Hmmmmm. Can you get the output > > of 'devinfo -ur' with ACPI enabled? Also, you can maybe try setting > > 'debug.acpi.disabled=sysres' from the loader. > > Unfortunately, it's getting even more puzzling now. :-/ > > When I set debug.acpi.disabled=sysres in the loader, I no longer get > the resource allocation failure, thus ahc0 correctly gets the 0xde00 > IO address range. Nevertheless, the boot hangs by the time when it > wants to detect the disks. > > When I don't set debug.acpi.disabled=sysres, I'm back at the resource > allocation failure. > > The only way to boot FreeBSD 8 is to disable ACPI. > > Are you interested in the devinfo -ur output from the FreeBSD 6.2 boot > CD-ROM? I didn't spot anything interesting in it, but alas forgot to > save it from the serial console link into a file. Yes, I want to see what resources ACPI thinks the system resource devices should be using. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201001061343.16098.jhb>