Bug 117484
Summary: | (ACPI 3C59X) S3 resume -- no eth0 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mihai Ibanescu <mihai.ibanescu> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | acpi-bugzilla, pfrields |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-16 05:43:14 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
Mihai Ibanescu
2004-03-04 15:11:58 UTC
sure sounds like an issue in the ethernet driver's suspend/resume... If you unload the ethernet before suspend, does resume otherwise work? thanks, -Len A lot has changed since 2.6.3-1.118 too, you might want to try the latest development kernel. This might be a separate bug, but I have a similar problem with a PCMCIA 3c575 (also uses 3c59x driver) on a an IBM TP600E with FC2, which uses APM (dmesg says ACPI is from 1999 and too old, so it's disabled). I had to put PCMCIARESTART=yes in /etc/sysconfig/apmd to make the card alive after resume, but eth0 doesn't get restarted, even though I have NET_RESTART=yes as well. It works ok if I bring it back up manually after resume. I have Lattitude C600, 3c59x driver breaks in the same manner after resuming from the sleep. Using FC3, kernel 2.6.9-1.724_FC3 Sorry for breaking into two messages, but I thought it might be usefull to note that rest of drivers seems to resume w/o any issues (audio/video/wireless card in ndiswrapper). Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |