Comment 35 for bug 152187

Let me explain why this is taking upstream so long to fix, as far as I understand it. It's not because they're not happy with the available patches or because they are "half-baked", it's because the bug occurs in code that is shared between different operating systems. In order for a fix to be applied upstream, there are a few things that need to happen. First of all, this needs to be fixed in ACPICA, the generic ACPI implementation that linux shares with most other OSes. Here we're almost there, ACPICA version 20080213 basically includes the necessary changes, but there is a typo in there that will definitely break things. Robert Moore is aware of this and I'm sure it will be corrected in their next version. The other thing that needs to happen is for the ACPICA changes to be integrated into linux. This involves source-to-source translation using a utility called acpisrc and making the necessary adjustments in the affected parts of the linux kernel and is generally only done at the beginning of a linux release cycle, hence already after ubuntu's kernel freeze (Yes, what I'm saying is that this issue won't be fixed upstream until 2.6.26). Waiting for this patch is not a good idea anyway, because it will be one big patch including all the acpica changes since the last merge 2007-10-10 (presumably, that's acpica 20070919).

But at least everybody agrees on what needs to be done and how this should be accomplished, so the final fix will probably be very similar to the patches we have now.