Bug 1355

Created attachment 1051 [details]
dmesg

latest dmesg

Created attachment 1052 [details]
messages log

the first 2 lines are the last message before system close.... no error was
report on poweroff

Created attachment 1053 [details]
lspci -vv

Created attachment 1054 [details]
dmidecode

Created attachment 1055 [details]
acpidmp

Hmm, poweroff worked on this box 2.4.22, but fails in 2.6.0... 
Can you try 2.4.23? 
If it fails, we probably broke all the releases. 
if it works, then this may be 2.6 specific. 
 
thanks, 
-Len 
 

kernel 2.4.23-rc1: shutdown regular - system go down without error.
kernel 2.6.0-test9 including bk20 - system remain up. echo "5" in
/proc/acpi/sleep do nothing (no message, no error). poweroff or init 1 kill all,
close all application, make shutdown regularly, but remain with message
acpi_power_off (same message and no error displayed in al *-bk* o
kenel-2.6-test* tried since now.
tried disable sleep support from kernel - no changes.
tried change acpi modules from static to modular - no changes. System remain
damned on.
ask me every test o logfile you think may be usefull a I'll send to you.

This appears to be a dup of bug #1141.

Mauro, 
can you test 2.4.23-rc2 or later to see that we haven't broken 2.4.23 also (bug #1619) on your 
system? 
 
thanks, 
-Len 
 

tested kernel 2.4.22 (all rc* versions) and kernel 2.4.23 and I've found
something curious: normally all versions work well and system go off, but if I
start kernel 2.6.0-test and then  I reboot with a kernel 2.4.22/23 the  system
fail to poweroff  and remain with a message like 'flushing device hdx'
powerdown. In this case, if I detach all kind of power sources (AC and Battery)
next poweroff with 2.4.22/3 system go down as we expect.
It seems that some register, some information remains active throught the reboot.

Good to know that 2.4.22 or 2.4.23 by themselves powerdown properly. 
 
Is it true that any 2.4 or 2.6 kernel booted after a 2.6-reboot fails to power down? 
 
Does 2.6 powedown properly if 2.6 is booted from hard-power-off? 
If so, does the 2.4 or 2.6 kernel booted after that also power down properly? 
 
If yes, then this issue is specific to 2.6 reboot/reset. 
 
thanks, 
-Len 
 

I've made some test powering off different kernel starting from 2.4.22 to
2.6.test11. So this the results:

      first boot    init  off   second boot   init  off
      2.6.0-test11  6     x     2.4.22        0     ok
      2.4.22        0     ok    2.4.22        0     ok
      2.6.0-test11  0     fail  2.4.22        0     ok
      2.6.0-test11  0     fail  2.4.22-rc3    0     ok
      2.4.22-rc3    0     ok    2.4.22-rc3    0     ok
      2.4.22-rc3    0     ok    2.6.0-test11  0     fail
      2.6.0-test11  0     fail  2.4.22-rc4    0     ok
      2.4.22-rc4    0     ok    2.4.22-rc4    0     ok
      2.4.22-rc4    0     ok    2.4.22-rc5    0     ok
      2.4.22-rc5    0     ok    2.4.22-rc5    0     ok
      2.4.22-rc5    0     ok    2.4.22-rc5    0     fail
      2.4.22-rc5    0     fail  2.4.22-rc.5   0     ok
      
                                                                               
                  
kernel 2.4.22 to rc4 ok.
kernel 2.4.22-rc5 do correct off one time yes and one time no.
2.6.xx never do correct off.

I'm almost embarassed to write in so many acpi-bugs, but have you tried the
patch from here: http://bugme.osdl.org/show_bug.cgi?id=1141#c5

re: 2.6 poweroff always failing 
good -- something that is reproducible is easier to debug. 
Does this still happen with recent 2.6? 
 
re: 2.4.22 rc5 sometimes not working, when rc4 always worked. 
Sicne 2.4.23 (and presumably 2.4.24), work, I'm not going to worry about 2.4.22-rc5 
being intermittant. 
 

ACER Travelmate 634LC Gentoo 
ALI-Chipset 
 
Yes patch tried, with or without, system doesn't shut down ("acpi_power_off called" 
message) 
Tried 2.6.0, 2.6.1, 2.6.2, 2.6.3 
Works well with all 2.4.XX-versions since 2.4.21 

try kernel option : nolapic

--Luming

no success :-( 

how about http://bugzilla.kernel.org/attachment.cgi?id=723&action=view

Patcherrors on 2.6.1, but 2.6.3 was patchable, please tell what I have to patch :) 
 
Make kernel 2.6.3 with the patch gives me  errors. 
... 
  CHK     include/linux/compile.h 
  CC      drivers/acpi/hardware/hwsleep.o 
drivers/acpi/hardware/hwsleep.c: In function `acpi_enter_sleep_state': 
drivers/acpi/hardware/hwsleep.c:214: Warnung: unused variable `PM1control' 
drivers/acpi/hardware/hwsleep.c:304: Warnung: label `re_write' defined but not used 
drivers/acpi/hardware/hwsleep.c: In function `acpi_leave_sleep_state': 
drivers/acpi/hardware/hwsleep.c:434: error: `PM1control' undeclared (first use in this 
function) 
drivers/acpi/hardware/hwsleep.c:434: error: (Each undeclared identifier is reported 
only once 
drivers/acpi/hardware/hwsleep.c:434: error: for each function it appears in.) 
drivers/acpi/hardware/hwsleep.c:439: error: label `re_write' used but not defined 
make[3]: *** [drivers/acpi/hardware/hwsleep.o] Fehler 1 
make[2]: *** [drivers/acpi/hardware] Fehler 2 
make[1]: *** [drivers/acpi] Fehler 2 
make: *** [drivers] Fehler 2 
... 
acpi_power_off bug still present, no success :-( 

Same problem on an old machine/kernel using APM, kernel 2.6.3. 

Could you please check if this problem still exists in latest kernel?

Ok. I think i've fount some hints. 
Compiling the kernel with no apic and no local apic the system go down 
perfectly. 
I tested this solution with kernel 2.6.7 and 2.6.8.1, so the problem is not in 
the acpi core, but, I think, in the relation between acpi and apic. 
 

Re: no-APIC poweroff works...
This is interesting, because another submitter above wrote
that "nolapic" made no difference.  perhaps a different failure
on that box...  Can you verify that "nolapic" on an APIC+IOAPIC
enabled kernel also works?

I wonder also if this is involved:
ACPI: BOOT (v001 INSYDE SYS_BOOT 0x00000100 _CSI 0x00010101) @ 0x1f7ffb90

SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1

since this is an example where some state is preserved across boot.

test about lapic/apic 
 
kernel 2.6.8.1 
gcc 3.4.0 
 
kernel compiled with apic and lapic on by default. 
 
trying boot with: 
 
only noapic: poweroff fail 
only nolapic: poweroff success 
noapic & nolapic: poweroff success 
with apic & lapic: poweroff fail. 
 
from dmesg: 
ACPI: BOOT (v001 INSYDE SYS_BOOT 0x00000100 _CSI 0x00010101) @ 0x1f7ffb90 
 
about ACPI BOOT 
 
 

Created attachment 3859 [details]
Patch to shutdown local APIC at poweroff 

Could you please try the following patch? It looks like forcefully enabled APIC
should be disabled before power off...

*** This bug has been marked as a duplicate of 3643 ***