Bug 84406 - Problems with suspend/resume and network
Problems with suspend/resume and network
Status: CLOSED DUPLICATE of bug 83996
Product: Red Hat Linux
Classification: Retired
Component: kudzu (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
:
Depends On:
Blocks: 79579
  Show dependency treegraph
 
Reported: 2003-02-15 17:36 EST by Kjartan Maraas
Modified: 2014-03-16 22:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Kjartan Maraas 2003-02-15 17:36:02 EST
Description of problem:

I have a laptop with an e100 card as eth0 and a orinoco based wlan card as eth1.
I've set them up through redhat-config-network and on boot they work just fine.
However, after suspend resume the pcmcia based WLAN adapter is started as eth0
and the system is confused since it now has the wrong MAC. This leads to modules
not wanting to be unloaded etc and I have to reboot the system to get network up
and running again.

Version-Release number of selected component (if applicable):
This is all the latest stuff from rawhide today.

How reproducible:

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


Expected results:


Additional info:
Comment 1 Bill Nottingham 2003-02-18 14:50:57 EST

*** This bug has been marked as a duplicate of 83996 ***
Comment 2 Peter Bowen 2003-02-18 20:16:29 EST
you don't have to reboot the system, just do the following:

ifdown eth0; ifdown eth1
rmmod <module list> 

where module list is probably "e100 orinoco_pci orinoco hermes" or something
similar.

Then, if you want to use wireless:
modprobe eth0; ifup eth1
otherwise, if you want to use landline:
ifup eth0; modprobe eth1
otherwise, if you don't want to use either right now:
modprobe eth0; modprobe eth1

This should allow you to avoid the reboot, but it does need to be fixed ;)
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:49 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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