A brief discussion on the lkml looked at which 2.6 Linux kernel patchset offers the best stability. Only four patchsets were mentioned, the bleeding edge -bk snapshots, Andrew Morton [interview]'s -mm patchset [story], Con Kolivas [interview]'s -ck patchset [forum], and Alan Cox [interview]'s -ac patchset [story]. When it was suggested that the -ac patchset was the most stable, and that -mm might be too bleeding edge, Alan offered some insight:
""2.6.x-mm [forum] is more like some of the work the old 2.4-ac [forum] did in merging new stuff (its also worth noting that 2.4-ac ended up more stable than 2.4 at times so -mm might be stable)
"The -ac tree is trying to be fairly conservative. When I merge stuff that is a little less conservative because it has to be done then I've tried to put a note in the relnotes for that release warning people its more testing grade.
From: Maciej Soltysiak [email blocked] To: [email blocked] Subject: 2.6 flavours Date: Thu, 16 Dec 2004 21:13:56 +0100 Hi, AFAICS the -ac tree should be the most stable of all kernels, right? -mm is totally bleeding edge -bk the same -ck is experimental Others are experimental too. Looking at the changelogs, the most reasonable kernel to use for generic use are the -ac kernels, which I am going to use since 2.6.10 as long as Alan is kindly going to continue his fabulous work. I swear not to use 2.6.10 until Alan publishes 2.6.10-ac1 :-) Regards, Maciej
From: Jurriaan [email blocked] Subject: Re: 2.6 flavours Date: Thu, 16 Dec 2004 21:37:40 +0100 ^gt; From: Maciej Soltysiak: > Hi, > > AFAICS the -ac tree should be the most stable of all kernels, right? > > -mm is totally bleeding edge I don't agree there. It is bleeding edge, but Andrew makes a conscious decision when to release it, and I'm sure part of that decision is thinking about when things will be stable enough to work for many people. > -bk the same bk is the central repository, and depending on when you pull it, you may have just catched Linus asleep after merging patch 1, meaning the tree is unstable until he wakes up and merges patch 2. There is no conscious 'release moment' - this is totally bleeding edge. > -ck is experimental There are 'release moments' here too. > > Others are experimental too. > > Looking at the changelogs, the most reasonable kernel to use for > generic use are the -ac kernels, which I am going to use since 2.6.10 > as long as Alan is kindly going to continue his fabulous work. I've understood the 2.6.x-ac kernels started with some ide work, then included some serial fixes, and may or may not have other bug fixes. >From what I read, they are not as all-including as the 2.4.x-ac kernels were. Those I recognize most in the 2.6.x-mm kernels. > > I swear not to use 2.6.10 until Alan publishes 2.6.10-ac1 :-) > Whatever you think best, of course. That may be the release where Alan says 'Here's the new, experimental next-generation SATA code. It'll probably break every partition you have. Send me bug-reports' :-) My way of keeping my home system up is to test a new kernel first on my laptop (which has good backups and little configuration), then read this list for some days and then install it on my main workstation (which also has good backups). Only after some weeks quiet I think about such a kernel on my firewall/router. Keeping backups helps when testing kernels. YMMV, Jurriaan -- I never think, sir. Didn't get a degree. Chief Inspector Morse Debian (Unstable) GNU/Linux 2.6.10-rc3 2x6078 bogomips load 0.23
From: Alan Cox [email blocked] Subject: Re: 2.6 flavours Date: Thu, 16 Dec 2004 19:54:54 +0000 On Iau, 2004-12-16 at 20:37, Jurriaan wrote: > I've understood the 2.6.x-ac kernels started with some ide work, then > included some serial fixes, and may or may not have other bug fixes. > >From what I read, they are not as all-including as the 2.4.x-ac kernels > were. Those I recognize most in the 2.6.x-mm kernels. 2.6.x-mm is more like some of the work the old 2.4-ac did in merging new stuff (its also worth noting that 2.4-ac ended up more stable than 2.4 at times so -mm might be stable) The -ac tree is trying to be fairly conservative. When I merge stuff that is a little less conservative because it has to be done then I've tried to put a note in the relnotes for that release warning people its more testing grade. > Whatever you think best, of course. That may be the release where Alan > says 'Here's the new, experimental next-generation SATA code. It'll > probably break every partition you have. Send me bug-reports' :-) That would be Jeff 8)
From: Con Kolivas [email blocked] Subject: Re: 2.6 flavours Date: Fri, 17 Dec 2004 13:05:25 +1100 Jurriaan wrote: > From: Maciej Soltysiak [email blocked] >>-ck is experimental > > > There are 'release moments' here too. I keep releasing versions till it is stable. eg 2.6.9-ck3 is more stable than 2.6.9-ck1. 2.6.8.1-ck9 is more stable than 2.6.8.1 (for my users at least). Cheers, Con
cko
I presonally prefer the CKO-patch set, which is based on CK, but has some additional 'nice to have' features like up to date ACPI, Reiser4, Supermount, ska3, up to date ALSA, LIRC, BT and variable HZ setting to name a few. I probably wouldn't put that in any of my servers, but it sure makes a good desktop kernel add-on. It's available here: http://kem.p.lodz.pl/~peter/cko/
-AC is the most stable
.. I think :) it's the only kernel that suspends my lappy right (Dell Precision M60), and it never failed me so far...
-mm had gone far too unstable, doesn't even boot for me from time to time
-ck was fast and had some nice patches, but it feels broken lately (X lag, VM is b0rked afaik, nice schedulers but vanilla feels better lately:/ I think it has far too many patches, should be simpler and faster)
-cko.. the same as -ck, except it is b0rked even more... but the ultimate way to have reiser4 in kernel :)
-bk
just a snapshot, fixes things sooner if something goes wrong in the mainstream
cko
> -cko.. the same as -ck, except it is b0rked even more... but
> the ultimate way to have reiser4 in kernel :)
cko3 might be a bit goofed up, but I generally prefer CKOs. Thanks to the ACPI updates, my Thinkpad's ACPI actually works instead of just freezing up when going to sleep mode. 2.6.9-cko4 was supposed to fix the lagginess, but I think they're waiting for 2.6.10 to appear.
Anyway, there's two things I wouldn't ever change, the other is CKO and the other my .. err .. socks :)
Well if you use a workstation
Well if you use a workstation, and on 2.6.8.1, the ck/cko patchset is really impressive compare to any others. Fast, Stable ( 33 days uptime on main ws so far ) and it is simply visibly more responsive than all others i tested ( ac, mm, vanilla). Well done.
Too scared to move to 2.6.9, might wait for 2.6.10.
I've had nothing but trouble
I've had nothing but trouble with that patchset on 2.6.9. For some reason, to maximize a window from the gnome taskbar you have to mouse over the current window. I've also seen the gnome taskbar disappear completly and nautilus crash. As for the responsiveness, it has been nothing more than mediocore.
My vote for most stable most defineatly goes to -ac.
I have those problems with 2.
I have those problems with 2.6.9 vanilla, i wouldnt blame ck/cko for that
Reiser4
> -cko.. the same as -ck, except it is b0rked even more... but
> the ultimate way to have reiser4 in kernel
Reiser4 is easy to backport from -mm tree on any linux 2.6 tree.
All you need to do is copy fs/reiserfs4 directory and fs/Kconfig.reiser4 from -mm tree to any linux 2.6 tree (this could vanilla, -ac, -ck etc).
And apply the below patch your linux-2.6 tree using patch -p1:
Disclaimer: I am not an expert at kernel hacking. This has proven to work for me and has allowed to use ReiserFS4 with -ac.
Reiser4
More changes are needed for reiser4, best bet is either to use one from:
ftp://ftp.namesys.com/pub/reiser4-for-2.6/
or grab it from -mm and apply using quilt (edit series file to contain all those reiser4-* patches, then: quilt push -a).
Reiser4
You need also to edit fs/Makefile
vanilla
What about the vanilla kernels (e.g., from kernel.org)? I'm using 2.6.10-rc3 patched solely with vesafb-tng for better framebuffer support (http://dev.gentoo.org/~spock/projects/vesafb-tng/). It runs very nicely and I have yet to have a single problem with it.
ok too
The vanilla kernels are perfectly good for most of the people. Us non-people again want to spend hours of patching and tuning our boxes :)
Vanilla - security holes
Vanilla kernels tend not to have the security holes all fixed especially release ones (2.6.9 has numerous holes). 2.6.10-rc has holes not yet fixed that are fixed in the various other branches too but which one hopes will be fixed by 2.6.10 final.
rc3 is the most stable in a
rc3 is the most stable in a while for me. Even mm's patches compile clean. The packet writing is mostly fixed. No need to use ide-scsi anymore, takes a bit getting used to if you always used it, but works better for me.
How work all the usb stuff ?
How work all the usb stuff ?
Re: How work all the usb stuff ?
Hi!
I can only tell that rc3 seems to be the most stable and working-fine-with-my-hardware (thinkpad r40 with a cheap atmel pcmcia wireless card) kernel as well and as far as usb-support is concerned: works just fine and better than any other 2.6.x kernel for me as of yet (my palm t-e with cardexport to fake an usb mass-storage device works fine and most memory sticks as well, usb mouse always worked, scanner [epson something] too).
merry x-mas everyone and [if possible] a peaceful holiday!
regards,
- benjamin
I prefer no-sources...
I use a new patchset, no-sources. Basically, it's mm-based with some preempt patches added, nvidia fixed, reiser4, and cfq-timeslices. You might wanna check it out.
http://no.oldos.org/files/
If you ask me, more focus nee
If you ask me, more focus needs to be made on QC'ing the released sources. We had 2.6.8.0/2.6.8.1, with the major cdrecording bug. Then 2.6.9, which has some network exploits, and some other problems. And yet, no mew release to fix these problems.
Not everyone depends on RedHat for kernels, people!
Vanilla 2.6.7
This is probably the most stablest release.
2.6.10-rc3-ck[1,2] is wonderf
2.6.10-rc3-ck[1,2] is wonderfully stable for me. I have high hopes for 2.6.10. Looks like Andrew and Linus finally want a "little bit" more stable release...
security patchsets :)
I prefer A) Bleeding edge prepatches for PaX; or B) Current gentoo hardened-dev-sources, whichever is more up-to-date. I just like what PaX and GrSecurity do for security; and I never have stability problems.
Of course I'm also the type who's after the Realtime patches for Linux ;) Performance, stability, and security aren't mutually exclusive though. Not by nature anyway. . . (though PaX doesn't work correctly with the CK patches last I checked; it could be made to).