Fedora Account System
Red Hat Associate
Red Hat Customer
Networking (forcedeth) no longer comes up after resume from hibernate with kernel-2.6.29.1-30.fc10.x86_64 or kernel-2.6.29.1-36.fc10.x86_64. It used to with kernel-2.6.27.21-170.2.56.fc10.x86_64. Apr 21 23:02:14 viper kernel: ACPI: Waking up from system sleep state S4 Apr 21 23:02:14 viper kernel: pci 0000:00:05.0: PME# disabled Apr 21 23:02:14 viper kernel: nForce2_smbus 0000:00:0a.1: PME# disabled Apr 21 23:02:14 viper kernel: ohci_hcd 0000:00:0b.0: PME# disabled Apr 21 23:02:14 viper kernel: ohci_hcd 0000:00:0b.0: PCI INT A -> Link[LUB0] -> GSI 22 (level, low) -> IRQ 22 Apr 21 23:02:14 viper kernel: ohci_hcd 0000:00:0b.0: PME# disabled Apr 21 23:02:14 viper kernel: ehci_hcd 0000:00:0b.1: PME# disabled Apr 21 23:02:14 viper kernel: ehci_hcd 0000:00:0b.1: PCI INT B -> Link[LUB2] -> GSI 23 (level, low) -> IRQ 23 Apr 21 23:02:14 viper kernel: ehci_hcd 0000:00:0b.1: PME# disabled Apr 21 23:02:14 viper kernel: sata_nv 0000:00:0e.0: PCI INT A -> Link[LSA0] -> GSI 21 (level, low) -> IRQ 21 Apr 21 23:02:14 viper kernel: sata_nv 0000:00:0f.0: PCI INT A -> Link[LSA1] -> GSI 20 (level, low) -> IRQ 20 Apr 21 23:02:14 viper kernel: HDA Intel 0000:00:10.1: PCI INT B -> Link[LAZA] -> GSI 22 (level, low) -> IRQ 22 Apr 21 23:02:14 viper kernel: ata6.00: ACPI cmd ef/03:21:00:00:00:a0 filtered out Apr 21 23:02:14 viper kernel: ata5.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out Apr 21 23:02:14 viper kernel: ata5.00: ACPI cmd ef/03:01:00:00:00:a0 filtered out Apr 21 23:02:14 viper kernel: ata6.00: configured for MWDMA2 Apr 21 23:02:14 viper kernel: ata5.00: configured for UDMA/33 Apr 21 23:02:14 viper kernel: forcedeth 0000:00:14.0: wake-up capability disabled by ACPI Apr 21 23:02:14 viper kernel: forcedeth 0000:00:14.0: PME# disabled Apr 21 23:02:14 viper kernel: eth0: no link during initialization. [...] 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) Subsystem: ASUSTeK Computer Inc. A8N-VM CSM Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23 Memory at febd7000 (32-bit, non-prefetchable) [size=4K] I/O ports at d080 [size=8] Capabilities: [44] Power Management version 2 Kernel driver in use: forcedeth Kernel modules: forcedeth Smolt profile: http://smolt.fedoraproject.org/show?UUID=pub_ad06d183-2efe-4d00-8b61-66d2340e2b5b "modprobe -r forcedeth ; modprobe forcedeth" brings it back to life after resume, and SUSPEND_MODULES="forcedeth" in /etc/pm/config.d/local works too. Possibly related (I haven't tested it): https://lists.linux-foundation.org/pipermail/linux-pm/2009-March/020444.html
Fixed in 2.6.29.1-42
Confirmed, thanks.
kernel-2.6.29.2-52.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.29.2-52.fc10
kernel-2.6.29.2-52.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4132
kernel-2.6.29.3-60.fc10,hal-0.5.12-15.20081027git.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.29.3-60.fc10,hal-0.5.12-15.20081027git.fc10
kernel-2.6.29.3-60.fc10, hal-0.5.12-15.20081027git.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel hal'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4818
kernel-2.6.29.4-75.fc10,hal-0.5.12-15.20081027git.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.29.4-75.fc10,hal-0.5.12-15.20081027git.fc10
kernel-2.6.29.4-75.fc10, hal-0.5.12-15.20081027git.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel hal'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-5527
kernel-2.6.29.5-84.fc10,hal-0.5.12-15.20081027git.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.29.5-84.fc10,hal-0.5.12-15.20081027git.fc10
kernel-2.6.29.5-84.fc10, hal-0.5.12-15.20081027git.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel hal'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-6717
kernel-2.6.29.6-93.fc10,hal-0.5.12-15.20081027git.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.29.6-93.fc10,hal-0.5.12-15.20081027git.fc10
kernel-2.6.29.6-93.fc10, hal-0.5.12-15.20081027git.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel hal'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-7573
kernel-2.6.29.6-97.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.29.6-97.fc10
kernel-2.6.29.6-97.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-8697
kernel-2.6.29.6-99.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.29.6-99.fc10
kernel-2.6.29.6-99.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-8870
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.