Linux Kernel 2.6.3 Has Been Released [updated]

justinarthur writes "At 04:36 UTC, Linux kernel version 2.6.3 has been made available. As is typical, downloaders are advised to utilize a mirror upon file availability. There are many changes from version 2.6.2, including recent ALSA patches, XFS fixes, and updates in many other areas." Update: 02/18 14:15 GMT by T : Peter Willis points out that kernel 2.4.25 (changelog) was also released, and writes "Incidentally, a security advisory dated today states there is an exploit in kernels up to 2.4.24 and 2.6.2, but the two releases today don't seem to reflect any changes, so get ready to patch up as soon as a patch pops up. More details on the vulnerability here."

Comments

SCO's code is available for perusal

[ObviousGuy]

Wait until 2.6.4 when that code has been removed.

Re:SCO's code is available for perusal

[BrynM]

Wait until 2.6.4 when that code has been removed.

Yep, the ink's still wet and SCO will have to amend their filing. The wheels of justice churn onward... *cough* *cough* er... The hamster wheels in Darl's head keep churning. My mistake. Sorry. Sometimes the sqeeky justice wheels sound just like hamster wheels.

Re:SCO's code is available for perusal

[warmcat]

Many a true word is spoken in jest... copied from this Yahoo SCOX messageboard post (thanks to jgabriel66 and kevinmcb2004 for finding the site)

The full URL for the parent package is here:

http://linuxupdate.sco.com/scolinux/update/RPMS.up dates/glibc-devel-2.2.5-213.i5 86.rpm

Here is the kernel mentioned in the grandparent post

http://linuxupdate.sco.com/scolinux/update/RPMS.up dates/kernel-source-2.4.21-138 .i586.rpm

(as mentioned in the parents they have set up some kind of HTTP auth, but blank credentials work fine)

What is bizarre is that the files are still being updated while all this crap is going on. For example http://linuxupdate.sco.com/scolinux/update/RPMS.up dates/mc-4.5.55-719.i586.rpm is dated 17th Feb 2004.

Further the RPMs are cryptographically signed with GPG keys for both

SuSE Package Signing Key [9C800ACA]
Caldera Security [C4970D31]

This is proof that the files are deliberately approved and issued by Caldera/SCOX, signing packages is the most protected step that can happen in a company for its sources and binaries.

Further when I look at /usr/src/linux-2.4.21-138/COPYING I see... the GPL v2 with a note at the top by Linus as usual.

Its like the arms and legs of SCOX don't know what the 455h013 is saying. HEY IDIOTS, you're still GIVING AWAY on your websites, under the GPL, the stuff you're trying to shake down companies for!! AND ITS GPG-SIGNED BY YOU THAT IT IS OKAY!!!!

Re:SCO's code is available for perusal

[warmcat]

They have kernel source in a kernel-source package in the updates dir, the distro sources and apparatently by the date the rest of the update sources are here:

http://linuxupdate.sco.com/scolinux/SRPMS/

The thing is they are compliant to the GPL :-)

Today they put up a new web-based "buy a year's license for the SCO IP" thing on their website. But why bother when you can license any SCO IP under the GPL irrevocably and for free, from the same website? Its just madness from SCO.

Great work!

[Michael Iatrou]

$ cat ChangeLog-2.6.2 | grep -xP "<.*@.*>" | wc -l
1105

$ cat ChangeLog-2.6.3 | grep -xP "<.*@.*>" | wc -l
1260

155 more bug fixes from the last release... (yeah, I know, not a really sophisticated method...)

Re:Great work!

[Feztaa]

gazbo mentioned the unneccessary use of cat, you actually don't need any pipes at all:

$ grep -xP "<.*@.*>" ChangeLog-2.6.2 -c
1105

$ grep -xP "<.*@.*>" ChangeLog-2.6.3 -c
1260

Gentoo disappointment...

[dmayle]

I must admit to being a little disappointed right now with my Gentoo installation. I saw the article here, ran an emerge sync, and 2.6.3 is still marked as unstable. I guess I'll have to wait 15 minutes before I can install it... ;)

On a slightly related sidenote, whichever developer it was who "broke" support for the 105th key (the "Europe" key) in 2.6.1 should be drawn and quartered. It took me forever to figure out why my tilde key wasn't working. I created a text file called tilde with the character in it so that everytime I needed a tilde, I could copy and paste it... Aaarrggh

Re:Gentoo disappointment...

[Dahan]

At least I know that my fscking keyboard will work properly.

You may use Windows XP, but your keyboard must be running Linux, if it's always having to run fsck.

Re:Gentoo disappointment...

[vojtech]

That was me, thanks for the torture offer. ;)

Btw, the problem was that 2.6.1 actually supported the 103rd European key, and users couldn't cope with that. Now (2.6.2+) it's treated like a regular backslash key, even though they're two different keys in reality.

Re:Gentoo disappointment...

[dmayle]

I don't think it was that 2.6.1 supported the 103rd key, but that X doesn't. When I had 2.6.1 installed, X couldn't distinguish the key from the PrtScrn key, so there was no way to change the map file to support the key...

Changes include

[halfnerd]

KernelTrap reported "large merges" to 2.6.3-rc2, including:

network driver updates, compiler warning fixes, PPC updates, a major ALSA update and SCSI updates, NFSv4 update, XFS fixes, ARM and sparc updates

Re:Changes include

[halfnerd]

And as if that wasn't enough, -rc4 introduced these:

out-of-the-box ppc/ppc64 support, complete with G5 support (64-bit), large radeonfb driver updates, IDE oops fixes (and cleanups), and a SELinux update

Slashdot really should consider linking to kerneltrap for each kernel update that has to be reported...

Summary Redefined by Changelog

[Red Pointy Tail]

Summary of changes from v2.6.2 to v2.6.3

At a tidy 9472 lines, I think the word 'summary' needs a new definition...

Re:Summary Redefined by Changelog

[cassidyc]

that would be summary, as in not the full unabridged version.

CJC

distributions

[HoneyBunchesOfGoats]

Any idea when we'll start seeing 2.6 as the kernel included in the big distributions?

Re:distributions

[FooAtWFU]

I hear that it's the kernel in Fedora Core 2 test release 1.

Re:distributions

[RodeoBoy]

Fedora is scheduled for april, Debian and Suse by the summer. Start preparing now for the new install.

Changelogs..

[noselasd]

Those that wants detailed changelogs, or just wants to follow the very very latest changes/additions to the kernel source tree can do so here
2.4 kernel tracking can be done here

Damn it!

[Rysc]

I still haven't upgraded to 2.6.2!

I grabbed the patch, applied it, reconfigured, recompiled, and set up grub. I've been waiting and waiting but still have not suffered a single crash, so I have been unable to justify rebooting.

Is any distro already with 2.6 kernel series?

[ron_lima]

Is there already any distro with the kernel 2.6 series? I'm still waiting for the response of the market before going for kernel 2.6 yet. My 2.4.24 is really stable and running fine, but I'm anxious to see the threads improvements in 2.6...

Re:Is any distro already with 2.6 kernel series?

[mshiltonj]

Fedora Core 2 is running the 2.6 kernel. I hear from first impressions that the performance
improvements are nothing short of stunning, but I haven't tried it yet.

Re:Is any distro already with 2.6 kernel series?

[Ender Ryan]

To really see the threads performance improvements, you will need to recompile glibc with support for it. From what I understand, this will break a number of programs and cause some programs to not compile, so it's not really considered stable yet by most people.

OTOH, even without rebuilding glibc to take advantage of the new kernel-based pthread support, I have found really nice interactivity improvements on the desktop. It's really quite nice, I wouldn't want to go back to 2.4.

TODO:

[gazbo]

Locate and insert link to the "unnecessary use of cat" awards page.

And I don't mean having feline carnal knowledge.

Re:TODO:

[tcopeland]

> "unnecessary use of cat" awards page

Done.

Many's the time I've been guily of a

[tom@hal tom]$ cat pmdexport.xml | wc -l
42031
[tom@hal tom]$

when a

[tom@hal tom]$ wc -l pmdexport.xml
42031 pmdexport.xml
[tom@hal tom]$

would have done just as well...

Re:TODO:

[Anonymous Coward]

Here you go..
This is also a useless use of wc:
$ grep -cxP "" ChangeLog-2.6.3
1260

Re:TODO:

[Anonymous Coward]

One prog to read the lines, one prog to find them,
One prog to count the lines and to the console bind them.

Nforce fix went in

[motown]

[ACPI] nforce2 timer lockup from Maciej W. Rozycki

Oooh, does that mean I can finally enable both APIC and ACPI support in the kernel without experiencing lockups on my Nforce2-based system? I've been waiting for quite a while for this patch to go in. :)

But weren't there supposed to be two (complementary) patches for this problem out there?

len.brown@intel.com

Thanks Intel guy, for allowing this AMD fix to go in. :D

Radeon users will be happy

[CRCulver]

Previous kernels have never worked entirely well with my Mobile Radeon M6-P graphics card. Switching from radeon-powered X to radeonfb-powered console, or changing the resolution within radeonfb, would occasionally cause the screen to get all fuzzy, making me switch back and forth until it looked normal again.

But with the 2.6.3 kernel, there's a kickass new radeonfb driver that doesn't have any of these problems, and has improved collaboration with the BIOS to decide certain settings. No longer will peers think Linux must suck because my screen occasionally gets fuzzy.

However, I'm still only getting 435fps in glxgears with a 16MB graphics card at 1024x768 with DRI definitely on. Is this normal for a sucky notebook display card, or is there a problem with Linux's radeon gl support or my settings?

Re:Radeon users will be happy

[HoldmyCauls]

435 is a low number to you? For how long have you been working at Pixar? My Radeon Mobility M7 *occasionally* gets 70 or higher at that resolution, with that amount of video RAM. BTW, the reason it never *feels* like 435 fps is probably because you're running ATi's glxgears which somehow does *wonderfully* for testing. Tuxracer, RtCW, Unreal2003, whatever else you're using, don't have the same mysterious code that ATi's glxgears does, IIUC.

Re:Radeon users will be happy

[green pizza]

However, I'm still only getting 435fps in glxgears with a 16MB graphics card at 1024x768 with DRI definitely on.

I've heard that glxgears is a terrible benchmark, but it piqued my curiousity enough to fire it up on my PowerBook (Radeon Mobility 9600, Mac OS X 10.3.2 w/ optional X11 installed). With the window geometry set to 1024x768 I'm getting ~1800 to ~2700 fps, it really bounces around. Given that glxgears doesn't use any texturing nor any other wizbang new features, I'm guessing that something's not right on your end. Maybe it's even rendering with software?

Debian and Slackware already patched

[mst76]

According to the changelogs, Debian and Slackware already have the patches for the bounds checking error in place. I didn't check the other distributions. (Or rather, I don't know where to check most of them quickly.)

It still crashes :(

[motown]

The bug's still there. :(

The lockup can be easily triggered by running "hdparm -t /dev/hdX" (hdX being your harddrive) from the root prompt a couple of times.

I know, I know, it's easy (as well as unfair) for me to bitch and moan, since I'm not a kernel developer. But knowing that there are patches out there that could solve this problem, but still haven't made it into the kernel, it's frustrating.

For what it's worth: I haven't noticed any speed advantages between an APIC-enabled and non-APIC-enabled kernel, so I guess it's not too much of a loss.

Does anybody here have any better experiences with this?

Vulnerabitily fixed in 2.6.3 and 2.4.25

[Shanes]

At least acording to Linus .

ACPI cure for 2.4.25 HOW-TO

[Quietti]

Many people complained that kernels since 2.4.22 broke ACPI support on their hardware.

The cause is a brand new ACPI implementation which has a cutoff date of January 1st 2001. If your computer's BIOS is older than that, any ACPI support that might be present will be completely ignored by the kernel. ACPI hacker Len Brown explains that while the cutoff date is indeed arbitrary, it was already being used by certain distributions who noticed a pattern in when BIOSes with broken ACPI support where manufactured, so the ACPI hackers stuck by that concensus.

If you know for fact that ACPI worked fine on your computer until 2.4.21, you can enable it again: the cure is to put acpi=force in your bootloader configuration options.

Len also noted that there might eventually be a whitelist of older BIOS versions whose ACPI support is spotless. If you feel that your motherboard is one of those that should be whitelisted, file a bug at Kernel.org. Len makes absolutely no promise whatsoever that such a whitelist will ever be implemented, but still leaves the door open for people to manifest their interest via the above bug report form.