Hi Chad, I'm sorry to say that this most likely wont be fixed in time for Feisty's release. In order to have a proper and stable release different parts of Ubuntu have to be frozen at different times, and the kernel was frozen back on April 5th: https://wiki.ubuntu.com/FeistyReleaseSchedule
Since this bug depends on a module being in the kernel, either raid45, dm-raid45 or raid456, this means this bug wont be fixed in time for Feisty. However, don't drop interest in the bug, we have to make sure it gets into Feisty +1 due in October.
Hi Chad, I'm sorry to say that this most likely wont be fixed in time for Feisty's release. In order to have a proper and stable release different parts of Ubuntu have to be frozen at different times, and the kernel was frozen back on April 5th: https:/ /wiki.ubuntu. com/FeistyRelea seSchedule
Since this bug depends on a module being in the kernel, either raid45, dm-raid45 or raid456, this means this bug wont be fixed in time for Feisty. However, don't drop interest in the bug, we have to make sure it gets into Feisty +1 due in October.
Because of this I'm unassigning myself from the bug and subscribing to both this and the one you indicated at https:/ /bugs.launchpad .net/ubuntu/ +source/ linux-source- 2.6.20/ +bug/97655