Bug 794834 - p37p1 interface disconnects again
Summary: p37p1 interface disconnects again
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-17 18:29 UTC by Michael Schwendt
Modified: 2012-03-30 06:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 10:16:19 UTC
Type: ---


Attachments (Terms of Use)

Description Michael Schwendt 2012-02-17 18:29:28 UTC
Updated to the most recent NM from koji (pending -> updates-testing):

$ rpm -qa Net\*|sort
NetworkManager-0.9.3-0.2.git20120215.fc17.x86_64
NetworkManager-debuginfo-0.9.3-0.2.git20120215.fc17.x86_64
NetworkManager-glib-0.9.3-0.2.git20120215.fc17.x86_64
NetworkManager-gnome-0.9.3-0.2.git20120215.fc17.x86_64
NetworkManager-gtk-0.9.3-0.2.git20120215.fc17.x86_64
NetworkManager-openconnect-0.9.2.0-1.fc17.x86_64
NetworkManager-openvpn-0.9.0-2.fc17.x86_64
NetworkManager-pptp-0.9.0-2.fc17.x86_64
NetworkManager-vpnc-0.9.0-2.fc17.x86_64

Just as in F-17 Alpha TC2, NM fails to keep my DHCP based Ethernet connection. It disconnects after a minute. No such problems with F-16 and older.

Feb 17 19:14:15 localhost NetworkManager[5344]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-p37p1 ...
Feb 17 19:14:15 localhost NetworkManager[5344]:    ifcfg-rh:     read connection 'System p37p1'
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): carrier is ON
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): new Ethernet device (driver: 'r8169' ifindex: 2)
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): exported as /org/freedesktop/NetworkManager/Devices/0
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): now managed
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): preparing device.
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Activation (p37p1) starting connection 'System p37p1'
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): device state change: unavailable -> ip-config (reason 'none') [20 70 0]
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Activation (p37p1) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Activation (p37p1) Stage 3 of 5 (IP Configure Start) started...
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Activation (p37p1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Activation (p37p1) Stage 3 of 5 (IP Configure Start) complete.
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): DHCPv4 state changed nbi -> preinit
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): DHCPv4 state changed preinit -> reboot
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Activation (p37p1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Activation (p37p1) Stage 5 of 5 (IPv4 Commit) started...
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> (p37p1): device state change: ip-config -> activated (reason 'none') [70 100 0]
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Policy set 'System p37p1' (p37p1) as default for IPv4 routing and DNS.
Feb 17 19:14:15 localhost NetworkManager[5344]: <info> Activation (p37p1) successful, device activated.
Feb 17 19:14:16 localhost NetworkManager[5344]: <info> Activation (p37p1) Stage 5 of 5 (IPv4 Commit) complete.
Feb 17 19:15:14 localhost NetworkManager[529]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-p37p1 ...
Feb 17 19:15:14 localhost NetworkManager[529]:    ifcfg-rh:     read connection 'System p37p1'
Feb 17 19:15:14 localhost NetworkManager[529]: <info> (p37p1): carrier is OFF
Feb 17 19:15:14 localhost NetworkManager[529]: <info> (p37p1): new Ethernet device (driver: 'r8169' ifindex: 3)
Feb 17 19:15:14 localhost NetworkManager[529]: <info> (p37p1): exported as /org/freedesktop/NetworkManager/Devices/0
Feb 17 19:15:14 localhost NetworkManager[529]: <info> (p37p1): now managed
Feb 17 19:15:14 localhost NetworkManager[529]: <info> (p37p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 17 19:15:14 localhost NetworkManager[529]: <info> (p37p1): bringing up device.
Feb 17 19:15:14 localhost NetworkManager[529]: <info> (p37p1): preparing device.
Feb 17 19:15:15 localhost NetworkManager[529]: <info> (p37p1): deactivating device (reason 'managed') [2]
Feb 17 19:15:16 localhost NetworkManager[529]: <info> (p37p1): carrier now ON (device state 20)
Feb 17 19:15:16 localhost NetworkManager[529]: <info> (p37p1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]


A manual "ifup p37p1" succeeds:

Feb 17 19:21:17 localhost NetworkManager[529]: <info> (p37p1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 1 of 5 (Device Prepare) scheduled...
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 1 of 5 (Device Prepare) started...
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 2 of 5 (Device Configure) scheduled...
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 1 of 5 (Device Prepare) complete.
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 2 of 5 (Device Configure) starting...
Feb 17 19:21:17 localhost NetworkManager[529]: <info> (p37p1): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 2 of 5 (Device Configure) successful.
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 2 of 5 (Device Configure) complete.
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 3 of 5 (IP Configure Start) started...
Feb 17 19:21:17 localhost NetworkManager[529]: <info> (p37p1): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 17 19:21:17 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 3 of 5 (IP Configure Start) complete.
Feb 17 19:21:18 localhost NetworkManager[529]: <info> (p37p1): DHCPv4 state changed nbi -> preinit
Feb 17 19:21:18 localhost NetworkManager[529]: <info> (p37p1): DHCPv4 state changed preinit -> reboot
Feb 17 19:21:18 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Feb 17 19:21:18 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 5 of 5 (IPv4 Commit) started...
Feb 17 19:21:19 localhost NetworkManager[529]: <info> (p37p1): device state change: ip-config -> activated (reason 'none') [70 100 0]
Feb 17 19:21:19 localhost NetworkManager[529]: <info> Policy set 'System p37p1' (p37p1) as default for IPv4 routing and DNS.
Feb 17 19:21:19 localhost NetworkManager[529]: <info> Activation (p37p1) successful, device activated.
Feb 17 19:21:19 localhost NetworkManager[529]: <info> Activation (p37p1) Stage 5 of 5 (IPv4 Commit) complete.

Comment 1 Michael Schwendt 2012-03-20 10:15:54 UTC
After some weeks, I've revisited Network Settings to try enabling the connection again, and the problem is gone.

# rpm -q NetworkManager kernel
NetworkManager-0.9.3.995-0.6.git20120314.fc17.x86_64
kernel-3.3.0-0.rc6.git0.2.fc17.x86_64
# uname -r
3.3.0-0.rc6.git0.2.fc17.x86_64

Comment 2 Joachim Backes 2012-03-30 06:10:48 UTC
Having similar issues with my Ethernet controller em1: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) after updating to 

NetworkManager.x86_64 1:0.9.4.0-1.git20120328.fc17
NetworkManager-glib.x86_64 1:0.9.4.0-1.git20120328.fc17
NetworkManager-gnome.x86_64 1:0.9.4.0-1.git20120328.fc17
NetworkManager-gtk.x86_64 1:0.9.4.0-1.git20120328.fc17

See thread http://lists.fedoraproject.org/pipermail/test/2012-March/106426.html


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