[HP Pavilion Notebook - 13-b208tu] Broadcom BCM43142 wireless fails to resume from suspend

[Stuart Bishop]

The wifi connection on the HP 13-b208tu laptop (Broadcom BCM4365) fails after computer resumes from suspend:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1435728/+attachment/4356127/+files/log

As per Bug 1434136 this laptop is running the latest version of the BIOS that boots successfully with Ubuntu (F.24).

WORKAROUND: rmmod wl && modprobe wl

WORKAROUND: Boot via upstart instead of systemd.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-9-generic 3.19.0-9.9
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: stub 1951 F.... pulseaudio
 /dev/snd/controlC0: stub 1951 F.... pulseaudio
CRDA:
 country SG: DFS-UNSET
  (2402 - 2482 @ 40), (N/A, 20), (N/A)
  (5170 - 5250 @ 40), (N/A, 20), (N/A)
  (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS
  (5735 - 5835 @ 40), (N/A, 20), (N/A)
CurrentDesktop: Unity
Date: Tue Mar 24 15:19:56 2015
HibernationDevice: RESUME=UUID=85d38fc2-ada5-4f5e-83ec-ca176c194dab
InstallationDate: Installed on 2015-03-13 (10 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0a5c:216c Broadcom Corp.
 Bus 001 Device 002: ID 064e:c33c Suyin Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion 13 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-9-generic N/A
 linux-backports-modules-3.19.0-9-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-03-16 (7 days ago)
dmi.bios.date: 11/28/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.24
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2340
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 07.09
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.24:bd11/28/2014:svnHewlett-Packard:pnHPPavilion13NotebookPC:pvr097D120000005F00000400080:rvnHewlett-Packard:rn2340:rvr07.09:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 13 Notebook PC
dmi.product.version: 097D120000005F00000400080
dmi.sys.vendor: Hewlett-Packard

[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.0 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.0-rc5-vivid/

[penalvch (penalvch)]

Stuart Bishop, unfortunately testing the latest mainline kernel won't help in this report as the proprietary module typically doesn't work with an unmodified mainline kernel, and your chipset doesn't have an open source variant AFAIK.

Despite this, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend (please ignore for now the request for the mainline kernel in the support article, just do it in the Vivid repository kernel)?

[Stuart Bishop (stub)]

cat /proc/acpi/wakeup > wakeup

[Stuart Bishop (stub)]

dmesg > dmesg.txt, after performing "resume-trace" debugging procedure for finding buggy drivers.

The wiki page and kern.log state that the system clock will need to be reset after the procedure. This did not happen. I do not know if this means the trace did not work as expected, or if someone or something ran ntp-date after the process (systemd?). I also do not see any "hash matches" entries in dmesg.txt at all.

Mar 25 11:07:27 aargh kernel: [ 234.903292] PM: Enabling pm_trace changes system date and time during resume.
Mar 25 11:07:27 aargh kernel: [ 234.903292] PM: Correct system time has to be restored manually after resume.
Mar 25 11:07:27 aargh kernel: [ 235.042115] ahci 0000:00:1f.2: port does not support device sleep
Mar 25 11:07:52 aargh kernel: [ 235.159382] PM: Syncing filesystems ... done.
Mar 25 11:07:52 aargh kernel: [ 235.162773] PM: Preparing system for mem sleep
Mar 25 11:07:52 aargh kernel: [ 235.162900] Freezing user space processes ... (elapsed 0.001 seconds) done.
Mar 25 11:07:52 aargh kernel: [ 235.164660] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Mar 25 11:07:52 aargh kernel: [ 235.165867] PM: Entering mem sleep
Mar 25 11:07:52 aargh kernel: [ 235.165882] Suspending console(s) (use no_console_suspend to debug)
Mar 25 11:07:52 aargh kernel: [ 235.166628] cfg80211: Calling CRDA to update world regulatory domain
Mar 25 11:07:52 aargh kernel: [ 235.166746] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mar 25 11:07:52 aargh kernel: [ 235.166955] sd 0:0:0:0: [sda] Stopping disk
Mar 25 11:07:52 aargh kernel: [ 235.226018] i8042 aux 00:03: System wakeup disabled by ACPI
Mar 25 11:07:52 aargh kernel: [ 235.226035] i8042 kbd 00:02: System wakeup enabled by ACPI
Mar 25 11:07:52 aargh kernel: [ 236.235376] [drm:stop_ring [i915]] *ERROR* render ring : timed out trying to stop ring
Mar 25 11:07:52 aargh kernel: [ 236.579776] PM: suspend of devices complete after 1412.325 msecs
Mar 25 11:07:52 aargh kernel: [ 236.619802] PM: late suspend of devices complete after 39.979 msecs
Mar 25 11:07:52 aargh kernel: [ 236.620364] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
Mar 25 11:07:52 aargh kernel: [ 236.620370] r8169 0000:04:00.0: System wakeup enabled by ACPI
Mar 25 11:07:52 aargh kernel: [ 236.636115] PM: noirq suspend of devices complete after 16.295 msecs
Mar 25 11:07:52 aargh kernel: [ 236.636387] ACPI: Preparing to enter system sleep state S3
Mar 25 11:07:52 aargh kernel: [ 236.703833] PM: Saving platform NVS memory
Mar 25 11:07:52 aargh kernel: [ 236.703838] Disabling non-boot CPUs ...
Mar 25 11:07:52 aargh kernel: [ 236.703868] intel_pstate CPU 1 exiting
Mar 25 11:07:52 aargh kernel: [ 236.704043] Broke affinity for irq 49
Mar 25 11:07:52 aargh kernel: [ 236.705053] kvm: disabling virtualization on CPU1
Mar 25 11:07:52 aargh kernel: [ 236.705063] smpboot: CPU 1 is now offline
Mar 25 11:07:52 aargh kernel: [ 236.705396] intel_pstate CPU 2 exiting
Mar 25 11:07:52 aargh kernel: [ 236.706548] kvm: disabling virtualization on CPU2
Mar 25 11:07:52 aargh kernel: [ 236.706556] smpboot: CPU 2 is now offline
Mar 25 11:07:52 aargh kernel: [ 236.706866] intel_pstate CPU 3 exiting...

[Stuart Bishop (stub)]

The chunk of kern.log, truncated in the above comment.

It seems at wireless is often recovering after the failure, and in the cases it doesn't 'sudo service NetworkManager restart' sorts it out. The above pm_trace procedure was performed after a fresh boot.

[penalvch (penalvch)]

Stuart Bishop, just to clarify, after resuming from suspend, does the following terminal command provide a WORKAROUND:
rmmod bcmwl && modprobe bcmwl

[Stuart Bishop (stub)]

I did a suspend/resume which triggered the failure. The terminal command failed:

root@aargh:~# rmmod bcmwl && modprobe bcmwl
rmmod: ERROR: Module bcmwl is not currently loaded

Bouncing network manager brought me back online, but bcmwl did not get reloaded.

root@aargh:~# service NetworkManager restart
root@aargh:~# rmmod bcmwl && modprobe bcmwl
rmmod: ERROR: Module bcmwl is not currently loaded

Which is unsurprising as it doesn't seem to exist:

root@aargh:~# modprobe bcmwl
modprobe: FATAL: Module bcmwl not found.

[Stuart Bishop (stub)]

Looking a little closer, the 'wl' module looked promising. 'rmmod wl && modprobe wl' does get everything back on its feet after the resume failure.

[Stuart Bishop (stub)]

Mar 25 20:33:39 aargh kernel: [ 121.980963] PM: resume of devices complete after 754.239 msecs
Mar 25 20:33:39 aargh kernel: [ 121.981208] ------------[ cut here ]------------
Mar 25 20:33:39 aargh kernel: [ 121.981216] WARNING: CPU: 2 PID: 457 at /build/buildd/linux-3.19.0/drivers/base/firmware_class.c:1126 _request_firmware+0x72e/0xbd0()
Mar 25 20:33:39 aargh kernel: [ 121.981268] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables binfmt_misc rfcomm bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic hp_wmi snd_hda_intel snd_hda_controller snd_hda_codec sparse_keymap snd_hwdep snd_pcm snd_seq_midi intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp snd_seq_midi_event kvm_intel snd_rawmidi kvm wl(POE) btusb joydev uvcvideo videobuf2_vmalloc serio_raw bluetooth snd_seq lpc_ich snd_seq_device videobuf2_memops snd_timer videobuf2_core v4l2_common videodev media cfg80211 rtsx_pci_ms memstick snd mei_me mei shpchp soundcore hp_accel lis3lv02d 8250_fintek input_polldev hp_wireless acpi_pad mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i915 cryptd psmouse i2c_algo_bit ahci drm_kms_helper libahci r8169 drm rtsx_pci mii wmi video
Mar 25 20:33:39 aargh kernel: [ 121.981298] CPU: 2 PID: 457 Comm: kworker/u17:2 Tainted: P OE 3.19.0-9-generic #9-Ubuntu
Mar 25 20:33:39 aargh kernel: [ 121.981300] Hardware name: Hewlett-Packard HP Pavilion 13 Notebook PC /2340, BIOS F.24 11/28/2014
Mar 25 20:33:39 aargh kernel: [ 121.981319] Workqueue: hci0 hci_power_on [bluetooth]
Mar 25 20:33:39 aargh kernel: [ 121.981323] ffffffff81b0fa68 ffff88008acfbb78 ffffffff817c09b5 ffffffff81c54d78
Mar 25 20:33:39 aargh kernel: [ 121.981326] 0000000000000000 ffff88008acfbbb8 ffffffff8107595a ffffffff81517f6a
Mar 25 20:33:39 aargh kernel: [ 121.981329] ffff88008acfbcd0 ffff88023252ccc0 ffff88008a86bb40 00000000fffffff5
Mar 25 20:33:39 aargh kernel: [ 121.981330] Call Trace:
Mar 25 20:33:39 aargh kernel: [ 121.981336] [<ffffffff817c09b5>] dump_stack+0x45/0x57
Mar 25 20:33:39 aargh kernel: [ 121.981340] [<ffffffff8107595a>] warn_slowpath_common+0x8a/0xc0
Mar 25 20:33:39 aargh kernel: [ 121.981345] [<ffffffff81517f6a>] ? _request_firmware+0x5a/0xbd0
Mar 25 20:33:39 aargh kernel: [ 121.981347] [<ffffffff81075a4a>] warn_slowpath_null+0x1a/0x20
Mar 25 20:33:39 aargh kernel: [ 121.981351] [<ffffffff8151863e>] _request_firmware+0x72e/0xbd0
Mar 25 20:33:39 aargh kernel: [ 121.981355] [<ffffffff81518b15>] request_firmware+0x35/0x50
Mar 25 20:33:39 aargh kernel: [ 121.981362] [<ffffffffc08ba869>] btusb_setup_bcm_patchram+0x89/0x570 [btusb]
Mar 25 20:33:39 aargh kernel: [ 121.981365] [<ffffffff8150f7e6>] ? rpm_idle+0xd6/0x230
Mar 25 20:33:39 aargh kernel: [ 121.981382] [<ffffffffc082c561>] hci_dev_do_open+0xe1/0xa90 [bluetooth]
Mar 25 20:33:39 aargh kernel: [ 121.981386] [<ffffffff810135e0>...

[penalvch (penalvch)]

Cut from Bug Description.

[penalvch (penalvch)]

Stuart Bishop, for regression testing purposes, could you please test broadcom-sta (not bcmwl) in Trusty via http://releases.ubuntu.com/trusty/ (live environment is fine) and advise to the results?

[Stuart Bishop (stub)]

I am not able to get the card recognized at all using a Trusty CD, either with the default setup or after selecting the broadcom drivers from System Settings/Software and Uodates/Additional Drivers.

[penalvch (penalvch)]

Stuart Bishop, how about Utopic via http://releases.ubuntu.com/utopic/ ?

[Stuart Bishop (stub)]

It seems that this is a regression from Utopic.

I just booted a Utopic USB stick, switched on the proprietary driver, and connected to my wifi network. I then performed 10 suspend/resumes in sequence (using suspend from the system menu), and they all worked flawlessly. The kern.log file was silent.

[penalvch (penalvch)]

Stuart Bishop, does hibernate provide a WORKAROUND?

[Stuart Bishop (stub)]

Hibernate fails to resume (running 'sudo pm-hibernate', as it seems disabled by default), and requires a power cycle to recover.

[penalvch (penalvch)]

Stuart Bishop, the bug you are reporting is an upstream one. Could you please report this to them following https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#Broadcom_STA_Wireless_driver ?

[penalvch (penalvch)]

Stuart Bishop, one other thing I was curious about, could you please provide the results of the following terminal command:
iwconfig wlan0

[Stuart Bishop (stub)]

wlan0 IEEE 802.11abg ESSID:"MYSSID"
          Mode:Managed Frequency:2.447 GHz Access Point: 01:23:45:67:89:ab
          Retry short limit:7 RTS thr:off Fragment thr:off
          Power Management:on

[penalvch (penalvch)]

Stuart Bishop, anything change if you turn off power management via:
sudo iwconfig wlan0 power off

[Stuart Bishop (stub)]

I am having trouble reproducing this at all with the latest round of updates. I still get the traceback (the bluetooth one), but wifi is reliably reconnecting.

[Stuart Bishop (stub)]

As of the most recent update (3.19.0-12), is has returned to consistently failing.

Turning off power management via 'sudo iwconfig wlan0 power off' has no effect.

[Stuart Bishop (stub)]

The trigger was not the kernel version. The trigger is upstart or systemd. The laptop reliably reconnects to wifi after resume if I have booted using the 'upstart' option in the grub advanced boot menu. If I have booted using the default grub selection, the laptop reliably fails to reconnect to wifi after resume.

I have been working in 'upstart' mode most of the time recently, for unrelated compatibility issues, which is why I had been unable to reproduce this for the last week.

I will attach kern.log logs, showing a fresh boot in upstart mode followed by three successful suspend/resumes. And kern.log logs, showing a fresh boot in systemd mode followed by three failed suspend/resumes (and rmmod, modprobe in between).

[Louis (darkenlx)]

i can confirm this is an exact same problem with HP Pavilion TouchSmart 14 Sleekbook model 14-b109wm as well but has wifi card Atheros AR5B125

[penalvch (penalvch)]

Louis (darkenlx), it will help immensely if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.