On 5/31/07, LarsBjerregaard <[EMAIL PROTECTED]> wrote: > This is FIXED in Debian! I'm sorry, but I have to say that I find it > disheartening, that bug https://bugs.launchpad.net/ubuntu/+source/linux- > source-2.6.20/+bug/116996 is still unconfirmed+undecided, bug > https://bugs.launchpad.net/ubuntu/+source/linux- > source-2.6.20/+bug/117447 is unconfirmed+undecided, and bug > https://bugs.launchpad.net/ubuntu/+source/linux- > source-2.6.20/+bug/117314 is unconfirmed, though recognized as status > high. > > Please devs! You are probably overburdened, that's understood. BUT.... > this bug is wrecking the systems of a hell of a lot of users, and if far > worse than the X-oops update you released some time ago. This one is > GRAVE, as the Debian bug correctly states. Please please... fix this. > Thank you.
I'm monitoring the situation, and trying to decide what is the best way to resolve this. The reversion from libata for PATA to the older IDE drivers was done to fix a large number of bugs people were experiencing with the feisty final kernel. Happily it has fixed a number of problems, and many systems are now correctly working for the first time. Unhappily, the bad behaviour that other people are experiencing with the reversion wasn't intended. A wholesale re-reversion of the libata isn't an option because this will cause devices to change again for everyone, and everyone will be quite understandably upset. The ideal solution to this is to selectively re-revert to libata for the people experiencing these problems. Unfortunately, this takes time to work out exactly what hardware isn't working and to only revert that. Please continue sending bug reports. Thanks -- latest kernel(2.6.20-16.28) update gives boot problems https://bugs.launchpad.net/bugs/117314 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
