[HP Pavilion dv6-1390ev] Wifi network fails to come online after resuming from suspend

[Mohd Imran Jamadar]

I am primarily connect using wifi, so after i close the lid of my laptop, and then open it back again, i find wifi connect won't come online and upon selecting enable networking nothing happens, so the only solution is to reboot.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: imran 1912 F.... pulseaudio
 /dev/snd/controlC0: imran 1912 F.... pulseaudio
CurrentDesktop: Unity
CurrentDmesg:
 [ 18.646738] init: plymouth-upstart-bridge main process ended, respawning
 [ 320.025576] perf samples too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
 [ 1183.898845] systemd-hostnamed[3266]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
Date: Sat Jul 26 00:17:53 2014
HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367
InstallationDate: Installed on 2014-07-25 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.46
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3628
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 18.51
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Mohd Imran Jamadar (imranmohd72)]

dump of sudo lshw -C network

[Mohd Imran Jamadar (imranmohd72)]

Screenshot attached, please refer to it when seeing how the network module is disabled.

[penalvch (penalvch)]

Mohd Imran Jamadar, thank you for reporting this and helping make Ubuntu better. Could you please provide the full computer model as noted on the sticker?

[Mohd Imran Jamadar (imranmohd72)]

Please note model no as noted on the sticker;

Hp Pavilion dv6-1390ev

Product Specifications?
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c01882177

If you need anymore info, then let me know.

[Seth Forshee (sforshee)]

In the logs I'm seeing this message in the logs:

iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.

This just keeps on repeating, alternating with "enable radio" messages, and it's also intermixed with "unknown key" messages. The radio is never enabled long enough to establish a wireless connection.

If I remember correctly the RF_KILL messages would result from the state of a hardware signal to the wireless card changing, and this signal would either be under firmware control or tied directly to a physical switch on the machine. If it's controlled by firmware then the state may be related to a wifi hotkey or similar on the machine, and the unknown key messages could also be generated by such a key. Does your machine have such a switch or key, and if so were you toggling or pressing this switch or key after resuming from suspend?

[Mohd Imran Jamadar (imranmohd72)]

Yes, my laptop has a wifi on/off toggle hotkey , and ever since i have installed Ubuntu, i see it blinking between blue and orange state, but it has no effect on my wifi connection , i mean that i am connected to my wifi network.

But when i click on my icon, the wifi switches off, cutting the connection to my wifi network. But sometimes when i resume from suspend wifi never comes online, sometimes it doesn't.

When i was running windows, this wifi key would always be in a blue state, not blinking between blue and orange as it's doing now.

[Seth Forshee (sforshee)]

In the logs attached to the bug I see two suspend/resume cycles. In the first it looks like you reconnect to wireless just fine. In the second it looks like you do not, and in that case I see the RF_KILL messages. Did you do anything which might cause the firmware to toggle the rfkill state after you resumed, like tapping the wireless hotkey?

Next time this happens, please run 'rfkill list' and note the states of the blocks. Then click on "Enable Networking" in the network indicator and run the command again. Finally press the wireless hotkey toggle and run the command one last time. Then paste the output from all three runs here. It would also be useful if you could run 'tail -F /var/log/syslog' in another terminal and watch it while doing all of this to see whether or not the RF_KILL messages appear in direct response to something you do.

Thanks!

[Mohd Imran Jamadar (imranmohd72)]

Please refer to the small video i have made showing the blinking wifi, switch,

http://youtu.be/8CmsFDWPgLg

this should give you the idea, in relation to my previous comment.

Initially when this issue first occurred, i did try to fiddle with the settings, like clicking on the key to check if i could bring wifi online again, and also tried toggling the enable network option.

to make wifi enabled again i would send the machine to suspend again, and bring it out of suspension state. By any chance, any setting in the bio's might need a look?

Please watch the video, and advise back, also, i will get back with the data you have asked for. Thanks.

[Seth Forshee (sforshee)]

I'm not sure what's causing the LED to blink, but if as you say it does it even when the wifi is working then it probably doesn't tell us much right now. What I'm trying to determine right now is whether wifi doesn't work because it's blocked by rfkill or if those log messages are just a symptom of things you did to try and get the wifi working again.

[Mohd Imran Jamadar (imranmohd72)]

As of now , the issue of wifi not working after asking the system to resume from suspend has not happened, waiting for the issue to occur.

But i would like to bring to your notice that when ever, i ask the system to wakeup, on the console i see some error message, to fast to catch, may be you can help me find where they are logged?

[Seth Forshee (sforshee)]

Whatever you saw ought to show up in /var/log/syslog. The only thing I see there is this:

[drm:rv730_stop_dpm] *ERROR* Could not force DPM to low

which would be associated with graphics. Does that look like the message you're seeing?

[Mohd Imran Jamadar (imranmohd72)]

Ref to your comment no#16l

True, that's the message i am seeing. Thanks.

[Mohd Imran Jamadar (imranmohd72)]

Should i file a separate bug for this issue?
[drm:rv730_stop_dpm] *ERROR* Could not force DPM to low

???

[Mohd Imran Jamadar (imranmohd72)]

Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low

[Mohd Imran Jamadar (imranmohd72)]

What about this one? related to the suspend issue?

Jul 31 00:05:21 imran-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[852]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 31 00:07:21 imran-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[852]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 31 00:07:23 imran-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[852]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Jul 31 00:09:21 imran-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[852]: wlan0: CTRL-EVENT-SCAN-STARTED

[Seth Forshee (sforshee)]

You'd need a separate bug for the DPM message. The scan messages are nothing to worry about, and there's already a bug for the nl_recvmsgs errors.

[Mohd Imran Jamadar (imranmohd72)]

I have filed a separate bug for DPM, but as of now i am unable to reproduce the wifi issue? no matter how many times i put the laptop into suspend mode? Do you want any more data?

[Seth Forshee (sforshee)]

Just keep an eye out for the problem, and if you encounter it again please collect the information requested in comment #10.

[Mohd Imran Jamadar (imranmohd72)]

Ref to comment no#10;

i am attaching the issue as it had occured, but then i use a workaround "kind off",
1) Enable Networking
2) Edit connections > select wifi > access point> select the access point > click edit > Wifi security > entered the psw and clicked on save and then clicked on toggle wifi button and it worked and connected.

[Seth Forshee (sforshee)]

It appears that your system firmware is for some reason deciding to apply a so-called "hard block" to the wireless. Based on the rfkill command output you supplied it looks like all you should need to do is push the wifi toggle button to reverse the state to get your wireless back. The next time this happens check that 'rfkill list' shows the "Hard blocked" state of hp-wifi and phy0 as "yes", then press the wifi toggle button and confirm that the states change to "no". If both the soft and hard blocked states for these devices are "no" then network manager should attempt to connect to wireless, assuming that the "Enable Networking" in the network indicator hasn't somehow become unselected. The step of updating the password in the network settings should not make any difference.

Fixing weird firmware behavior like this can be challenging. About all I can do is take a look at the ACPI tables and see if I can find anything there. If you'll run 'sudo acpidump > acpi-tables.txt' and attach acpi-tables.txt here I'll see if I can figure anything out.

[Mohd Imran Jamadar (imranmohd72)]

#acpi-tables dump log

[Seth Forshee (sforshee)]

I took a look at the acpi tables, and I can't see anything obvious the kernel does wrong which would make this happen. It is possible for us to change the state of the wireless block in the bios, but it shouldn't be getting set that way, and I don't see any way for it to be inadvertently enabled during suspend or resume. But the details are handled internal to the firmware and not in the acpi tables, so I don't know what might be happening there.

So unfortunately I think it's going to be rather difficult for me to help you get this fixed. Hopefully you can easily work around the issue by using the wireless hotkey to clear the block whenever it happens.

[Neil Hollow (nr-hollow)]

I'm having the same problem 14.04 with rtl8187, toggling switches and the workaround suggested above does not work. This has not been a problem in previous versions of linux.

[Seth Forshee (sforshee)]

Neil: You have different wireless hardware, so while your problem looks similar to this one it's likely to have a different root cause. Please open a new bug for your issue. The best way for you to do this is to wait until you start experiencing wireless problems, then as soon as possible connect to a wired network and run 'ubuntu-bug linux' from a terminal. If it's not possible to connect to a wired network, reboot immediately after you start seeing problems and reconnect to the wireless network to file the bug. Thanks!