| |||||||||||||
|
| |||||||||||||
Which kernel is targeted?Which kernel is targeted?Posted Jun 30, 2008 14:21 UTC (Mon) by nhippi (subscriber, #34640)In reply to: Which kernel is targeted? by callegar Parent article: The first Ubuntu "Intrepid" alpha release
The solution is known (custom compiled kernels from kernel.org such as 2.6.25.9 do not show the issue, as the system from which I am writing this message proves)Thats not a solution for a distro. Since only hardy users with problems upgrade to 2.6.25.9, it very much possible 2.6.25.9 has regressions for *other* users. You can't just blindly upgrade to a new kernel version when you have a very wide userbase with lots of different hardware... Since you are competent enough to compile your own kernel, you might help and use "git bisect" to find the change in kernel that makes it work again.
(Log in to post comments)
Which kernel is targeted? Posted Jun 30, 2008 16:11 UTC (Mon) by callegar (guest, #16148) [Link] Following this reasoning to an extreme, since there were already bug reports about 2.6.24 showing freezing regressions for some users, why have I been encouraged by the same distro to blindly upgrade from the 2.6.22 that gusty had without any warning in the release notes? On the other hand, given that 2.6.25 is at .9 I would say that it should have received some testing by now. Maybe it has a larger userbase than 2.6.24. And anyway: I am not suggesting that all hardy users are forced to upgrade to 2.6.25.9. I am just suggesting that in one way or another some kernel that does not freeze is provided. Maybe 2.6.25 can be provided through a dedicated channel (e.g. ppa or whatever) with as many scaring warnings as needed. For what concerns bisecting, I will not do it. Compiling a kernel takes a night on my slow host. Bisecting and testing a bug that causes a freeze every few hours could take a fortnight or more. It is just not an option and IMHO is a waste of time since the bug has anyway been fixed upstream and the kernel developers have moved over. And even assuming that I can identify the spot to be changed, where is the guarantee that the backported changes do not cause regressions to other users? Personally, I feel better using a pristine, vastly tested 2.6.25.9 than a 2.6.24 patched by myself with stuff taken from 2.6.25.9. But if someone wants host them, I am more than willing to share my kernel image and headers debs.
|
|
||||||||||||