The workaround mentioned by Roax (boot with acpi=force) is inappropriate in this case owing to ACPI-related problems on this laptop (ThinkPad A20m, 1999 BIOS). While booting with acpi=force is largely successful (save for some messages re modules not loaded to prevent EPROM damage), and while performance with acpi=force "seems better", S3 sleep is unreliable (recorded in other bugs).
So for the moment I am stuck with manually turning the machine off once "shutdown" is "complete". Ironically, restart works fine, the machine powers itself off and on again.
Note: Bug continues with latest Dapper (all updates as of 20060516) applied.
The workaround mentioned by Roax (boot with acpi=force) is inappropriate in this case owing to ACPI-related problems on this laptop (ThinkPad A20m, 1999 BIOS). While booting with acpi=force is largely successful (save for some messages re modules not loaded to prevent EPROM damage), and while performance with acpi=force "seems better", S3 sleep is unreliable (recorded in other bugs).
So for the moment I am stuck with manually turning the machine off once "shutdown" is "complete". Ironically, restart works fine, the machine powers itself off and on again.
Note: Bug continues with latest Dapper (all updates as of 20060516) applied.