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.
Created attachment 100041 [details] /var/log/messages and lspci -vv excerpts
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.
fixed in 2.6.9 update ?
WFM in FC3 with latest kernel-2.6.9-1.698_FC3.
(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.