Bug 36817
Summary: | 3CCFE575BT cannot resume | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michal Roszkowski <michal.roszkowski> |
Component: | kernel-pcmcia-cs | Assignee: | Dave Jones <davej> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | 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:13:06 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
Michal Roszkowski
2001-04-20 12:55:18 UTC
I'm finding similar behavior with the 3Com PCI 3CCFE575CT Tornado CardBus on a Dell Inspiron 7500. The card works fine until a suspend, at both 10 and 100 mb. I have configured pcmcia to restart in apmd, but this seems to mostly fail -- pcmcia-core cannot be removed because yento-socket is using it, and for some reason the pcmcia init script won't try to rmmod yento-socket. If I manually remove the modules, I can at least restart pcmcia successfully, but restarting networking doesn't seem to work very reliably. I believe this is a kernel 2.4 problem. I noticed the same behavior in RH 7.0 after trying a 2.4 kernel (I went back to 2.2 to fix it), but maybe its just a kernel config problem? Some more info on the Dell Inspiron 7500 with 3Com PCI 3CCFE575CT Tornado CardBus: ejecting/reinserting the card does not solve the problem for me (neither physically nor with cardctl). In order to get networking back up, a reboot is neccesary. Restarting networking, or even issuing a 'pump $PUMPARGS' command manually, results in sporadic, temporary lock-ups, as if the system is in a tight cli()/sti() loop. Interrupts seem to get disabled every 10-30 seconds, then are reenabled 5-10 seconds later. This continues until pump is terminated. |