Date: Tue, 5 Jan 2010 08:39:57 -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: <201001050839.57199.jhb@freebsd.org> In-Reply-To: <20100104223738.GP1616@uriah.heep.sax.de> References: <20091230082556.GD1637@uriah.heep.sax.de> <200912301122.28030.jhb@freebsd.org> <20100104223738.GP1616@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 04 January 2010 5:37:38 pm Joerg Wunsch wrote: > As John Baldwin wrote: > > > 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. > > It happens here: > > res = resource_list_alloc(rl, bus, dev, type, ®, start, end, count, > prefetch ? RF_PREFETCHABLE : 0); > if (res == NULL) { > /* > * If the allocation fails, clear the BAR and delete > * the resource list entry to force > * pci_alloc_resource() to allocate resources from the > * parent. > */ > resource_list_delete(rl, type, reg); > printf("resource_list_alloc() failed\n"); > start = 0; > > The printf() I added there triggers, and this resets "start" to 0. > > Where to proceed now? 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. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201001050839.57199.jhb>