Ubuntu 16.04 - Broadcom Corporation BCM43602 - wrong icon after first resume

[Cruz Fernandez]

After resuming from suspend the WiFi icon disappears, and a cabled icon appears. The WiFi still works.

On startup it shows some strange errors on dmesg:
Bluetooth: hci0: BCM20703A1
Bluetooth: hci0: BCM (001.001.005) build 0000
IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
brcmf_add_if: ERROR: netdev:wlp2s0 already exists
brcmf_add_if: ignore IF event
IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
brcmf_add_if: ERROR: netdev:wlp2s0 already exists
brcmf_add_if: ignore IF event
IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

After succesive suspend(s)/resume(s) the icon gets back to be a WiFi icon

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-24-generic 4.4.0-24.43
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cruz 2651 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Jun 20 20:01:30 2016
HibernationDevice: RESUME=UUID=afd0c8e7-78e3-47d1-b086-10c627ac3d76
InstallationDate: Installed on 2016-06-13 (7 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 003: ID 04f3:21d5 Elan Microelectronics Corp.
 Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
 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=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=0bdc13dd-b122-4879-8d8a-31cce3301ef5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-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: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00: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)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 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.7-rc4-yakkety/

[Cruz Fernandez (cruz-fernandez)]

I only have used 4.4.0-24.43 kernel so far (new machine). I'll check with latest kernel 4.7-rc4-yakkety

[penalvch (penalvch)]

Cruz Fernandez, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Arend van Spriel, Franky Lin, and Hante Meuleman CC linux-wireless and brcm80211-dev-list.pdl)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your help.

[Cruz Fernandez (cruz-fernandez)]

I've sent to the mails you requested @penalvch . Link in linux-wireless: http://permalink.gmane.org/gmane.linux.kernel.wireless.general/153338

Also added to the description of the bug that only FIRST suspend and resume produced wrong icon.

[Cruz Fernandez (cruz-fernandez)]

After more digging, it might have been a mistake to contact the kernel drivers, as it seems there's a bug #1574347 on the network-manager component that might be producing this same error.

Maybe we should rollback to avoid having kernel maintainers loose time? I'll move this issue to network-manager component in best case.

[Cruz Fernandez (cruz-fernandez)]

I think it will be better in this component

[penalvch (penalvch)]

Cruz Fernandez, bug #1574347 has nothing to do with this issue, as the scope of that report has already been released for your version of Ubuntu (and it's not the same issue). Also, driver bugs can manifest incorrect reporting to other packages (especially after a resume).

Hence, unless this has been technically diagnosed to a particular package (not "I have an unsubstantiated hunch") then it would be best to let upstream speak to the issue raised, and let the package remain until proven otherwise.

[Cruz Fernandez (cruz-fernandez)]

You are right that the bug #1574347 is closed and already applied on my system.

I'll trust you that is good the kernel developers confirm this one but what about the spin-off bug #1589401 and also the upstream gnome-bugzilla https://bugzilla.gnome.org/show_bug.cgi?id=767317 ?

I've confirmed with this command that network-manager has loaded the correct status (but showing wrong icon):

$ nmcli d
DEVICE TYPE STATE CONNECTION
wlp2s0 wifi connected MyRouterSSID

[penalvch (penalvch)]

Cruz Fernandez, those bug reports are useless, as it's a bunch of people piling in and completely drowning out the original reporter's problem (many reporting different symptoms, WORKAROUNDs, and one said his problem was solved by updating his router's firmware), not providing any helpful debugging information, and not filing separate reports as the developers asked. This is a common problem for folks who aren't ahead of how to make it easiest for developers to work on fixing bugs.

Despite this, it wouldn't hurt to have the additional debugging information be made available for a wider review:
To increase logging level, set 'level=TRACE' in the [logging] section of /etc/NetworkManager/NetworkManager.conf and restart the service. Then attach the output of:
journalctl -u NetworkManager -b

[Cruz Fernandez (cruz-fernandez)]

Thanks for taking time to explain me Christopher M. Penalver ! I'll add the log you've requested (to reproduce the problem I don't need to reboot, just login/logout and suspend/resume produces the wrong-icon-error)

[Benny Bach (benny-bach)]

I see the same issue, also on a dell xps 15 9550. Currently running on kernel 4.7

uname -rvm
4.7.0-040700-generic #201608021801 SMP Tue Aug 2 22:03:09 UTC 2016 x86_64

dmesg shows:
[16659.882037] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
[16660.360033] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c
[16660.387699] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)

After resume I can
sudo rmmod brcmfmac; sudo modprobe brcmfmac

And wifi icon comes back

It looks more like:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575321

but I have no problem with wifi connection stability though

[Benny Bach (benny-bach)]

Is this confirmed to be a bios issue. I am running the version before 1.2.10 as people have reported issues with 1.2.10 which seems to persist on 1.2.13 according to this:

http://en.community.dell.com/techcenter/os-applications/f/4613/t/19985875?pi22229=2

Besides that I am now running the 4.7.2 kernel and the issue is the same.

[Benny Bach (benny-bach)]

Tried the new bios 1.02.13 and sure enough, it resulted in the issues reported in the previous link.

It wakes up with the screen turned off. I was able to login by turning the backlight up to full brightness (press Fn+F12 until screen turns on). After login the backlight cannot be adjusted it's either full brightness or screen off. So reverted back to 1.02.00.

[penalvch (penalvch)]

Benny Bach, to ensure we have your hardware tracked, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[penalvch (penalvch)]

Cruz Fernandez, to keep this relevant to upstream, one would want to test the latest mainline kernel (now 4.8-rc4) as it is released.

Could you please advise?

[Cruz Fernandez (cruz-fernandez)]

I've tested 4.8-rc5 and the icon is still showing after first suspend/resume. After second suspend/resume the icon is shown correctly.

On latest kernel 4.4.0-36 the situation looks similar.

[penalvch (penalvch)]

Cruz Fernandez, the latest mainline kernel has been 4.8-rc6 for a few days.

[Cruz Fernandez (cruz-fernandez)]

@penalvch , I've tested again on kernel 4.8-rc6, and from suspend button and closing lid, the system is not suspending. It only blocks the screen, and after unblocking the screen, I cannot open a new terminal, or access internet, or shutdown the system neither.

When suspending with command 'sudo pm-suspend' it can suspend and also the wifi-icon is shown correctly!

[Cruz Fernandez (cruz-fernandez)]

On latest Ubuntu 17.04 this problem is no longing standing if it helps!

[penalvch (penalvch)]

Cruz Fernandez, I am closing this report because as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594614/comments/22 the bug has been fixed in the latest development version of Ubuntu.