Port-i386 archive

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

Re: ACPI runtime debugging




To: port-i386%NetBSD.org@localhost

Subject: Re: ACPI runtime debugging

From: Jukka Ruohonen <jruohonen%iki.fi@localhost>

Date: Wed, 14 Apr 2010 07:46:03 +0300


On Tue, Feb 02, 2010 at 12:07:34PM -0800, Jason Thorpe wrote:
> 
> On Jan 30, 2010, at 12:38 AM, Jukka Ruohonen wrote:
> 
> > ACPICA's own debugger is already hooked into ddb(4). Just drop into DDB and
> > call acpi_osd_debugger(). Also this requires a kernel with ACPI_DEBUG
> > option.
> 
> Maybe this should become a full-fledged DDB command that shows up in the
> DDB help, etc?

Just for the record: I haven't forgotten this. The general problem here is
that building the ACPICA debugger requires also the disassembler. Together
these add plenty of code:

     GENERIC:                        11180269
     GENERIC + ACPI_DEBUG:           11376086        + approx. 1 %

Naturally some #ifdefs could be added.

Given the amount of problems people have with ACPI, I am currently
investigating whether at least the debug output -features could be enabled
in stock GENERICs. (Unfortunately the ACPICA build system is somewhat
braindead.)

- Jukka.


References:

ACPI runtime debugging
From: Jukka Ruohonen

Re: ACPI runtime debugging
From: Bernd Ernesti

Re: ACPI runtime debugging
From: Jukka Ruohonen

Re: ACPI runtime debugging
From: Bernd Ernesti

Re: ACPI runtime debugging
From: Jukka Ruohonen

Re: ACPI runtime debugging
From: Jason Thorpe




Prev by Date: Re: ACPI Exception AE_NO_MEMORY

Next by Date: Re: ACPI Exception AE_NO_MEMORY

Previous by Thread: Re: ACPI runtime debugging

Next by Thread: PCI_$FOO_FIXUP vs. netbsd-5-0

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index