Re: ACPI issues (maybe)

[YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>]

Hi.
Please post any bug reports to bugs@, whether it's ACPI-related or
not.

On Fri, Mar 02, 2007 at 08:18:05PM -0500, Joe Talbott wrote:
> I am experiencing some weird behavior with my Toshiba Satellite
> M115-S3094 Laptop.  I cannot power off the laptop with shutdown or
> reboot.  Both go through the steps of shutting down the machine but it
> never powers off.  I've tried setting hw.acpi.disable_on_poweroff to 1
> to no avail.  I have to press the power button for 5 or so seconds for
> it to power off.  So I've been using 'shutdown -h ...' which lets me
> tap the power button to power off the laptop but this often leaves the
> speakers beeping throughout the shutdown process.

Is this bug new in 1.8?  Do you experience this problem when you
run a UP kernel?

> When doing a 'shutdown -p ...' I do see a message like "Powering off
> via ACPI" or some similar text flash on the screen before the LCD is
> blanked, but it isn't completely powered off.
> 
> So I tried adding "options ACPI_DEBUG" to my kernel config and rebuilt
> my kernel.  This left me with a clock that ran at about 1 minute per 1
> second of real time.

That's how you enable some debugging features when the acpi driver is
compiled in the kernel.  However, compiling the ACPI driver in the kernel
is not supported at the moment, as some modifications to ACPI-CA code are
given as *.patch files in /sys/dev/acpica5 and those are not used when
compiled in the kernel (I believe there's a few other drivers which also
use *.patch files, but I haven't tried to see if these are not used either).
To compile an acpi driver with debugging feature enabled for an SMP kernel,
you do:
  export ACPI_DEBUG=yes CFLAGS='-O -pipe -DSMP=1'
for bourne shell users, or for *csh,
  setenv ACPI_DEBUG yes
  setenv CFLAGS '-O -pipe -DSMP=1'

> Oddly none of the sysctl nodes for hw.acpi were
> available with this kernel option added.  I don't know if this is due
> to acpi being loaded as a module or what.

Sounds like ACPI driver failed to load.  Do you have this problem
when you boot with ACPI disabled (debug.acpi.disabled="acpi" in the
boot loader)?

Cheers.