Bug 635055 - NetworkManager does not work after suspend
Summary: NetworkManager does not work after suspend
Keywords:
Status: CLOSED DUPLICATE of bug 638640
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 13
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-17 17:25 UTC by Matthias Scheutz
Modified: 2010-10-18 17:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-18 17:22:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthias Scheutz 2010-09-17 17:25:54 UTC
Description of problem:

Both the wired and the wireless network are not accessible after suspend.  Specifically, none of the checkboxes in nm-applet can be changed, and the following error message is printed:

** (nm-applet:12901): WARNING **: handle_property_changed: property 'ip-interface' changed but wasn't defined by object type NMDeviceBt.

Version-Release number of selected component (if applicable):

NetworkManager-0.8.1-6.git20100831.fc13.i686

How reproducible:

Suspend computer and when it comes back the network does not work anymore.
The only way to get the network working again via NetworkManager is to kill it and restart it.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Neither wireless or wired connections work.

Expected results:

Wired and wireless connections should be re-established.

Additional info:

Comment 1 Dan Williams 2010-09-23 20:11:12 UTC
When this happens, can you attach /var/log/messages after it resumes and the problem is exhibited?

Comment 2 Matthias Scheutz 2010-09-25 15:46:47 UTC
I looked at the dmesg output a few times but never saw anything related to NetworkManager

Also let me know what it does not happen every time, but when it happens and I kill NetworkManager and start it again, everything works fine

Comment 3 Matthias Scheutz 2010-09-30 13:56:14 UTC
I just saw this on the terminal after resuming (and again the network did not work, I had to kill NetworkManager...)

** (nm-applet:6485): WARNING **: handle_property_changed: property 'ip-interface' changed but wasn't defined by object type NMDeviceBt.

Comment 4 Jirka Klimes 2010-10-04 08:14:49 UTC
(In reply to comment #0)
> Suspend computer and when it comes back the network does not work anymore.
> The only way to get the network working again via NetworkManager is to kill it
> and restart it.

Do you mean restarting NetworkManager daemon or just nm-applet.

(In reply to comment #2)
> I looked at the dmesg output a few times but never saw anything related to
> NetworkManager

Well, we need /var/log/messages file that contains NetworkManager logs to see what's going on.

Comment 5 Matthias Scheutz 2010-10-08 16:01:23 UTC
Here is the relevant output:

Oct  8 11:07:45 mslap kernel: Freezing user space processes ... (elapsed 0.01 seconds) done.
Oct  8 11:07:45 mslap kernel: Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Oct  8 11:07:45 mslap kernel: Suspending console(s) (use no_console_suspend to debug)
Oct  8 11:07:45 mslap kernel: btusb_intr_complete: hci0 urb efabbe80 failed to resubmit (1)
Oct  8 11:07:45 mslap kernel: btusb_bulk_complete: hci0 urb efabbb00 failed to resubmit (1)
Oct  8 11:07:45 mslap kernel: btusb_bulk_complete: hci0 urb efabbc00 failed to resubmit (1)
Oct  8 11:07:45 mslap kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
Oct  8 11:07:45 mslap kernel: sd 2:0:0:0: [sda] Stopping disk
Oct  8 11:07:45 mslap kernel: serial 00:09: disabled
Oct  8 11:07:45 mslap kernel: ata_piix 0000:00:1f.2: PCI INT C disabled
Oct  8 11:07:45 mslap kernel: ata_piix 0000:00:1f.1: PCI INT A disabled
Oct  8 11:07:45 mslap kernel: ehci_hcd 0000:00:1d.7: PCI INT A disabled
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1d.2: PCI INT C disabled
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1d.1: PCI INT B disabled
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1d.0: PCI INT A disabled
Oct  8 11:07:45 mslap kernel: HDA Intel 0000:00:1b.0: PCI INT A disabled
Oct  8 11:07:45 mslap kernel: ehci_hcd 0000:00:1a.7: PCI INT C disabled
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1a.1: PCI INT B disabled
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1a.0: PCI INT A disabled
Oct  8 11:07:45 mslap kernel: PM: suspend of devices complete after 1205.728 msecs
Oct  8 11:07:45 mslap kernel: PM: late suspend of devices complete after 21.711 msecs
Oct  8 11:07:45 mslap kernel: ACPI: Preparing to enter system sleep state S3
Oct  8 11:07:45 mslap kernel: Disabling non-boot CPUs ...
Oct  8 11:07:45 mslap kernel: CPU 1 is now offline
Oct  8 11:07:45 mslap kernel: SMP alternatives: switching to UP code
Oct  8 11:07:45 mslap kernel: Extended CMOS year: 2000
Oct  8 11:07:45 mslap kernel: Extended CMOS year: 2000
Oct  8 11:07:45 mslap kernel: Enabling non-boot CPUs ...
Oct  8 11:07:45 mslap kernel: SMP alternatives: switching to SMP code
Oct  8 11:07:45 mslap kernel: Booting Node 0 Processor 1 APIC 0x1
Oct  8 11:07:45 mslap kernel: Initializing CPU#1
Oct  8 11:07:45 mslap kernel: CPU1 is up
Oct  8 11:07:45 mslap kernel: ACPI: Waking up from system sleep state S3
Oct  8 11:07:45 mslap kernel: yenta_cardbus 0000:03:01.0: O2: enabling read prefetch/write burst
Oct  8 11:07:45 mslap kernel: PM: early resume of devices complete after 1.977 msecs
Oct  8 11:07:45 mslap kernel: dell-wmi: Unknown key e043 pressed
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Oct  8 11:07:45 mslap kernel: usb usb3: root hub lost power or was reset
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
Oct  8 11:07:45 mslap kernel: usb usb4: root hub lost power or was reset
Oct  8 11:07:45 mslap kernel: ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 22 (level, low) -> IRQ 22
Oct  8 11:07:45 mslap kernel: HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Oct  8 11:07:45 mslap kernel: usb usb5: root hub lost power or was reset
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
Oct  8 11:07:45 mslap kernel: usb usb6: root hub lost power or was reset
Oct  8 11:07:45 mslap kernel: uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
Oct  8 11:07:45 mslap kernel: usb usb7: root hub lost power or was reset
Oct  8 11:07:45 mslap kernel: ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Oct  8 11:07:45 mslap kernel: ata_piix 0000:00:1f.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct  8 11:07:45 mslap kernel: ata_piix 0000:00:1f.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Oct  8 11:07:45 mslap kernel: ata3.00: _GTF evaluation failed (AE 0x1001)
Oct  8 11:07:45 mslap kernel: firewire_core: skipped bus generations, destroying all nodes
Oct  8 11:07:45 mslap kernel: serial 00:09: activated
Oct  8 11:07:45 mslap kernel: firewire_core: rediscovered device fw0
Oct  8 11:07:45 mslap kernel: ata4.01: failed to resume link (SControl 0)
Oct  8 11:07:45 mslap kernel: ata4.00: SATA link down (SStatus 4 SControl 300)
Oct  8 11:07:45 mslap kernel: ata4.01: SATA link down (SStatus 0 SControl 0)
Oct  8 11:07:45 mslap kernel: sd 2:0:0:0: [sda] Starting disk
Oct  8 11:07:45 mslap kernel: dell-wmi: Unknown key e044 pressed
Oct  8 11:07:45 mslap kernel: ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct  8 11:07:45 mslap kernel: ata3.01: SATA link down (SStatus 4 SControl 300)
Oct  8 11:07:45 mslap kernel: ata3.00: configured for UDMA/133
Oct  8 11:07:45 mslap kernel: usb 7-1: reset full speed USB device using uhci_hcd and address 2
Oct  8 11:07:45 mslap kernel: usb 7-1.2: reset full speed USB device using uhci_hcd and address 3
Oct  8 11:07:45 mslap kernel: usb 3-2: reset full speed USB device using uhci_hcd and address 4
Oct  8 11:07:45 mslap kernel: btusb 3-2:1.0: no reset_resume for driver btusb?
Oct  8 11:07:45 mslap kernel: btusb 3-2:1.1: no reset_resume for driver btusb?
Oct  8 11:07:45 mslap kernel: PM: resume of devices complete after 5697.274 msecs
Oct  8 11:07:45 mslap bluetoothd[4689]: HCI dev 0 down
Oct  8 11:07:45 mslap bluetoothd[4689]: Adapter /org/bluez/4687/hci0 has been disabled
Oct  8 11:07:45 mslap bluetoothd[4689]: Stopping security manager 0
Oct  8 11:07:45 mslap bluetoothd[4689]: HCI dev 0 unregistered
Oct  8 11:07:45 mslap bluetoothd[4689]: Unregister path: /org/bluez/4687/hci0
Oct  8 11:07:45 mslap bluetoothd[4689]: HCI dev 0 registered
Oct  8 11:07:45 mslap NetworkManager[9758]: <info> BT device 00:1D:FE:05:FA:37 removed
Oct  8 11:07:45 mslap NetworkManager[9758]: <info> BT device D0:37:61:78:E9:1B removed
Oct  8 11:07:45 mslap kernel: Restarting tasks ... done.
Oct  8 11:07:45 mslap kernel: video LNXVIDEO:01: Restoring backlight state
Oct  8 11:07:45 mslap bluetoothd[4689]: HCI dev 0 up
Oct  8 11:07:45 mslap bluetoothd[4689]: Starting security manager 0
Oct  8 11:07:45 mslap bluetoothd[4689]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Oct  8 11:07:45 mslap bluetoothd[4689]: probe failed with driver input-headset for device /org/bluez/4687/hci0/dev_00_1D_FE_05_FA_37
Oct  8 11:07:45 mslap bluetoothd[4689]: Invalid record
Oct  8 11:07:45 mslap bluetoothd[4689]: probe failed with driver input-headset for device /org/bluez/4687/hci0/dev_D0_37_61_78_E9_1B
Oct  8 11:07:45 mslap bluetoothd[4689]: Adapter /org/bluez/4687/hci0 has been enabled
Oct  8 11:07:45 mslap NetworkManager[9758]: <warn> (D0:37:61:78:E9:1B): failed to look up interface index
Oct  8 11:07:45 mslap NetworkManager[9758]: <info> BT device DROID2 (D0:37:61:78:E9:1B) added (DUN NAP)
Oct  8 11:07:45 mslap NetworkManager[9758]: <info> (D0:37:61:78:E9:1B): new Bluetooth device (driver: 'bluez' ifindex: -1)
Oct  8 11:07:45 mslap NetworkManager[9758]: <info> (D0:37:61:78:E9:1B): exported as /org/freedesktop/NetworkManager/Devices/3

Comment 6 Dan Williams 2010-10-15 15:13:45 UTC
When this happens, can you run:

nmcli nm

and paste the output in?

Comment 7 Matthias Scheutz 2010-10-16 12:53:46 UTC
RUNNING     STATE       WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running     asleep      enabled         enabled    enabled         enabled 

and when i tried to click the box "Enable Networking" which was not checked, i would not check it, i had to kill NetworkManager, restarted it and everything worked fine

The above is one example of what happens, sometimes STATE is running and it still doesn't work

Comment 8 Dan Williams 2010-10-18 17:22:00 UTC
Ok, based on that information this is a dupe of 638640 which I've pushed fixes for now.  Please see that bug for more information on fixed packages.

*** This bug has been marked as a duplicate of bug 638640 ***


Note You need to log in before you can comment on or make changes to this bug.