Bug 445405 - Sporadic failure to connect to cable modem on boot
Sporadic failure to connect to cable modem on boot
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
i386 Linux
low Severity high
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-05-06 14:47 EDT by charles harris
Modified: 2009-07-14 13:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 13:52:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages edited to remove non-network stuff. (12.26 KB, text/plain)
2008-05-06 14:47 EDT, charles harris
no flags Details

  None (edit)
Description charles harris 2008-05-06 14:47:36 EDT
Description of problem:

About 50% of the time the system boots and the network is up. The other 50% it
is down, and can't be established using ifup. This may be a timeout problem,
I've attached edited boot messages from both successful and failed boots that
indicate that NetworkManager incorrectly times out the dhclient.

Sorry if this has already been reported, but that wasn't clear to me.

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

f9 preview.

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 charles harris 2008-05-06 14:47:36 EDT
Created attachment 304676 [details]
/var/log/messages edited to remove non-network stuff.
Comment 2 Dan Williams 2008-05-08 14:35:54 EDT
Which version of NetworkManager are you running?  Can you upgrade to latest F9
packages?  You should have at least "svn3623".
Comment 3 charles harris 2008-05-08 15:50:29 EDT
I'll have to wait till after work. Is svn3623 part of the package name, or do I
find it somewhere else? I just do the normal updates when new packages show up.
Comment 4 charles harris 2008-05-09 01:00:20 EDT
I'm running svn3623 and there is still a problem.
Comment 5 Bug Zapper 2008-05-14 06:44:04 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 6 Jessica Sterling 2009-03-06 12:46:41 EST
This bug has been triaged

Fedora Bugzappers volunteer triage team
Comment 7 Bug Zapper 2009-06-09 20:39:02 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 8 Bug Zapper 2009-07-14 13:52:29 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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