RTNL: assertion failed when modprobing 'wl'

Bug #271024 reported by Mario Limonciello
8
Affects Status Importance Assigned to Milestone
linux-restricted-modules (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using a fully updated intrepid install as of Sept 16:

lrm-common: 2.6.27-3.4
lrm-generic: 2.6.27.3.3
rlm-2.6.27-3-generic: 2.6.27-3.4

This is on a Latitude XT w/ a Dell 1397 (PCI ID 14e4:4315)

Revision history for this message
Mario Limonciello (superm1) wrote :
Revision history for this message
freiric (freiric2) wrote :

Same bug here using a fully updated intrepid install as of Sept 18:
This is on a Latitude E6400.
Linux version 2.6.27-3-generic
I have the same bug log (as part of dmesg).

Revision history for this message
Pablo Castellano (pablocastellano) wrote :

I think my case is similar.
It happens when I do modprobe -r ssb; modprobe -r wl; modprobe wl; (Note that I did it several times in the attached log).
But my dmesg output is shorter.

Also fully updated intrepid 18 sept.

Changed in linux-restricted-modules:
status: New → Confirmed
Revision history for this message
Pablo Castellano (pablocastellano) wrote :

I have blacklisted ssb from initrd and my dmesg is now similar to theirs.
Network is working anyway.

Revision history for this message
Pablo Castellano (pablocastellano) wrote :

Tim, have you checked it before marking as duplicate?
Last week I installed xubuntu and It hadn't been solved yet so I don't think it's a duplicate.

Revision history for this message
Robert Spanjaard (spamtrap-arumes) wrote :

Marking a bug as duplicate doesn't (have to) mean it's fixed. As you can see in the other bug's comments (from me, for example), the bug is still open. "Fix Committed" is not the same as "Solved".

Revision history for this message
Pablo Castellano (pablocastellano) wrote :

I'm sorry if I'm wrong.
I wanted to say that both bugs don't seem to be the same: error messages are different.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

@Pablo - it really is a duplicate. The root issue is that a fix was added in Hardy 2.6.24 to set the VLAN mode default to 0 so that normal ssh/ssl traffic worked. The fix was forward ported to Intrepid 2.6.27 where it stopped working as of 2.6.27-rc5. I updated the fix slightly, and now it works again.

Revision history for this message
Pablo Castellano (pablocastellano) wrote :

My apologizes... good work! =)

no longer affects: dell
Revision history for this message
Timothy R. Chavez (timrchavez) wrote :

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305821

no longer affects: somerville
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.