Bug 14302 - 3c59x apm problems
3c59x apm problems
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-07-19 21:07 EDT by Matthew Galgoci
Modified: 2007-04-18 12:27 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-10 14:47:07 EDT
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 Matthew Galgoci 2000-07-19 21:07:03 EDT
Machine is a dell Latitude LS with a built-in 3c905C-TX, rev 78

When the machine goes into suspend, the ethernet controller loses
itself. Upon waking up, the network interface is still present and 
up, but is not functioning. In order to restore the network device,
the kernel module 3c59x must be unloaded and then reloaded.

This is actually on the updated 2.2.16-3 kernel from the 6.2 updates,
but a diff of the drivers in 2.2.16-3 and 2.2.16-8 revealed no 
changes.
Comment 1 Matthew Galgoci 2000-07-19 21:29:09 EDT
I switched to the 3c90x driver, and networking can now be restored by
simply dropping the interface and bringing it back up again. No module
reload necessary, but it is still inconvenient.
Comment 2 Matthew Galgoci 2000-07-19 21:35:02 EDT
I will try the beta3 kernel next, and see if the 3c90x driver in it is 
better.
Comment 3 Michael K. Johnson 2000-08-01 16:15:14 EDT
Sometimes you just need to configure apmd to do pcmcia stop on
suspend and pcmcia start on wake.
Comment 4 David Sainty 2001-03-18 17:34:47 EST
I have EXACTLY the same problem with a Latitude LS500 here.  I suspend, and when
I come back, I must remove and reload the module before the in-built 3com will
work again.

LATEST rawhide - 2.4.2-0.1.29 kernel  (i.e. this isn't a 2.2 kernel specific thing.)

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