Since I ran into this, I have done a complete fresh install of edgy. The problem disappeared with the fresh install. That leads me to believe that this is one of:
- Differences between the resulting images of upgrade and fresh install
- Problems introduced by one or more of the ACPI settings changes
- Incompatibilities caused by specific packages, such as that which would exist with mysql if the ACPI scripts weren't deliberately working around it.
For reference, I'm on a ThinkPad T42p, and the ec_intr=0 workaround had no effect.
TuxMe posted this workaround which I have not tried, but I don't see it listed here, so just in case it works for somebody... "[...] you might try appending the following parameters to your kernel entry in /etc/boot/menu.lst:
pci=noacpi acpi_sleep=s3_bios
[...]"
Since I ran into this, I have done a complete fresh install of edgy. The problem disappeared with the fresh install. That leads me to believe that this is one of:
- Differences between the resulting images of upgrade and fresh install
- Problems introduced by one or more of the ACPI settings changes
- Incompatibilities caused by specific packages, such as that which would exist with mysql if the ACPI scripts weren't deliberately working around it.
For reference, I'm on a ThinkPad T42p, and the ec_intr=0 workaround had no effect.
TuxMe posted this workaround which I have not tried, but I don't see it listed here, so just in case it works for somebody... "[...] you might try appending the following parameters to your kernel entry in /etc/boot/menu.lst:
pci=noacpi acpi_sleep=s3_bios
[...]"