Bug 122621 - (ACPI) network (e100) fails after S3 suspend
(ACPI) network (e100) fails after S3 suspend
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
2
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Dave Jones
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-06 08:53 EDT by Didier
Modified: 2015-01-04 17:05 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-12-08 11:51:40 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)
/var/log/messages and lspci -vv excerpts (1.60 KB, text/plain)
2004-05-06 08:56 EDT, Didier
no flags Details

  None (edit)
Description Didier 2004-05-06 08:53:34 EDT
Description of problem:

When resuming from an ACPI S3 suspend, the 'e100' network module gets
corrupted.


Version-Release number of selected component (if applicable):

kernel-2.6.5-1.349


How reproducible:

Always


Steps to Reproduce:

1. {boot in single mode}
2. # echo -n mem > /sys/power/state
3. {resume}
4. # modprobe e100


Actual results:

PCI: Enabling device 0000:02:08.0 (0000 -> 0003)
e100: eth%d: e100_eeprom_load: EEPROM corrupted
e100: probe of 0000:02:08.0 failed with error -11


Expected results:

network functionality


Additional info:

- The above corruption message only occurs if an S3 suspend is invoked
*before* e100 is loaded.

- If an S3 suspend is invoked *after* e100 is loaded (e.g. from
initlevel 3 or initlevel 5), after resuming, the NIC detects network
cabling & communication protocol, but does not connect to the network
(eg. DHCP lease offers).

In both cases, network functionality is fatally hosed after ACPI S3
suspend/resume.
Comment 1 Didier 2004-05-06 08:56:25 EDT
Created attachment 100041 [details]
/var/log/messages  and  lspci -vv  excerpts
Comment 2 Didier 2004-05-06 09:17:32 EDT
The initlevel 3 (and 5) behaviour as described above, is similar to
bug #121906 (e1000 module) ; nevertheless, I do hope that the EEPROM
corruption messages may provide an additional clue.
Comment 3 Dave Jones 2004-12-08 01:34:02 EST
fixed in 2.6.9 update ?
Comment 4 Didier 2004-12-08 07:04:32 EST
WFM in FC3 with latest kernel-2.6.9-1.698_FC3.
Comment 5 Didier 2004-12-08 15:10:50 EST
(off-topic)
Ouch : reviewing bug activity, it seems I erroneously changed bug state from
NEEDINFO to ASSIGNED ; please accept my apologies while I wipe some egg off my face.

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