Are you looking for an Ubuntu kernel patch for Lucid, or are you really asking for a 2.6.34 upstream patch?
If you're really asking for upstream, I'm sorry to say, the answer is "no". Let me explain.
We really don't want to add any more machines to that DMI table, and there has been quite a bit of effort upstream by Matthew Garrett to find the proper fix. I think he's pretty much got it now:
Matthew's patch should fix the bug once and for all. I believe it will be targeted for 2.6.35.
In the meantime, please use the kernel command line workaround "acpi_sleep=sci_force_enable". I know this is annoying, but should be quite manageable if you're adventurous enough to run an upstream kernel.
For Lucid, it's a different story. We can add an Ubuntu-specific patch to handle this machine.
@madbiologist, I'm a little confused.
Are you looking for an Ubuntu kernel patch for Lucid, or are you really asking for a 2.6.34 upstream patch?
If you're really asking for upstream, I'm sorry to say, the answer is "no". Let me explain.
We really don't want to add any more machines to that DMI table, and there has been quite a bit of effort upstream by Matthew Garrett to find the proper fix. I think he's pretty much got it now:
http:// thread. gmane.org/ gmane.linux. acpi.devel/ 45907
Matthew's patch should fix the bug once and for all. I believe it will be targeted for 2.6.35.
In the meantime, please use the kernel command line workaround "acpi_sleep= sci_force_ enable" . I know this is annoying, but should be quite manageable if you're adventurous enough to run an upstream kernel.
For Lucid, it's a different story. We can add an Ubuntu-specific patch to handle this machine.