Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 455578

Summary: Network is broken after upgrade from RHEL4U6
Product: Red Hat Enterprise Linux 4 Reporter: Nicole Dai <ndai>
Component: kernelAssignee: Neil Horman <nhorman>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: low    
Version: 4.7CC: desktop-bugs, herbert.xu, jolsa, nhorman, notting, tgraf
Target Milestone: rc   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-13 15:05:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log information when manually run ifup or server network restart
none
lspci output none

Description Nicole Dai 2008-07-16 11:45:17 UTC 
Description of problem:
After upgrade from RHEL4U6 to RHEL4U7-20080711.0, network cannot be up with the
following outputs:
[root@localhost ~]# ifup eth0

Determining IP information for eth0...SIOCSIFFLAGS: Device or resource busy
SIOCSIFFLAGS: Device or resource busy

Version-Release number of selected component (if applicable):
initscripts-7.93.33-1.el4

How reproducible:
Always

Steps to Reproduce:
1. Fresh install RHEL4U6 (default or everything)
2. Upgrade the RHEL4U6 to RHEL4U7-20080711.0
3. Log on system and ifconfig 
  
Actual results:
No IP address was assigned to the default NIC. ifup or server network restart
outputted the error:
Determining IP information for eth0...SIOCSIFFLAGS: Device or resource busy
SIOCSIFFLAGS: Device or resource busy

Expected results:


Additional info:
Got the following information from /var/log/messages which showed the NIC was up
during the startup:
Jul 16 17:48:29 dhcp-65-148 ifup:
Jul 16 17:48:29 dhcp-65-148 ifup: Determining IP information for eth0...
Jul 16 17:48:29 dhcp-65-148 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 8
Jul 16 17:48:29 dhcp-65-148 dhclient: DHCPOFFER from 10.66.65.254 <30>Jul 16
17:48:29 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 16 17:48:29 dhcp-65-148 dhclient: DHCPACK from 10.66.65.254
Jul 16 17:48:29 dhcp-65-148 NET: /sbin/dhclient-script : updated /etc/resolv.conf
Jul 16 17:48:29 dhcp-65-148 dhclient: bound to 10.66.65.148 -- renewal in 12112
seconds.
Jul 16 17:48:29 dhcp-65-148 ifup:  done.
Jul 16 17:48:29 dhcp-65-148 network: Bringing up interface eth0:  succeeded
Comment 1 Nicole Dai 2008-07-16 11:45:18 UTC 
Created attachment 311942 [details]
log information when manually run ifup or server network restart
Comment 2 Bill Nottingham 2008-07-16 17:29:11 UTC 
Can you attach the output of lspci? This sounds like a driver issue.
Comment 3 Nicole Dai 2008-07-17 02:28:16 UTC 
Created attachment 312007 [details]
lspci output
Comment 4 Neil Horman 2009-12-21 13:39:19 UTC 
It sounds to me like perhaps something actually started working correctly,  in that, after the upgrade, perhaps NetworkManager is automating the bringup of the interface in question, making the ifup which you issue redundant?
Comment 5 Neil Horman 2010-06-23 18:37:12 UTC 
ping any update here?