Bug 115169

Summary: will not shut down interface eth0
Product: Red Hat Enterprise Linux 3 Reporter: Len Jacobs <ljacobs>
Component: net-toolsAssignee: Phil Knirsch <pknirsch>
Status: CLOSED NOTABUG QA Contact: Ben Levenson <benl>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: rvokal, shillman
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-02-16 14:19:40 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
output of a dmiddecode command none

Description Len Jacobs 2004-02-07 16:28:48 UTC 
Description of problem:
On an Intel server, L440GX+ motherboard with an onboard NIC, e100,
"/etc/init.d/network stop" will not actually shutdown the network
interface and the shutdown command will thus no9t shut down gracefully.

I have tried using "acpi=nopci" as well as "acpi=off" in my grub booting.

I am attaching the output of /usr/sbin/dmidecode to help resolve this
annoying problem.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Len Jacobs 2004-02-07 16:29:55 UTC 
Created attachment 97525 [details]
output of a dmiddecode command
Comment 5 Suzanne Hillman 2004-02-16 14:19:40 UTC 
Have you yet spoken to support about this problem? If you have, what
did they say? If you have not, there should have been a phone number
to call that came with your entitlement.

If you are unable to find it, logging in to Global Support Services
https://www.redhat.com/apps/support/ may be useful. 

Conversely, you might be able to use the customer service information
on https://www.redhat.com/about/contact/directory.html to determine
who you need to call.

I will be closing this bug, since I believe it to be something you
need to talk to support about. If this is not the case, or they are
unable to help, please reopen with additional information about the
problem and anything support was able to determine.