Description of problem: After boot of latest unstable kernel there is no network card (eth0). After manual rmmod/modprobe of r8169 module network starts again and works well. Tested multiple reboots, rerun of "dracut -f" and still same problem. Version-Release number of selected component (if applicable): kernel-3.6.5-1.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. ifconfig eth0 Actual results: [root@work ~]# ifconfig eth0 eth0: error fetching interface information: Device not found Expected results: [root@work ~]# ifconfig eth0 eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ... Additional info: [root@work ~]# ifconfig eth0 eth0: error fetching interface information: Device not found [root@work ~]# rmmod r8169 [root@work ~]# modprobe r8169 [root@work ~]# ifconfig eth0 eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ... Latest fully functional kernel for me was 3.5.2. In other 3.5 kernels there was unable to start qemu-kvm (reportoed in BZ). All 3.6 kernels are hanging after some time. Unable to describe, how to reproduce, so this was not reported yet.
Created attachment 636965 [details] dmesg output Here is my dmesg. In 284th second my modules was reloaded as described in report.
Same problem on 3.6.6 kernel. I don't use NetworkManager, may be users with NetworkManager are not affected.
Are you still seeing this with 3.7.9 or 3.8.2 in updates-testing?
I have a new motherboard with external PCIe card with same chipset without problems. I can't test it on my old motherboard. You can close this bug.
OK, thanks for the response.