latest upgrade of linux-restricted-modules-2.6.24-24-rt under Hardy breaks nvidia drivers (and probably others too)

Bug #356866 reported by Stéphane Magnenat
6
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Fix Released
Medium
Stefan Bader

Bug Description

After applying the latest securtiy fix on Ubuntu Hardy, which upgraded the 2.6.24-24 and 2.6.24-24-rt kernel pakcages, the nvidia drivers and emu10k1 drivers are broken under thr -rt kernel (but works under the normal kernel). My guess is that some ABI change got silently introduced which broke the -rt subsystem. Such sudden breackage of stable distributions upon security fix is bad and damages much the reputation of Ubuntu. Please fix this as soon as possible.

The errors are the followings, related to the versioning of the __wake_up symbol it seems, as shown in the attached log file.

Revision history for this message
Stéphane Magnenat (stephane.magnenat) wrote :
Revision history for this message
Stefan Bader (smb) wrote :

I am slightly confused how an update to -security (which is 2.6.24-23) affects you with 2.6.24-24 (which is from proposed). But as -proposed has to be rebuild with the security fixes anyways, can you check whether that fixes the symbols? The new version will be 2.6.24-24.53.

Revision history for this message
Stéphane Magnenat (stephane.magnenat) wrote :

I have updated the computer after several weeks of non-updates, as it is not mine. So there might have been several kernel versions upgraded. I thought that 2.6.24-24 was the lastest official version, but as I understand you it is an unofficial one, so I'll check the repository in sources.list next time.

Revision history for this message
Stéphane Magnenat (stephane.magnenat) wrote :

I will not have access to this computer for two weeks, but I'll do the upgrade and check whether the problem is fixed or not in two weeks. Thank you very much.

Revision history for this message
Stefan Bader (smb) wrote : Re: [Bug 356866] Re: latest upgrade of linux-restricted-modules-2.6.24-24-rt under Hardy breaks nvidia drivers (and probably others too)

The proposed is official as well. It just acts as a staging area. You get fixes
sooner, but you might also face new problems. I did not want to sound as you
did something bad. It was just strange that you had a more recent kernel than
the security updates and said you only did security.
To have proposed enabled is highly appreciated if you have a computer which is
not critical to be running, as it is the only way to have a broad testing on
the kernels before they go to updates.

So, knowing there has been proposed enabled explains that. The question remains
why the symbol versions do not match up. This certainly are external modules
(sound comes from linux-ubuntu-modules and nvidia from linux-restricted-modules
) but they are rebuilt when the abi changes.

So if you have access to that laptop again, could you verify that LUM and LRM
have been updated to -24 as well for the rt kernel?

--

When all other means of communication fail, try words!

Revision history for this message
Stéphane Magnenat (stephane.magnenat) wrote :

I do not have access to this computer for the next two weeks, but as far as I remember (I checked), the linux-restricted-modules and linux-ubuntu-modules where at -24 as well, but I might be wrong (90% probability to be right thought).

Revision history for this message
energymomentum (ktkawabe) wrote :

On my system, combination of linux-image-2.6.24-24-rt (version 2.6.24-24.51) and LUM 2.6.24-24-rt (2.6.24-24.38) would kill the USB sound (see the attached /var/log/messages).

On the same system, generic kernel (version2.6.24-24.51) and generic LUM (2.6.24-24.38) works.

Also, 2.6.24-23-rt (2.6.24-23.52 kernel, 2.6.24-23.37 LUM) works.

I'm using Tascam US-122 USB sound card.

Revision history for this message
Stefan Bader (smb) wrote :

Ok, it seems that the update of the rt patchset changed the abi just for rt kernels. But as those are specially build kernels it went undetected. This means LUM and LRM have just to be recompiled with the newer headers. I prepared some temporary packages and placed them at
http://people.ubuntu.com/~smb/bug356886/

Sometime in the next days LRM and LUM will get updated anyways. until then you will unfortunately have to use the temporary ones.

Revision history for this message
energymomentum (ktkawabe) wrote :

Thank you very much.
Confirmed that the sound works with the temporary LUM.

Revision history for this message
David C (da-cas) wrote :

I can confirm that I saw this problem and that the packages supplied by Stefan sorted out the problems with sound on my machine also (I just installed all the i386 LUM and LRM packages, though presumably this is resolved by the LUM).

Stefan Bader (smb)
Changed in linux-meta (Ubuntu):
assignee: nobody → stefan-bader-canonical
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Stéphane Magnenat (stephane.magnenat) wrote :

The new version do fix the probleme. For me, we can close the bug. Thank you very much.

Revision history for this message
Stefan Bader (smb) wrote :

As far as I can tell, updates to LBM, LRM and LUM now caused them all to be rebuild in -proposed, which brings them back in sync with the rt update.

Changed in linux-meta (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.