Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk

Bug #1247712 reported by Po-Hsu Lin on 2013-11-04
58
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Jockey
Undecided
Unassigned
bcmwl (Baltix)
Medium
Unassigned
bcmwl (Ubuntu)
Critical
Alberto Milone
Nominated for Saucy by Po-Hsu Lin
Precise
Critical
Unassigned
Trusty
Critical
Unassigned
jockey (Ubuntu)
Critical
Alberto Milone
Nominated for Saucy by Po-Hsu Lin
Precise
Critical
Alberto Milone
Trusty
Critical
Unassigned
linux-lts-trusty (Ubuntu)
Critical
Unassigned
Nominated for Saucy by Po-Hsu Lin
Precise
Critical
Unassigned
Trusty
Critical
Unassigned

Bug Description

SRU request:

Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed.

[Impact]

Kernel versions higher than 3.8 fail to rebind the Broadcom device to the driver thus compromising system stability. While rebinding is a nice feature it can't come at the cost of system stability. For this reason we'll disable this feature when dealing with Linux >= 3.8 and preserve it in the other cases.

[Test Case]

Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux-lts-trusty), then use Jockey to install the broadcom wireless driver. Jockey will hang and the system will probably hang on shutdown.

[Regression Potential]

It should be minimal i.e. there won't be device rebinding on the livecd. This, however, shouldn't be an issue since the open broadcom driver should already work out of the box.

Furthermore the test suite now covers this test case.

== Description ==

CID: 201303-13027 Dell Inspiron 5535
CID: 201012-6925 Dell Latitude E6320
CID: 201208-11536 Dell Latitude 6430u

Affected chipsets:
Broadcom 4365
Broadcom 4313 [14e4:4727] (rev 01)
Broadcom 43132

The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29)

Steps:
1. Install Ubuntu 12.04.3 (or 12.04.4) + update
2. Boot to desktop
3. Install the Broadcom STA wireless driver via jockey-gtk

Driver cannot be installed, jockey-gtk will stuck at "Downloading and installing driver"
The last message from jockey.jog is:
unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device 0000:02:00.0

Error message could be found in dmesg:
Nov 3 21:34:14 201012-6925 kernel: [ 528.104653] wlc_lcnphy_rx_gain_tbl_free_entry = 5
Nov 3 21:34:14 201012-6925 kernel: [ 528.104863] BUG: unable to handle kernel paging request at ffffffffa045d020
Nov 3 21:34:14 201012-6925 kernel: [ 528.104906] IP: [<ffffffffa045d020>] 0xffffffffa045d01f
Nov 3 21:34:14 201012-6925 kernel: [ 528.104936] PGD 1c0f067 PUD 1c13063 PMD 2ea40067 PTE 0
Nov 3 21:34:14 201012-6925 kernel: [ 528.104967] Oops: 0010 [#1] SMP
Nov 3 21:34:14 201012-6925 kernel: [ 528.104988] Modules linked in: lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma]
Nov 3 21:34:14 201012-6925 kernel: [ 528.105424] CPU 0
Nov 3 21:34:14 201012-6925 kernel: [ 528.105438] Pid: 2695, comm: jockey-backend Tainted: PF O 3.8.0-33-generic #48~precise1-Ubuntu Dell Inc. Latitude E6320/
Nov 3 21:34:14 201012-6925 kernel: [ 528.105493] RIP: 0010:[<ffffffffa045d020>] [<ffffffffa045d020>] 0xffffffffa045d01f
Nov 3 21:34:14 201012-6925 kernel: [ 528.105533] RSP: 0018:ffff88001b405d50 EFLAGS: 00010282
Nov 3 21:34:14 201012-6925 kernel: [ 528.105558] RAX: 0000000000000001 RBX: ffff880031788000 RCX: 0000000000000000
Nov 3 21:34:14 201012-6925 kernel: [ 528.105590] RDX: 0000000000000000 RSI: ffffffffa0861ec0 RDI: ffff880031788000
Nov 3 21:34:14 201012-6925 kernel: [ 528.105623] RBP: ffff88001b405d78 R08: 0000000000000000 R09: 0000000000000000
Nov 3 21:34:14 201012-6925 kernel: [ 528.105657] R10: 0000000000003684 R11: 0000000000000293 R12: ffff88001b405da0
Nov 3 21:34:14 201012-6925 kernel: [ 528.105690] R13: ffffffffa08643e0 R14: ffff880031788098 R15: ffff8800317880f8
Nov 3 21:34:14 201012-6925 kernel: [ 528.105724] FS: 00007fc348968700(0000) GS:ffff880100200000(0000) knlGS:0000000000000000
Nov 3 21:34:14 201012-6925 kernel: [ 528.105760] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 3 21:34:14 201012-6925 kernel: [ 528.105787] CR2: ffffffffa045d020 CR3: 0000000003fe2000 CR4: 00000000000407f0
Nov 3 21:34:14 201012-6925 kernel: [ 528.105820] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 3 21:34:14 201012-6925 kernel: [ 528.105853] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 3 21:34:14 201012-6925 kernel: [ 528.105886] Process jockey-backend (pid: 2695, threadinfo ffff88001b404000, task ffff880031fb0000)
Nov 3 21:34:14 201012-6925 kernel: [ 528.105928] Stack:
Nov 3 21:34:14 201012-6925 wpa_supplicant[1130]: Failed to initiate AP scan.
Nov 3 21:34:14 201012-6925 kernel: [ 528.105939] ffffffff8138750b 00000000ffffffff ffffffffa08643e0 ffffffffa0864448
Nov 3 21:34:14 201012-6925 kernel: [ 528.105980] ffff880031788098 ffff88001b405dc8 ffffffff81388de9 00007fc352864000
Nov 3 21:34:14 201012-6925 kernel: [ 528.106021] ffff880031788098 ffff88001b405da8 ffffffffa08643e0 ffff880031788000
Nov 3 21:34:14 201012-6925 kernel: [ 528.106061] Call Trace:
Nov 3 21:34:14 201012-6925 kernel: [ 528.106079] [<ffffffff8138750b>] ? local_pci_probe+0x4b/0x80
Nov 3 21:34:14 201012-6925 kernel: [ 528.106109] [<ffffffff81388de9>] __pci_device_probe+0xd9/0xe0
Nov 3 21:34:14 201012-6925 kernel: [ 528.106138] [<ffffffff81388e2a>] pci_device_probe+0x3a/0x60
Nov 3 21:34:14 201012-6925 kernel: [ 528.106166] [<ffffffff81466491>] really_probe+0x61/0x210
Nov 3 21:34:14 201012-6925 kernel: [ 528.106193] [<ffffffff8146678e>] driver_probe_device+0x3e/0x60
Nov 3 21:34:14 201012-6925 kernel: [ 528.106224] [<ffffffff8146511a>] driver_bind+0xca/0x110
Nov 3 21:34:14 201012-6925 kernel: [ 528.106252] [<ffffffff814644e4>] drv_attr_store+0x24/0x40
Nov 3 21:34:14 201012-6925 kernel: [ 528.106280] [<ffffffff812101af>] sysfs_write_file+0xef/0x170
Nov 3 21:34:14 201012-6925 kernel: [ 528.106310] [<ffffffff8119b9d3>] vfs_write+0xb3/0x180
Nov 3 21:34:14 201012-6925 kernel: [ 528.106336] [<ffffffff8119bd12>] sys_write+0x52/0xa0
Nov 3 21:34:14 201012-6925 kernel: [ 528.106363] [<ffffffff816f880e>] ? do_page_fault+0xe/0x10
Nov 3 21:34:14 201012-6925 kernel: [ 528.106391] [<ffffffff816fd15d>] system_call_fastpath+0x1a/0x1f
Nov 3 21:34:14 201012-6925 kernel: [ 528.106419] Code: Bad RIP value.
Nov 3 21:34:14 201012-6925 kernel: [ 528.106442] RIP [<ffffffffa045d020>] 0xffffffffa045d01f
Nov 3 21:34:14 201012-6925 kernel: [ 528.106472] RSP <ffff88001b405d50>
Nov 3 21:34:14 201012-6925 kernel: [ 528.107684] CR2: ffffffffa045d020
Nov 3 21:34:14 201012-6925 kernel: [ 528.117115] ---[ end trace 3abc2d81fa437419 ]---

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1
ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
Uname: Linux 3.8.0-33-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1709 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0x3f660000 irq 44'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:111d76e7,10280492,00100102 HDA:80862805,80860101,00100000'
   Controls : 43
   Simple ctrls : 13
Date: Sun Nov 3 21:46:46 2013
HibernationDevice: RESUME=UUID=91b2743a-c198-4376-b46d-3b533b1281c8
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
MachineType: Dell Inc. Latitude E6320
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=666300ee-69fe-4d8a-a5cb-29164f727ae3 ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-33-generic N/A
 linux-backports-modules-3.8.0-33-generic N/A
 linux-firmware 1.79.7
RfKill:

SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X54
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrX54:bd02/04/2011:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6320
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-32-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1650 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0x3f660000 irq 44'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:111d76e7,10280492,00100102 HDA:80862805,80860101,00100000'
   Controls : 43
   Simple ctrls : 13
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=91b2743a-c198-4376-b46d-3b533b1281c8
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
MachineType: Dell Inc. Latitude E6320
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux-lts-raring (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=UUID=01e1685a-9490-405d-9eb6-804378fd2fa2 ro quiet splash initcall_debug vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-32-generic N/A
 linux-backports-modules-3.8.0-32-generic N/A
 linux-firmware 1.79.7
RfKill:

Tags: precise running-unity qa-kernel-lts-testing
Uname: Linux 3.8.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/04/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X54
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrX54:bd02/04/2011:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6320
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Po-Hsu Lin (cypressyew) wrote :
Po-Hsu Lin (cypressyew) wrote :

I found this bug also affects 3.8.0-32 kernel, therefore the "regression-proposed" tag will be removed

For results from 3.8.0-32 kernel (201012-6925 Dell Latitude E6320)
Please refer to the following attachments

tags: removed: regression-proposed
tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

  • syslog Edit (826.7 KiB, application/octet-stream)

Syslog for 3.8.0-32 kernel

description: updated
Po-Hsu Lin (cypressyew) on 2013-11-04
summary: - Unable to install Broadcom STA wireless dirver on 3.8.0-33 proposed
- kernel
+ Unable to install Broadcom STA wireless dirver on 3.8.0-33 proposed /
+ 3.8.0-32 kernel

CID: 201206-11396 could reproduce this bug

reproduce steps:
  1. install 12.04.3 on this machine
  2. update 12.04.3 to be up-to-date
  3. use jockey to install the driver (jockey-gtk and select the driver)
  4. then there will be kernel panic

other information:
a clean 12.04.3 could not reproduce this bug on this machine

tags: added: 201206-11396
Taihsiang Ho (taihsiangho) wrote :

CID: 201206-11396 system information for comment 21

Po-Hsu Lin (cypressyew) wrote :

For 201012-6925 Dell Latitude E6320,
the driver cannot be installed on 12.04.3 stock Ubuntu (3.8.0-29) as well
The same kernel dump will be displayed on the screen.

However, Boradcom 4313 [14e4:4727], 43224[14e4:0576], 43228[14e4:4359] works fine on 3.8 kernel without the proprietary driver.

description: updated

CID: 201303-13027 Dell Inspiron 5535

This system comes with Broadcom 4365, the proprietary driver,
bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.3 (3.8.0-29) as well.

tags: added: 201303-13027
Changed in linux-lts-raring (Ubuntu):
assignee: nobody → Anthony Wong (anthonywong)
summary: Unable to install Broadcom STA wireless dirver on 3.8.0-33 proposed /
- 3.8.0-32 kernel
+ 3.8.0-32 / 3.8.0-29 kernel
description: updated

More information:
this bcmwl package could be installed by using apt-get install via terminal.
Therefore this bug might be related to jockey itself, there are some clues in the log as well.

summary: Unable to install Broadcom STA wireless dirver on 3.8.0-33 proposed /
- 3.8.0-32 / 3.8.0-29 kernel
+ 3.8.0-32 / 3.8.0-29 kernel via jockey-gtk
Changed in jockey (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
Changed in linux-lts-raring (Ubuntu):
assignee: Anthony Wong (anthonywong) → nobody
Po-Hsu Lin (cypressyew) on 2013-11-12
summary: - Unable to install Broadcom STA wireless dirver on 3.8.0-33 proposed /
- 3.8.0-32 / 3.8.0-29 kernel via jockey-gtk
+ Unable to install Broadcom STA wireless dirver on 3.8.0-33 / 3.8.0-29
+ kernel via jockey-gtk
tags: added: blocks-hwcert

Description modified to clarify the problem

description: updated
Alberto Milone (albertomilone) wrote :

Please reproduce the error and attach your /var/log/jockey.log

Alberto Milone (albertomilone) wrote :

the attached kernel log shows that the broadcom driver doesn't play well with the local_pci_probe() function in the kernel. The jockey.log that I requested might explain what jockey did to trigger local_pci_probe() and therefore also the error, which seems to me like a bug in broadcom's proprietary driver.

Po-Hsu Lin (cypressyew) wrote :

Error reproduced on 201304-13207 with 12.04.3 + update (3.8.0-33)
/var/log/jockey.log attached

Alberto Milone (albertomilone) wrote :

Jockey's log confirms that the program simply triggers the problem when unbinding and then rebinding the driver (hence the driver_bind() call in the backtrace), which in turn calls driver_probe_device(), etc. up to local_pci_probe() which is what fails.

To sum it up, it's not a bug in Jockey. The broadcom driver is the problem here.

Changed in bcmwl (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
Changed in jockey (Ubuntu):
status: New → Invalid
Changed in jockey (Ubuntu Precise):
status: New → Invalid
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bcmwl (Ubuntu Precise):
status: New → Confirmed
Changed in bcmwl (Ubuntu):
status: New → Confirmed
Changed in linux-lts-raring (Ubuntu Precise):
status: New → Confirmed
Changed in linux-lts-raring (Ubuntu):
status: New → Confirmed
Daniel Manrique (roadmr) on 2014-01-17
Changed in linux-lts-raring (Ubuntu):
importance: Undecided → High
Po-Hsu Lin (cypressyew) wrote :

Still affecting 12.04.4 (3.11.0-15)
201206-11158 Broadcom 43228 [14e4:4359]

tags: added: 201206-11158
Changed in jockey:
status: New → Invalid
Po-Hsu Lin (cypressyew) wrote :

It stuck at unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device 0000:02:00.0

summary: - Unable to install Broadcom STA wireless dirver on 3.8.0-33 / 3.8.0-29
- kernel via jockey-gtk
+ Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel via
+ jockey-gtk
Po-Hsu Lin (cypressyew) on 2014-04-08
description: updated
description: updated

@Po-Hsu: can you try the attached package please? (please reboot after installing the package, just in case)

Po-Hsu Lin (cypressyew) wrote :

Hello Alberto,

I tried with the package by:
1. Install 12.04.4
2. Install this package, reboot
3. Try to install the Broadcom driver

It still stuck at the unbind/rebind

Also this package has been released, is this the right package to test with?

Alberto Milone (albertomilone) wrote :

Ok, please try again with the packages I made available here:
http://people.canonical.com/~amilone/lp1247712/

You might want to install only jockey-common and jockey-gtk, and then reboot.

I made change so that Jockey won't try to unbind/rebind the driver.

Po-Hsu Lin (cypressyew) wrote :

Hello Alberto,
This one works!

Steps:
1. Install 12.04.4 + jockey-gtk + jockey-common you provided here
2. Reboot
3. Install the Broadcom driver from jockey-gtk

Result:
* Driver successfully installed, those error messages in jockey.log and dmesg are gone

Thanks!

Po-Hsu Lin (cypressyew) wrote :
Alberto Milone (albertomilone) wrote :

Ok, now that we have confirmed that that's the issue, please follow these steps:

1) Uninstall the broadcom driver

2) dowgrade jockey to 0.9.7-0ubuntu7.15

3) Reboot

4) Make sure jockey-backend is not running ("ps aux | grep jockey-backend"). If it is, make sure to kill it.

5) Type the following command:
sudo strace -fvvs1024 -o /tmp/jockey.trace /usr/share/jockey/jockey-backend --debug

6) Launch jockey as usual and try to install the driver so as to reproduce the problem

7) Attach the /tmp/jockey.trace file

Po-Hsu Lin (cypressyew) wrote :

Hello Alberto,

the jockey-gtk + jockey-common you provided here are 0.9.7-0ubuntu7.15
Should I downgrade them to 0.9.7-0ubuntu7.14 (Precise Update)
or just skip to step 3?

Alberto Milone (albertomilone) wrote :

my mistake, yes, please downgrade to 0.9.7-0ubuntu7.14

Po-Hsu Lin (cypressyew) wrote :

OK, I've reverted jockey-gtk and jockey-common to 0.9.7-0ubuntu7.14

I fetch the log after this message (issue reproduced)
2014-04-09 23:28:28,642 DEBUG: unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device 0000:02:00.0
PANIC: handle_group_exit: 2698 leader 2151

Alberto Milone (albertomilone) wrote :

Ok, I've uploaded a new build of jockey, can you try it please?

http://people.canonical.com/~amilone/lp1247712/

This time I only need the log (no need to strace). If it fails, then we can probably work around it.

Po-Hsu Lin (cypressyew) wrote :

Sure,
test steps:
1. Install 12.04.4 + jockey-gtk + jockey-common you provided here
2. Reboot
3. Install the Broadcom driver from jockey-gtk

It still stuck at unbind / rebind stage.

Alberto Milone (albertomilone) wrote :

Let's try a different approach to the problem.

Please test the new packages available here:
http://people.canonical.com/~amilone/lp1247712/

As last time, I only need the log.

Po-Hsu Lin (cypressyew) wrote :

With these new packages, jockey won't be stuck at the unbind/rebind stage.
However, the "Bad RIP value" error message still could be found in syslog
And when you try to power off the system, it will be stuck at the Ubuntu splash screen as usual.
The only way to power it off is to hold the power button.
Wireless works after boot

Steps:
1. Install 12.04.4 + jockey-gtk + jockey-common you provided here
2. Reboot
3. Install the Broadcom driver from jockey-gtk

Po-Hsu Lin (cypressyew) wrote :
Alberto Milone (albertomilone) wrote :

Can you reproduce the problem with Ubuntu 12.04? Or does it only happen with 12.04.3 and 12.04.4?

Po-Hsu Lin (cypressyew) wrote :

On:
12.04.1 + update (3.2.0-60)
12.04.2 + update (3.5.0-48)
This issue cannnot be reproduced

I'll verify this on 12.04.3 tomorrow.

Po-Hsu Lin (cypressyew) wrote :

Yes, this issue could be reproduced on 12.04.3, with the same symptom

Also note that everything works fine on 12.04.4 (3.11.0-19) if I install the driver with command:
sudo apt-get install bcmwl-kernel-source

Log files for 12.04.3 attached here.

Alberto Milone (albertomilone) wrote :

Ok, I think a good compromise would be to disable rebinding on Linux >= 3.8

Please test my new packages here:
http://people.canonical.com/~amilone/lp1247712/

Po-Hsu Lin (cypressyew) wrote :

This one works fine on 12.04.4 (3.11.0-15)
Thanks

description: updated
Changed in jockey (Ubuntu Precise):
status: Invalid → In Progress
assignee: nobody → Alberto Milone (albertomilone)

Hello Po-Hsu, or anyone else affected,

Accepted jockey into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/jockey/0.9.7-0ubuntu7.15 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in jockey (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed

Verified on:
201206-11158 with Broadcom 43228 [14e4:4359]
201302-12682 with Broadcom 43228 [14e4:4359]
201108-8942 with Broadcom 43227 [14e4:4358]
201012-6925 with Broadcom 4313 [14e4:4727]

Steps:
1. Install 12.04.4, enable proposed, run update and reboot.
2. Install the Broadcom driver via jockey

VERIFICATION DONE
Driver installation complete successfully

But for
201307-13942 with Broadcom 4352 [14e4:43b1]
201307-13942 with Broadcom 4352 [14e4:43b1]

From jockey.log, it will stuck on:
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.11.0-20-generic

And error messages could be found in dmesg
[ 344.878100] RIP: 0010:[<ffffffffa05a1020>] [<ffffffffa05a1020>] wdev_priv.part.7+0x4/0x6 [wl]
...(see attachment)

There is a bug for this component [14e4:43b1], #1279690, since the error message is different from what I posted in the bug description, maybe this is another issue?

Po-Hsu Lin (cypressyew) wrote :

Note, for comment 58, another system I have test with is:
201303-13030 with Broadcom 4352 [14e4:43b1]

Alberto Milone (albertomilone) wrote :

Something goes wrong when modprobing the module (which jockey does when installing the driver).

The log shows that while the module segfaults, the installation is complete. Does Jockey report that the driver was installed? Or does it just hang?

Po-Hsu Lin (cypressyew) wrote :

It just hang there, the log stopped as attached in comment 59
and the "downloading and installing" small dialog still running

tags: added: bios-outdated-a19
Changed in bcmwl (Baltix):
status: New → Confirmed
importance: Undecided → Medium
Taihsiang Ho (taihsiangho) wrote :

Dell Latitude E5530 (CID 201202-10546) could reproduce this bug on 12.04.5
the attachment bcm-install-dmesg-jockey.tar.gz is the dmesg.log and jockey.log

tags: added: 201202-10546
Taihsiang Ho (taihsiangho) wrote :

Dell Latitude E5530 (CID 201202-10546) in the comment #62
has
Broadcom BCM43228 802.11a/b/g/n [14e4:4359]

It needs the proprietary driver to enable the wireless.

Daniel Manrique (roadmr) on 2014-10-16
Changed in linux-lts-trusty (Ubuntu):
importance: Undecided → Critical
Po-Hsu Lin (cypressyew) on 2014-10-16
summary: - Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel via
- jockey-gtk
+ Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 /
+ 3.13 kernel via jockey-gtk
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-lts-trusty (Ubuntu Precise):
status: New → Confirmed
Changed in linux-lts-trusty (Ubuntu):
status: New → Confirmed
no longer affects: linux-lts-raring (Ubuntu)
no longer affects: linux-lts-raring (Ubuntu Precise)
tags: added: verification-failed
removed: verification-needed
Changed in jockey (Ubuntu Precise):
status: Fix Committed → In Progress
Changed in linux-lts-trusty (Ubuntu Trusty):
importance: Undecided → Critical
status: New → Confirmed
Changed in linux-lts-trusty (Ubuntu Precise):
importance: Undecided → Critical
Changed in jockey (Ubuntu Trusty):
importance: Undecided → Critical
status: New → Confirmed
Changed in jockey (Ubuntu Precise):
importance: Undecided → Critical
Changed in jockey (Ubuntu):
importance: Undecided → Critical
Changed in bcmwl (Ubuntu Trusty):
importance: Undecided → Critical
status: New → Confirmed
Changed in bcmwl (Ubuntu Precise):
importance: Undecided → Critical
Changed in jockey (Ubuntu):
status: Invalid → In Progress
Changed in bcmwl (Ubuntu):
importance: Undecided → Critical
tags: added: trusty
tags: added: kernel-net
Changed in bcmwl (Ubuntu Trusty):
status: Confirmed → In Progress
Changed in bcmwl (Ubuntu Precise):
status: Confirmed → In Progress
Changed in bcmwl (Ubuntu):
status: Confirmed → In Progress
Changed in jockey (Ubuntu Trusty):
status: Confirmed → In Progress
Changed in linux-lts-trusty (Ubuntu):
status: Confirmed → In Progress
Changed in linux-lts-trusty (Ubuntu Precise):
status: Confirmed → In Progress
Changed in linux-lts-trusty (Ubuntu Trusty):
status: Confirmed → In Progress
Alberto Milone (albertomilone) wrote :

Does the driver work after a reboot?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers