Wifi Stops Working After Suspend

Bug #1555418 reported by Aakash Dabas
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
High
Unassigned

Bug Description

My wifi works before suspending the ubuntu but right after I login after suspension wifi doesn't works. It always displays hard blocked but the thing is that the hardware key doesn't works here. The possible solution is to restart. I've also tried following commands:
nmcli nm wifi on (NO EFFECT)
service network-manager restart (NO EFFECT)
rfkill ublock all (NO EFFECT)
I've also updated my ubuntu to latest and also updated the drivers. But non of them works.
I've also contacted my network driver providers. They are saying that this is a problem with the kernel and not with the driver.

OUPTUT OF lshw -c network

WARNING: you should run this program as super-user.
  *-network
       description: Wireless interface
       product: RTL8723BE PCIe Wireless Network Adapter
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:08:00.0
       logical name: wlo1
       version: 00
       serial: 70:77:81:30:51:21
       width: 64 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rtl8723be driverversion=4.2.0-32-generic firmware=N/A ip=192.168.1.105 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn
       resources: irq:18 ioport:5000(size=256) memory:c6100000-c6103fff
  *-network UNCLAIMED
       description: Ethernet controller
       product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:09:00.0
       version: 0a
       width: 64 bits
       clock: 33MHz
       capabilities: bus_master cap_list
       configuration: latency=0
       resources: ioport:4000(size=256) memory:c6004000-c6004fff memory:c6000000-c6003fff

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.3
ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
Uname: Linux 4.2.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CRDA:
 country IN: DFS-JP
  (2402 - 2482 @ 40), (N/A, 20), (N/A)
  (5170 - 5250 @ 80), (N/A, 20), (N/A)
  (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
  (5735 - 5835 @ 80), (N/A, 20), (N/A)
CurrentDesktop: GNOME
Date: Thu Mar 10 08:18:15 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-02-25 (13 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default via 192.168.1.1 dev wlo1 proto static metric 600
 169.254.0.0/16 dev wlo1 scope link metric 1000
 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.105 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlo1 wifi connected /org/freedesktop/NetworkManager/Devices/2 DABAS HOME ~_^ be64c657-04f4-4070-aefe-e50d74ee19bd /org/freedesktop/NetworkManager/ActiveConnection/0
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
Aakash Dabas (entangler007) wrote :
Revision history for this message
Aakash Dabas (entangler007) wrote :

One more thing after using logging in again, wifi network manager doesn't responds and rfkill event shows following output on pressing the wifi hardware key,

 idx 2 type 1 op 0 soft 0 hard 1
 idx 2 type 1 op 0 soft 1 hard 1
 idx 2 type 1 op 0 soft 0 hard 1

it changes the software lock but not the hardware lock. After restarting the ubuntu everything again starts functioning properly.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in network-manager (Ubuntu):
status: New → Confirmed
Changed in network-manager (Ubuntu):
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.