Bug 573799 - Networking Enabled piggybacks on sleep/wake
Summary: Networking Enabled piggybacks on sleep/wake
Keywords:
Status: CLOSED DUPLICATE of bug 589108
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-15 20:11 UTC by Orion Poplawski
Modified: 2010-06-26 01:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-26 01:48:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Log "Networking status" at startup (575 bytes, patch)
2010-04-07 08:42 UTC, Jirka Klimes
no flags Details | Diff

Description Orion Poplawski 2010-03-15 20:11:05 UTC
Description of problem:

eth0 is an Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
eth1 is a Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

# cat ifcfg-eth0
# Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter
DEVICE=eth0
HWADDR=00:0C:F1:05:6D:72
ONBOOT=no
# cat ifcfg-eth1
# Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:40:D0:3D:15:8F
ONBOOT=yes
OPTIONS=layer2=1
PEERDNS=yes
PEERROUTES=yes
TYPE=Ethernet
UUID=9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04

Cable is plugged in but network is not brought up on boot.

NetworkManager Tool

State: asleep

- Device: eth0 -----------------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            ipw2100
  State:             unmanaged
  Default:           no
  HW Address:        00:0C:F1:05:6D:72

  Capabilities:

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points 


- Device: eth1 -----------------------------------------------------------------
  Type:              Wired
  Driver:            8139too
  State:             unmanaged
  Default:           no
  HW Address:        00:40:D0:3D:15:8F

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties
    Carrier:         off

ethtool reports link:

Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 32
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes

messages:
Mar 15 13:56:49 localhost NetworkManager: <info>  starting...
Mar 15 13:56:49 localhost NetworkManager: <info>  Trying to start the modem-manager...
Mar 15 13:56:49 localhost NetworkManager: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Mar 15 13:56:49 localhost NetworkManager: <info>  WiFi enabled by radio killswitch; enabled by state file
Mar 15 13:56:49 localhost NetworkManager: <info>  WWAN enabled by radio killswitch; enabled by state file
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Novatel
Mar 15 13:56:49 localhost modem-manager: Loaded plugin MotoC
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Huawei
Mar 15 13:56:49 localhost modem-manager: Loaded plugin ZTE
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Ericsson MBM
Mar 15 13:56:49 localhost modem-manager: Loaded plugin AnyData
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Nokia
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Gobi
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Sierra
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Longcheer
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Option High-Speed
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Option
Mar 15 13:56:49 localhost modem-manager: Loaded plugin Generic
Mar 15 13:56:50 localhost NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth1 ... 
Mar 15 13:56:50 localhost NetworkManager:    ifcfg-rh:     read connection 'System eth1'
Mar 15 13:56:50 localhost NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... 
Mar 15 13:56:50 localhost NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-CoRA ... 
Mar 15 13:56:50 localhost NetworkManager:    ifcfg-rh:     read connection 'CoRA'
Mar 15 13:56:50 localhost NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... 
Mar 15 13:56:50 localhost NetworkManager:    ifcfg-rh:     error: Missing SSID
Mar 15 13:56:50 localhost NetworkManager: <info>  (eth0): driver does not support SSID scans (scan_capa 0x00).
Mar 15 13:56:50 localhost NetworkManager: <info>  (eth0): new 802.11 WiFi device (driver: 'ipw2100')
Mar 15 13:56:50 localhost NetworkManager: <info>  (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Mar 15 13:56:50 localhost NetworkManager: <info>  (eth1): carrier is OFF
Mar 15 13:56:50 localhost NetworkManager: <info>  (eth1): new Ethernet device (driver: '8139too')
Mar 15 13:56:50 localhost NetworkManager: <info>  (eth1): exported as /org/freedesktop/NetworkManager/Devices/1
Mar 15 13:56:50 localhost NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
Mar 15 13:56:50 localhost NetworkManager: <info>  modem-manager is now available
Mar 15 13:56:50 localhost NetworkManager: <info>  Trying to start the supplicant...
Mar 15 13:56:50 localhost NetworkManager: <info>  (eth0): supplicant manager state:  down -> idle

I can bring the link up with "ifup eth1", then I get:

Mar 15 13:59:45 localhost NetworkManager: <info>  (eth1): carrier now ON (device state 1)
Mar 15 13:59:45 localhost kernel: eth1: link up, 100Mbps, full-duplex, lpa 0xC5E1

Version-Release number of selected component (if applicable):
NetworkManager-0.7.998-2.git20100106.fc12.i686

How reproducible:
Every time

Comment 1 Jirka Klimes 2010-04-07 08:33:20 UTC
NM is sleeping as nm-tool indicates by "State: asleep".
NetworkManager now remembers its state across restarts by storing the state to a file.
You've probably disabled NM via nm-applet's "Enable Networking" check box.

To re-enable networking, right click nm-applet and check "Enable Networking" box.

Comment 2 Jirka Klimes 2010-04-07 08:42:32 UTC
Created attachment 404866 [details]
Log "Networking status" at startup


Dan, we should probably log the networking status to make the thinks more obvious.
See the patch.

Comment 3 Orion Poplawski 2010-04-07 17:27:50 UTC
Thing is - I don't think it got disabled by the user.  Too far back though to find the logs.  The extra state logging would be helpful.  Currently you would have to detect the absence of "now managed" messages I think.

Comment 4 Dan Williams 2010-04-08 23:14:11 UTC
I think this is the case of turning off the machine while suspended...  Enable/Disable networking is currently the same thing as suspend/resume, so if you suspend/hibernate and turn the machine off without waking it back up normally, you'll end up with Networking disabled.  There's an open bug for that somewhere.

Comment 5 Dan Williams 2010-06-26 01:48:28 UTC

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


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