[Bug 1289884] Re: wireless doesn't associate after waking from suspend
*** This bug is a duplicate of bug 1252121 *** https://bugs.launchpad.net/bugs/1252121 Can confirm with 14.04/14.10/15.04, Thinkpad X121e, Intel WiFi 7260 N. Network is avaible after suspend but often fails to associate and to therefore to connect. This problem does _NOT_ exist with Debian/testing or Fedora 21. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289884 Title: wireless doesn't associate after waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289884] Re: wireless doesn't associate after waking from suspend
*** This bug is a duplicate of bug 1252121 *** https://bugs.launchpad.net/bugs/1252121 Can confirm using pm-suspend works ALWAYS, while Suspend from Unity menu is broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289884 Title: wireless doesn't associate after waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289884] Re: wireless doesn't associate after waking from suspend
*** This bug is a duplicate of bug 1252121 *** https://bugs.launchpad.net/bugs/1252121 I tracked down the issue where WiFi would fail after suspend in that it doesn't associate anymore (tries to connect but fails), and it's a bug in wpa-supplicant that was fixed in the current version (Ubuntu uses 2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's wpa-supplicant 2.3 and rebooting immediately fixed the issue. https://packages.debian.org/sid/wpasupplicant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289884 Title: wireless doesn't associate after waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289884] Re: wireless doesn't associate after waking from suspend
*** This bug is a duplicate of bug 1252121 *** https://bugs.launchpad.net/bugs/1252121 I am not sure this is duplicate of #1252121. In my case even after running sudo nmcli nm sleep false it unable to connect to wifi network. Having similar traceback as OP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289884 Title: wireless doesn't associate after waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289884] Re: wireless doesn't associate after waking from suspend
*** This bug is a duplicate of bug 1252121 *** https://bugs.launchpad.net/bugs/1252121 ** This bug has been marked a duplicate of bug 1252121 missing PrepareForSleep signal after resuming, causing networking to stay disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289884 Title: wireless doesn't associate after waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289884] Re: wireless doesn't associate after waking from suspend
It affects an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse). ** Changed in: bcmwl (Ubuntu) Status: New = Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: bcmwl (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289884 Title: wireless doesn't associate after waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289884] Re: wireless doesn't associate after waking from suspend
here is syslog after a resume where networking didn't resume immediately, but a network-manager restart caused resulted in a successfull connection: Mar 13 08:10:48 leafy kernel: [64782.772111] Freezing user space processes ... (elapsed 0.015 seconds) done. Mar 13 08:10:48 leafy kernel: [64782.787976] Freezing remaining freezable tasks ... (elapsed 0.120 seconds) done. Mar 13 08:10:48 leafy kernel: [64782.908611] PM: Entering mem sleep Mar 13 08:10:48 leafy kernel: [64782.908650] Suspending console(s) (use no_console_suspend to debug) Mar 13 08:10:48 leafy kernel: [64782.908816] sd 1:0:0:0: [sda] Synchronizing SCSI cache Mar 13 08:10:48 leafy kernel: [64782.909373] sd 1:0:0:0: [sda] Stopping disk Mar 13 08:10:48 leafy kernel: [64782.950546] apple-gmux 00:07: System wakeup disabled by ACPI Mar 13 08:10:48 leafy kernel: [64783.462757] PM: suspend of devices complete after 554.317 msecs Mar 13 08:10:48 leafy kernel: [64783.462955] PM: late suspend of devices complete after 0.196 msecs Mar 13 08:10:48 leafy kernel: [64783.466676] xhci_hcd :00:14.0: System wakeup enabled by ACPI Mar 13 08:10:48 leafy kernel: [64783.470726] PM: noirq suspend of devices complete after 7.771 msecs Mar 13 08:10:48 leafy kernel: [64783.480900] ACPI: Preparing to enter system sleep state S3 Mar 13 08:10:48 leafy kernel: [64823.456618] PM: Saving platform NVS memory Mar 13 08:10:48 leafy kernel: [64823.457107] Disabling non-boot CPUs ... Mar 13 08:10:48 leafy kernel: [64823.458754] kvm: disabling virtualization on CPU1 Mar 13 08:10:48 leafy kernel: [64823.560234] smpboot: CPU 1 is now offline Mar 13 08:10:48 leafy kernel: [64823.562404] kvm: disabling virtualization on CPU2 Mar 13 08:10:48 leafy kernel: [64823.664191] smpboot: CPU 2 is now offline Mar 13 08:10:48 leafy kernel: [64823.665268] Broke affinity for irq 18 Mar 13 08:10:48 leafy kernel: [64823.666324] kvm: disabling virtualization on CPU3 Mar 13 08:10:48 leafy kernel: [64823.768143] smpboot: CPU 3 is now offline Mar 13 08:10:48 leafy kernel: [64823.770272] kvm: disabling virtualization on CPU4 Mar 13 08:10:48 leafy kernel: [64823.872080] smpboot: CPU 4 is now offline Mar 13 08:10:48 leafy kernel: [64823.873028] Broke affinity for irq 45 Mar 13 08:10:48 leafy kernel: [64823.873033] Broke affinity for irq 46 Mar 13 08:10:48 leafy kernel: [64823.873038] Broke affinity for irq 47 Mar 13 08:10:48 leafy kernel: [64823.873043] Broke affinity for irq 49 Mar 13 08:10:48 leafy kernel: [64823.874069] kvm: disabling virtualization on CPU5 Mar 13 08:10:48 leafy kernel: [64823.976008] smpboot: CPU 5 is now offline Mar 13 08:10:48 leafy kernel: [64823.977954] kvm: disabling virtualization on CPU6 Mar 13 08:10:48 leafy kernel: [64824.079954] smpboot: CPU 6 is now offline Mar 13 08:10:48 leafy kernel: [64824.081984] kvm: disabling virtualization on CPU7 Mar 13 08:10:48 leafy kernel: [64824.183883] smpboot: CPU 7 is now offline Mar 13 08:10:48 leafy kernel: [64824.216900] ACPI: Low-level resume complete Mar 13 08:10:48 leafy kernel: [64824.216948] PM: Restoring platform NVS memory Mar 13 08:10:48 leafy kernel: [64824.217411] Enabling non-boot CPUs ... Mar 13 08:10:48 leafy kernel: [64824.217459] x86: Booting SMP configuration: Mar 13 08:10:48 leafy kernel: [64824.217461] smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 13 08:10:48 leafy kernel: [64824.237159] kvm: enabling virtualization on CPU1 Mar 13 08:10:48 leafy kernel: [64824.241219] CPU1 is up Mar 13 08:10:48 leafy kernel: [64824.241241] smpboot: Booting Node 0 Processor 2 APIC 0x4 Mar 13 08:10:48 leafy kernel: [64824.260528] kvm: enabling virtualization on CPU2 Mar 13 08:10:48 leafy kernel: [64824.264068] CPU2 is up Mar 13 08:10:48 leafy kernel: [64824.264089] smpboot: Booting Node 0 Processor 3 APIC 0x6 Mar 13 08:10:48 leafy kernel: [64824.282884] kvm: enabling virtualization on CPU3 Mar 13 08:10:48 leafy kernel: [64824.286231] CPU3 is up Mar 13 08:10:48 leafy kernel: [64824.286254] smpboot: Booting Node 0 Processor 4 APIC 0x1 Mar 13 08:10:48 leafy kernel: [64824.301980] kvm: enabling virtualization on CPU4 Mar 13 08:10:48 leafy kernel: [64824.304220] CPU4 is up Mar 13 08:10:48 leafy kernel: [64824.304231] smpboot: Booting Node 0 Processor 5 APIC 0x3 Mar 13 08:10:48 leafy kernel: [64824.320133] kvm: enabling virtualization on CPU5 Mar 13 08:10:48 leafy kernel: [64824.322718] CPU5 is up Mar 13 08:10:48 leafy kernel: [64824.322732] smpboot: Booting Node 0 Processor 6 APIC 0x5 Mar 13 08:10:48 leafy kernel: [64824.338588] kvm: enabling virtualization on CPU6 Mar 13 08:10:48 leafy kernel: [64824.341164] CPU6 is up Mar 13 08:10:48 leafy kernel: [64824.341178] smpboot: Booting Node 0 Processor 7 APIC 0x7 Mar 13 08:10:48 leafy kernel: [64824.357024] kvm: enabling virtualization on CPU7 Mar 13 08:10:48 leafy kernel: [64824.359597] CPU7 is up Mar 13 08:10:48 leafy kernel: [64824.437129] ACPI: Waking up from system sleep state S3 Mar 13 08:10:48 leafy kernel: [64826.487493] xhci_hcd :00:14.0: System
[Bug 1289884] Re: wireless doesn't associate after waking from suspend
adding linux as stack trace references cfg80211 module code ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289884 Title: wireless doesn't associate after waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289884] Re: wireless doesn't associate after waking from suspend
apport information ** Tags added: apport-collected ** Description changed: on a macbook pro retina, the wireless often doesn't work after waking from suspend. sometimes combinations of unloading and reloading kernel modules and restarting network-manager works; other times i need to reboot before I can reconnect to the wireless. here's syslog after a network-manager restart during one of the times i needed to reboot. Mar 8 13:38:42 leafy ModemManager[833]: info Caught signal, shutting down... Mar 8 13:38:42 leafy ModemManager[833]: info ModemManager is shut down Mar 8 13:38:42 leafy ModemManager[4223]: info ModemManager (version 1.0.0) starting... Mar 8 13:38:42 leafy NetworkManager[4230]: info NetworkManager (version 0.9.8.8) is starting... Mar 8 13:38:42 leafy NetworkManager[4230]: info Read config file /etc/NetworkManager/NetworkManager.conf Mar 8 13:38:42 leafy NetworkManager[4230]: info WEXT support is enabled Mar 8 13:38:42 leafy NetworkManager[4230]: info VPN: loaded org.freedesktop.NetworkManager.pptp Mar 8 13:38:42 leafy NetworkManager[4230]: info DNS: loaded plugin dnsmasq Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: init! Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: update_system_hostname Mar 8 13:38:42 leafy NetworkManager[4230]: interface-parser: parsing file /etc/network/interfaces Mar 8 13:38:42 leafy NetworkManager[4230]: interface-parser: finished parsing file /etc/network/interf aces Mar 8 13:38:42 leafy NetworkManager[4230]:SCPluginIfupdown: management mode: unmanaged Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:0 0/:00:1c.2/:03:00.0/net/wlan0, iface: wlan0) Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00 /:00:1c.2/:03:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/n et/lo, iface: lo) Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/ne t/lo, iface: lo): no ifupdown configuration found. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: end _init. Mar 8 13:38:42 leafy NetworkManager[4230]: info Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. Mar 8 13:38:42 leafy NetworkManager[4230]: info Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To r eport bugs please use the NetworkManager mailing list. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: Acquired D-Bus service com.canonical.NMOfono Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: init! Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: end _init. Mar 8 13:38:42 leafy NetworkManager[4230]: info Loaded plugin (null): (null) Mar 8 13:38:42 leafy NetworkManager[4230]:Ifupdown: get unmanaged devices count: 0 Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: (13606448) ... get_connections. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: (13606448) ... get_connections (managed=fal se): return empty list. Mar 8 13:38:42 leafy NetworkManager[4230]:keyfile: parsing HKGJ3 ... Mar 8 13:38:42 leafy NetworkManager[4230]:keyfile: read connection 'HKGJ3' Mar 8 13:38:42 leafy NetworkManager[4230]:keyfile: parsing Marin Secure ... Mar 8 13:38:42 leafy NetworkManager[4230]:keyfile: read connection 'Marin Secure' Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: (67124512) ... get_connections. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: (67124512) connections count: 0 Mar 8 13:38:42 leafy NetworkManager[4230]:Ifupdown: get unmanaged devices count: 0 Mar 8 13:38:42 leafy NetworkManager[4230]: info monitoring kernel firmware directory '/lib/firmware'. Mar 8 13:38:42 leafy NetworkManager[4230]: info rfkill3: found WiFi radio killswitch (at /sys/devices/pci0 000:00/:00:1c.2/:03:00.0/ieee80211/phy0/rfkill3) (driver wl) Mar 8 13:38:42 leafy NetworkManager[4230]: info rfkill4: found WiFi radio killswitch (at /sys/devices/pci0 000:00/:00:1c.2/:03:00.0/net/wlan0/rfkill4) (driver wl) Mar 8 13:38:42 leafy NetworkManager[4230]: info WiFi enabled by radio killswitch; enabled by state file Mar 8 13:38:42 leafy NetworkManager[4230]: info WWAN enabled by radio killswitch; enabled by state file Mar 8 13:38:42 leafy NetworkManager[4230]: info WiMAX enabled by radio killswitch; enabled by state file Mar 8 13:38:42 leafy NetworkManager[4230]: info Networking is enabled by state file Mar 8 13:38:42 leafy NetworkManager[4230]: info (wlan0): using nl80211 for WiFi device control
