@Gonzhauser, thanks for trying the test kernel noted in comment #2 and confirming it fixes the issue. The next round of kernel updates would supersede the test kernel. However, it appears the next official Maverick kernel update will be an ABI bump, so you would have the option of selecting the older test kernel or the newer updated kernel.
Getting these patches accepted as a Maverick stable release update will be a bit difficult (ie it's not exactly appropriate to qualify for SRU). Even Linus himself has refused to accept these into the upstream 2.6.36 kernel as noted in https://patchwork.kernel.org/patch/189182/ "I definitely am not going to pull this series for 2.6.36. I could possibly take this first one that only prepares for the real change and doesn't actually change anything in itself, but switching around the order of allocations after -rc5 would be crazy. Yes, it may help some people, but we have absolutely no idea who it could hurt. So the whole thing is definitely something for the merge window (and preferably pretty early there too)" I have to agree that this is a very risky change with a high risk of regression which is always something that one tries to avoid when introducing changes/fixes to a released kernel. I still need to discuss with the rest of the Ubuntu Kernel SRU team, but we may just have to wait for this to resolve itself in Natty. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- Kernel Oops with Maverick in ahci_stop_engine https://bugs.launchpad.net/bugs/658560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
