Bug 81050 - network interface won't go up if negotiation takes too long (with patch)
Summary: network interface won't go up if negotiation takes too long (with patch)
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: initscripts   
(Show other bugs)
Version: phoebe
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 79578
TreeView+ depends on / blocked
 
Reported: 2003-01-03 20:41 UTC by Alexandre Oliva
Modified: 2014-03-17 02:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-14 01:24:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch that fixes /etc/sysconfig/network-scripts/network-functions (1.53 KB, patch)
2003-01-03 20:42 UTC, Alexandre Oliva
no flags Details | Diff

Description Alexandre Oliva 2003-01-03 20:41:45 UTC
If ip link says the interface is up but mii-tool says it's got no link before
negotiation is complete, ifup fails very quickly.  In 8.0, we used to wait 5
seconds between ip set up and running mii-tool, which was enough for my epic100
card to negotiate the link.  In Phoebe, it always fails, because there's a 1-2
second window between ip link reporting the interface is up and mii-tool getting
a `link ok'.  The patch I'm going to attach restores the 8.0 behavior, in that
it takes at most 5 seconds to bail out, but it gives more time for mii-tool to
return a success result.

Comment 1 Alexandre Oliva 2003-01-03 20:42:50 UTC
Created attachment 89107 [details]
patch that fixes /etc/sysconfig/network-scripts/network-functions

Comment 2 Bill Nottingham 2003-01-14 01:24:23 UTC
Fixed differently in 7.03-1.

Comment 3 Alexandre Oliva 2003-01-23 14:56:39 UTC
Confirmed fixed in phoebe2.


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