Bug 62288

Summary: Network devices handling on resume on a laptop
Product: [Retired] Red Hat Public Beta Reporter: keithu <keithu>
Component: apmdAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: skipjack-beta1CC: rvokal
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: 2003-02-21 01:11:36 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:
Bug Depends On:    
Bug Blocks: 61901, 67218, 79579    

Description keithu@parl.clemson.edu 2002-03-29 04:45:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-31smp i686)

Description of problem:
There seem to be two problems with the handling of network interfaces on resume
from suspsend. 1) Even if NO interfaces are up at suspend time and NO interfaces
are supposed to come up at boot time, all interfaces attempt to come up after a
resume.  2) They do not seem to all try to come up at the same time.  In fact,
in a laptop with 3 network interfaces (long story), one PCMCIA interface
attempts to come up first.  After it fails, the built-in interface and the
PCMCIA wireless card attempt to come up.

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


How reproducible:
Always

Steps to Reproduce:
1.Procure laptop
2.install network interface
3.install RH 7.2.92
4.configure network interface to NOT activate on boot, but to activate by DHCP
5.ifdown eth0
6.suspend laptop
7.resume laptop
	

Actual Results:  eth0 attempted to DHCP for an address

Expected Results:  The laptop should have resumed without bringing up the
network interface.  

Additional info:

This is REALLY annoying.  Not nearly so bad as 7.2 (where the card was left in a
bad state), but still REALLY annoying.  Especially if you have a standard 100Tx
interface and a wireless interface.

Comment 1 Bill Nottingham 2002-03-31 17:03:43 UTC
This is handled by apmd.

Comment 2 Bill Nottingham 2003-02-21 01:11:36 UTC
This should be better now.

Comment 3 Bill Nottingham 2003-02-21 01:12:09 UTC
*** Bug 63655 has been marked as a duplicate of this bug. ***