DragonFly submit List (threaded) for 2006-12
DragonFly BSD
DragonFly submit List (threaded) for 2006-12
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: ACPI-CA update patch for review


From: YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>
Date: Sat, 2 Dec 2006 00:17:14 +0900

On Fri, Dec 01, 2006 at 04:01:04PM +0900, YONETANI Tomokazu wrote:
> > I copied by hand the ones i can see from boot -v with the options
> > you suggested:
> [dmesg output]
> 
> I'm afraid ACPI_LV_VERBOSE in debug.acpi.level wasn't enough to give us
> extra information.  Can you use the following two lines instead of the
> ones I wrote in the previous message?
>   debug.acpi.layer="ACPI_TABLES ACPI_EVENTS ACPI_NAMESPACE"
>   debug.acpi.level="ACPI_LV_FUNCTIONS ACPI_LV_INFO"
> 
> Judging from the dmesg output above and the one from older module, I think
> it's in the middle of AcpiInitializeTables(); or one of calls to
> AcpiInstallAddressSpaceHandler().  The "acpi_bus_number:" messages are
> displayed during the third call to it.

Ok, I saw a similar lock up on a machine I haven't updated since October --
before troubling your hand by writing down many function names, can you
try rebuilding your acpi driver with an environment variable
ACPI_USE_LOCAL_CACHE=yes ?
  $ /sys/dev/acpica5
  $ export ACPI_USE_LOCAL_CACHE=yes MAKEOBJDIRPREFIX=$HOME/obj
  $ make cleandir; make cleandir
  $ make obj && make depend && make && su root -c 'make install && reboot'



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]