50/50 chance for BCM43602 to come up correctly during boot

[Greg Taylor]

My BCM43602 has a 50/50 chance during boot of ever becoming "ready" and pulling an IP address. The problem seems to be this "link is not ready" and "already exists" loop. The log I sent was one of the cases where things eventually worked. If I get unlucky, it simply repeats the "already exists" / "not ready" loop indefinitely.

I get a similar situation when suspending/resuming. I've already pulled the firmware and stuck it under /lib (see dmesg output for version).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: greg.taylor 2418 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun May 1 01:11:42 2016
HibernationDevice: RESUME=UUID=efd205da-4a67-4d8a-9c0e-6f3036178157
InstallationDate: Installed on 2016-04-28 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
 Bus 001 Device 003: ID 0c45:6713 Microdia
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

[Greg Taylor (gtaylor)]

I just wanted to confirm that I'm running Xenial, and the provided PPA link
is for Wily. I understand that this might be just fine, but wanted to ask
ahead of time.

On Thu, May 5, 2016 at 11:10 AM, Joseph Salisbury <
<email address hidden>> wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.6 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577113
>
> Title:
> 50/50 chance for BCM43602 to come up correctly during boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577113/+subscriptions
>

[Andy (smiffy75)]

I believe this is similar to the issue im getting with my BCM43602 on macbookpro running 16.04. It worked fine on 15.10.

Ive updated to the upstream xenial kernel but the bug still exists :

$uname -a
Linux <redacted> 4.4.9-040409-generic #201605041832 SMP Wed May 4 22:34:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$lspci | grep -i wire
03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01)

$dmesg | grep -i brcmf
[ 10.242291] usbcore: registered new interface driver brcmfmac
[ 10.381196] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
[ 10.864481] brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c
[ 10.892497] brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 10.897532] brcmfmac 0000:03:00.0 wlp3s0: renamed from wlan0
[ 10.968018] brcmf_add_if: ERROR: netdev:wlp3s0 already exists
[ 10.968051] brcmf_add_if: ignore IF event
[ 11.080205] brcmf_add_if: ERROR: netdev:wlp3s0 already exists
[ 11.080208] brcmf_add_if: ignore IF event

[Andy (smiffy75)]

For me, a manual workaround is run the following after boot. When this is done the wireless comes back to life and is visible in network manager :

sudo modprobe -r brcmfmac && sudo modprobe brcmfmac

[Rowan Wookey (rwky)]

sudo modprobe -r brcmfmac && sudo modprobe brcmfmac also works for me on my mac book pro running xenial mate edition.

Another note that if the laptop goes to sleep and wakes it may lose the network interface. It appears as 'auto ethernet' when it's not functioning properly.

[Greg Taylor (gtaylor)]

I've seen the same behavior with my Dell XPS 15 9550 that Rowan is describing with their Mac.

[Greg Taylor (gtaylor)]

Also, general note to anyone watching: Please visit this issue in LP and hit that link on the top that lets the tracker know that this issue affects you. Right now it's only me and one other, which probably doesn't help in getting this noticed.

[penalvch (penalvch)]

Greg Taylor, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[Greg Taylor (gtaylor)]

A recent update has made this work flawlessly on every boot. No idea which
update it was, but we're good now.

On Sat, Jun 4, 2016 at 2:46 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Greg Taylor, in order to allow additional upstream developers to examine
> the issue, at your earliest convenience, could you please test the latest
> upstream kernel available from
> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in
> mind the following:
> 1) The one to test is at the very top line at the top of the page (not the
> daily folder).
> 2) The release names are irrelevant.
> 3) The folder time stamps aren't indicative of when the kernel actually
> was released upstream.
> 4) Install instructions are available at
> https://wiki.ubuntu.com/Kernel/MainlineBuilds .
>
> If testing on your main install would be inconvenient, one may:
> 1) Install Ubuntu to a different partition and then test this there.
> 2) Backup, or clone the primary install.
>
> If the latest kernel did not allow you to test to the issue (ex. you
> couldn't boot into the OS) please make a comment in your report about this,
> and continue to test the next most recent kernel version until you can test
> to the issue. Once you've tested the upstream kernel, please comment on
> which kernel version specifically you tested. If this issue is fixed in the
> mainline kernel, please add the following tags by clicking on the yellow
> circle with a black pencil icon, next to the word Tags, located at the
> bottom of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-X.Y-rcZ
>
> Where X, and Y are the first two numbers of the kernel version, and Z is
> the release candidate number if it exists.
>
> If the mainline kernel does not fix the issue, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-X.Y-rcZ
>
> Please note, an error to install the kernel does not fit the criteria of
> kernel-bug-exists-upstream.
>
> Also, you don't need to apport-collect further unless specifically
> requested to do so.
>
> Once testing of the latest upstream kernel is complete, please mark this
> report Status Confirmed. Please let us know your results.
>
> Thank you for your understanding.
>
> ** Tags added: latest-bios-01.02.00
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577113
>
> Title:
> 50/50 chance for BCM43602 to come up correctly during boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577113/+subscriptions
>

[penalvch (penalvch)]

Greg Taylor, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577113/comments/11 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.