Bug 726574 - [forcedeth] link bounces around
Summary: [forcedeth] link bounces around
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i386
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 04:21 UTC by Greg`
Modified: 2011-07-30 00:02 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-30 00:02:46 UTC
Type: ---


Attachments (Terms of Use)
messages file (3.67 MB, text/plain)
2011-07-29 10:39 UTC, Greg`
no flags Details

Description Greg` 2011-07-29 04:21:27 UTC
Description of problem:Problem is, i switch on my PC when i get out of bed in the morning and shower then get dressed and i head up the street and go get the NewsPaper and come back and get my breakfast and jump on the internet. my internet is fine for about 30min  then NetworkManager craps out on me for up to 15minutes it just says " connecting " even if i logout of Gnome3 and log into KDE its the same problem


Version-Release number of selected component (if applicable):
NetworkManager-0.8.9997-6.git20110721.fc15.i686

How reproducible:
i can reproduce it all the time

Steps to Reproduce:
1.stay on the internet for 30min when getting online
2.NetworkManager will stop automatically and say " connecting " 
3.
  
Actual results:
 

Expected results:
it should stay connected to the internet at all times

Additional info:

Comment 1 Jirka Klimes 2011-07-29 08:47:02 UTC
Could you grab /var/log/messages file and attach it? What type of connection do you use (wired, WiFi, 3G)?

Comment 2 Greg` 2011-07-29 09:13:18 UTC
(In reply to comment #1)
> Could you grab /var/log/messages file and attach it? What type of connection do
> you use (wired, WiFi, 3G)?

i use Wired - this is not letting me Add a File

Comment 3 Greg` 2011-07-29 10:39:22 UTC
Created attachment 515869 [details]
messages file

Comment 4 Greg` 2011-07-29 10:40:50 UTC
(In reply to comment #3)
> Created attachment 515869 [details]
> messages file

i use Wired internet btw

Comment 5 Dan Williams 2011-07-29 21:03:39 UTC
It appears that the kernel driver (forcedeth) is bouncing your link: either your router is having problems, the kernel driver is having problems, or your cable is faulty.  NM will disconnect the link when the kernel tells NM that the cable is disconnected, which is what has happened:

[  660.675390] forcedeth 0000:00:10.0: eth0: link down
NetworkManager[930]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
NetworkManager[930]: <info> (eth0): carrier now ON (device state 100)
kernel: [  662.457990] forcedeth 0000:00:10.0: eth0: link up
kernel: [  666.307395] forcedeth 0000:00:10.0: eth0: link down
NetworkManager[930]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
kernel: [  668.077872] forcedeth 0000:00:10.0: eth0: link up
NetworkManager[930]: <info> (eth0): carrier now ON (device state 100)
kernel: [  671.939414] forcedeth 0000:00:10.0: eth0: link down
NetworkManager[930]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
kernel: [  673.697428] forcedeth 0000:00:10.0: eth0: link up
NetworkManager[930]: <info> (eth0): carrier now ON (device state 100)
kernel: [  686.685209] forcedeth 0000:00:10.0: eth0: link down
NetworkManager[930]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
kernel: [  688.377350] forcedeth 0000:00:10.0: eth0: link up
NetworkManager[930]: <info> (eth0): carrier now ON (device state 100)
NetworkManager[930]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
kernel: [  691.497890] forcedeth 0000:00:10.0: eth0: link down
kernel: [  693.194306] forcedeth 0000:00:10.0: eth0: link up
NetworkManager[930]: <info> (eth0): carrier now ON (device state 100)

Comment 6 Greg` 2011-07-29 23:35:13 UTC
yeah i discovered that just thismorning. i think i got another Cable, so i'll try that.

Comment 7 Greg` 2011-07-30 00:02:46 UTC
i think i fixed it, turns out it was Dodgy Cables, Cables i got with the Modem not long enough. this Bug could probably be closed


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