Bug 60205
Summary: | pcmcia confused about network interfaces on Dell Latitude C610 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthew Saltzman <mjs> |
Component: | kernel-pcmcia-cs | Assignee: | Dave Jones <davej> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | pfrields |
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: | 2004-11-25 07:20:05 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
Matthew Saltzman
2002-02-21 23:25:24 UTC
Update: With 7.3, the problem does not occur in most cases, however there is still one problem scenario left. On resuming after suspend to RAM, eth1 does not come up. In order to get it to come up, I need to perform the steps listed above (and recapped below): (1) service pcmcia stop (2) ifup eth0 (with no cable attached) (3) service pcmcia start (4) ifup eth1 All other scenarios tested so far seem to work in 7.3. question: does it help if you add resume=force to the end of the line with "vmlinuz" in the /etc/grub/grub.conf file ? I tried the following: Set resume=force, set eth0 down and eth1 up. Suspend and resume. The effect is that eth0 attempts to start (which it should not do, since it was down at suspend). When eth0 times out, eth1 starts. So yes, resume=force seems to help, but the behavior is still not perfect. It seems like I would want things that were down to stay down and things that were up to attempt to come up on resume. Perhaps this is repated to bug 47529? This is still the behavior in RHL 8.0. |