As confirmed by some people in this bug's thread, the problem appears to come from recent ACPI backports in the 2.6.17 kernel sources. Reassigning.
As confirmed by some people in this bug's thread, the problem appears to come from recent ACPI backports in the 2.6.17 kernel sources. Reassigning.