Linux 2.6.36-rc1 Kernel Released

[monraaf]

For instance someone posts a patch to fix some problem in the drm for r600/r700, that patch could possibly also apply to Evergreen drm code, but the Evergreen drm code for some reason is not updated. Result: Bug fixed in r600/r700, bug still present in Evergreen.

[bridgman]

Sure, I guess that could happen in theory, but nearly all of the 6xx/7xx drm patches came from agd5f, who is actively testing/fixing the Evergreen code as well.

[ssam]

How badly does an rc1 kernel usually hurt when it misbehaves? I crave those drm and responsiveness improvements...

worst case was the corrupting of firmware for a specific network card, leaving the computer with no network.

http://lwn.net/Articles/300202/

there was a workaround fairly quickly, and the true cause was eventually found

http://lwn.net/Articles/303390/

and it was possible to re-upload the firmware in most cases. i think only a very small number of people were effected, you won't find more than a couple of angry rants (compared to hundreds when ubuntu moved the window buttons).

the odds of this kind of thing are very small. a more likely, but still rare possibility is filesystem corruption bug. as long as you have a backup you should be fine.

[xeros]

Anyone know if Ubuntu is going to switch from 2.6.35 to 2.6.36 with Maverick (10.10) or not?

[airlied]

For instance someone posts a patch to fix some problem in the drm for r600/r700, that patch could possibly also apply to Evergreen drm code, but the Evergreen drm code for some reason is not updated. Result: Bug fixed in r600/r700, bug still present in Evergreen.

For instance someone on a forum has no clue what they are talking about?

Dave.

[wswartzendruber]

Do ATI HDMI audio chips handle multichannel LPCM yet?

[sirdilznik]

Anyone know if Ubuntu is going to switch from 2.6.35 to 2.6.36 with Maverick (10.10) or not?

Extremely doubtful. Better chance that Fedora 14 will ship with 2.6.36 but even Fedora 14 will more likely stick with 2.6.35. Still I'm sure Ubuntu will backport some stuff from 2.6.36 to their 2.6.35 kernels like they usually do.

[pvtcupcakes]

Anyone know if Ubuntu is going to switch from 2.6.35 to 2.6.36 with Maverick (10.10) or not?

No. .36 will be out in November or December, which is after 10.10 would be out.

[monraaf]

For instance someone on a forum has no clue what they are talking about?

Dave.

Whatever. It's not like this -- where a bug was present in multiple drivers but was only fixed in a few -- has never happened before.

[kernelOfTruth]

worst case was the corrupting of firmware for a specific network card, leaving the computer with no network.

http://lwn.net/Articles/300202/

there was a workaround fairly quickly, and the true cause was eventually found

http://lwn.net/Articles/303390/

and it was possible to re-upload the firmware in most cases. i think only a very small number of people were effected, you won't find more than a couple of angry rants (compared to hundreds when ubuntu moved the window buttons).

the odds of this kind of thing are very small. a more likely, but still rare possibility is filesystem corruption bug. as long as you have a backup you should be fine.

bingo !

Filesystem corruption with 2.6.36-rc1-wl+ and ecryptfs

so hands off 2.6.36-rc1 if you're using ubuntu & ecryptfs (encrypted /home folder) !

another (small) bug is a segfault with reiserfs partitions

catalyst / fglrx 10.7 also doesn't work with it yet

anyone cares to provide a patch for it - so that we can start testing 2.6.36 with >=rc2 or rc3 ?