Bug 142917

Summary:	Intel Quad Network Adapter port activation freezes system
Product:	Red Hat Enterprise Linux 3	Reporter:	Peter Liu <peterl>
Component:	kernel	Assignee:	Andy Gospodarek <agospoda>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.0	CC:	peterm, shillman
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-03 17:01:31 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:

Description Peter Liu 2004-12-14 23:41:29 UTC

Description of problem:

I have the following hardware in the server:
1U rack chassis
Supermicro P4SCT+II  (with two 1GB NIC onboard)
1GB memory
Pentium 4 3.0Ghz processor
Intel Pro/1000 MT Quad Port Server Adapter
Maxtor IDE harddrive
IDE CDROM
OS:  Red Hat Enterprise 3.0 Workstation, update 3
 
The system locks up when I try to activate 2 of the ports on the Quad 
NIC card in Linux.  


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


How reproducible: everytime port activation is applied


Steps to Reproduce:
1. Install RHEL 3.0 
2. Start Network Device Control
3. Set Static IP address and activate port
  
Actual results: On certain ports on the Intel Quad Port network 
Adapter, the activation results in locked system.  The whole system 
freezes, you cannot go to another terminal screen


Expected results: Successful activation of port and be able to ping 
out over the network to other network devices


Additional info: I've installed another type of OS (non-Linux) with 
the same hardware and all the Network ports on the motherboard and 
the Quad card works.

Comment 2 Prarit Bhargava 2007-09-12 17:55:30 UTC

Peter, is this still an issue?

P.

Comment 3 Peter Martuccelli 2007-10-03 17:01:31 UTC

We are not going to resolve this in R3, closing out as wontfix.