Segfault during Broadcom STA wireless driver install in Kubuntu live session

Bug #1171048 reported by Scott Kitterman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bcmwl (Ubuntu)
Invalid
Undecided
Unassigned
Raring
Invalid
Undecided
Unassigned
jockey (Ubuntu)
Fix Released
High
Martin Pitt
Raring
Fix Released
High
Martin Pitt

Bug Description

As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: jockey-kde 0.9.7-0ubuntu12
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
CurrentDmesg:
 [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1
 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
 [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Date: Sat Apr 20 21:45:24 2013
InstallationDate: Installed on 2013-04-20 (0 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420)
MachineType: Dell Inc. Inspiron 1011
MarkForUpload: True
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro
SourcePackage: jockey
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/20/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: CN0Y53
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A00
dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00:
dmi.product.name: Inspiron 1011
dmi.product.version: A00
dmi.sys.vendor: Dell Inc.

Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :

Traceback is at 00:58:12.

Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1171048

tags: added: iso-testing
Revision history for this message
Scott Kitterman (kitterman) wrote :

When trying to install in the live session, I got automatically switched to a vt showing this. The same text shows up in the kern log and syslog I previously attached.

Changed in jockey (Ubuntu Raring):
importance: Undecided → High
Revision history for this message
Scott Kitterman (kitterman) wrote :

Since fixing this would only be useful on the installation media, it'd be nice to get this looked into before release.

Changed in jockey (Ubuntu Raring):
milestone: none → ubuntu-13.04
Revision history for this message
Martin Pitt (pitti) wrote :

The jockey handler essentially does this when enabling the wl driver:

  rmmod b43
  rmmod b43legacy
  rmmod bcm43xx
  rmmod ssb
  modprobe wl

Then it iterates over /sys/module/wl/drivers/*, and for each actual driver (like 1-1.5.4.2:1.0), echoes their name first into "unbind" and second into "bind", so that the kernel "reloads" the device for that driver. This causes firmware to be loaded, and wl to work without a reboot. According to the syslog, the driver oopsed on either unbinding or rebinding. Perhaps you could do the steps manually on your machine in the live session and record precisely what happens?

This unbinding/rebinding has worked fine for several cycles, so I guess either the kernel or (more likely) the bcmwl package broke something there recently. If there is a different way, or perhaps a different order of these commands that work, we can certainly change the jockey handler.

Revision history for this message
Scott Kitterman (kitterman) wrote :

I followed through the steps on the attached jockey log and everything is fine up to the unbind/rebind. What is the command for that?

Now the fun part is since I was stepping through this manually, so I could see where things were at a given time. Once I installed bcmwl-kernel-source and it's DKMS build/install had completed, I had wifi. I'm glad to continue troubleshooting the specific issue with the unbind/rebind, but for jockey, could it just be dropped for this driver?

Revision history for this message
Martin Pitt (pitti) wrote :

Ah, bcmwl-kernel-source's postinst now does the blacklisting and module unloading/reloading by itself now. That was done for moving to ubuntu-drivers-common, but the old jockey handler has never been updated. @release team: this only affects Kubuntu, jockey is not shipped on any other flavour's install images.

Changed in bcmwl (Ubuntu Raring):
status: New → Invalid
Changed in jockey (Ubuntu Raring):
status: New → In Progress
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Martin Pitt (pitti) wrote :
Changed in jockey (Ubuntu Raring):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jockey - 0.9.7-0ubuntu13

---------------
jockey (0.9.7-0ubuntu13) raring; urgency=low

  * broadcom_wl.py: Don't rebind or load the module, nor unload the b43*
    modules. Installing the package already does that in postinst, and doing
    it again in the handler causes an oops in the driver. (LP: #1171048)
 -- Martin Pitt <email address hidden> Tue, 23 Apr 2013 06:33:47 +0200

Changed in jockey (Ubuntu Raring):
status: Fix Committed → 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.