Description of problem: NetworkManager is continuously tearing down and setting up wired connection The Desktop is bombarded by gnome-shell notifications apps find and lose network Evo and firefox regularly decide to go offline Version-Release number of selected component (if applicable): kernel-3.3.0-0.rc1.git4.1.fc17.x86_64 NetworkManager-0.9.2-4.fc17.x86_64 systemd-39-1.fc17.x86_64
Created attachment 558024 [details] dmesg
Created attachment 558031 [details] system logs
Does setting Method to "Ignore" in IPv6 Settings tab in nm-connection-editor helps? BTW, there's a kernel problem (seen in dmesg): 66.250006] [ INFO: possible recursive locking detected ] [ 66.250006] 3.3.0-0.rc1.git4.1.fc17.x86_64 #1 Not tainted [ 66.250006] --------------------------------------------- [ 66.250006] udevd/489 is trying to acquire lock: [ 66.250006] (&hdl->lock){+.+...}, at: [<ffffffffa02dc7e7>] find_ref_lock+0x27/0x60 [videodev] [ 66.250006] ...
(In reply to comment #3) > Does setting Method to "Ignore" in IPv6 Settings tab in nm-connection-editor > helps? Thanks for the suggestion, I will try this Though networkmanager has been configured like this for ages here, so if it is the cause something regressed in the nm stack > BTW, there's a kernel problem (seen in dmesg): > 66.250006] [ INFO: possible recursive locking detected ] > [ 66.250006] 3.3.0-0.rc1.git4.1.fc17.x86_64 #1 Not tainted > [ 66.250006] --------------------------------------------- > [ 66.250006] udevd/489 is trying to acquire lock: > [ 66.250006] (&hdl->lock){+.+...}, at: [<ffffffffa02dc7e7>] > find_ref_lock+0x27/0x60 [videodev] > [ 66.250006] > ... the videodev people say this is a false alert, and can't find the time to annotate the kernel properly so it don't complain here
Maybe that's linked to bug #785772 ?
(In reply to comment #3) > Does setting Method to "Ignore" in IPv6 Settings tab in nm-connection-editor > helps? This seems to help I'll continue testing a few days, but disabling ipv6 is not nice
Please look at bug 753482. It describes a similar problem with wireless networks but it turns out the problem is packet loss and fragile Router Advertisement data. Please report if your connection problems are related to that bug.
*** This bug has been marked as a duplicate of bug 796837 ***