+++ This bug was initially created as a clone of Bug #438046 +++ Description of problem: After reboot, the my r8169 does not start properly. Must use rmmod and modprobe to get it working. Version-Release number of selected component (if applicable): Only kernel 2.6.24 has the problem. All previous kernels are OK. How reproducible: Always Steps to Reproduce: 1. Reboot or power on the computer 2. [root@linus ~]# lsmod | grep r8169 r8169 28229 0 [root@linus ~]# /etc/init.d/network restart Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0...PING 192.168.0.1 (192.168.0.1) from 192.168.0.193 eth0: 56(84) bytes of data. --- 192.168.0.1 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms , pipe 3 failed. [FAILED] [root@linus ~]# rmmod r8169 [root@linus ~]# lsmod | grep r8169 [root@linus ~]# modprobe r8169 [root@linus ~]# /etc/init.d/network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0... done. [ OK ] [root@linus ~]# uname -a Linux linus.localdomain 2.6.24.3-34.fc8 #1 SMP Wed Mar 12 18:17:20 EDT 2008 i686 athlon i386 GNU/Linux [root@linus ~]# Actual results: Network card works as expected after rmmod and modprobe. Expected results: Network card should have been working after reboot. Additional info: -- Additional comment from sveinrn on 2008-03-18 16:59 EST -- I just noticed that mii-tool does not recognize the card after the reboot: [root@linus ~]# lsmod | grep 8169 r8169 28229 0 [root@linus ~]# mii-tool no MII interfaces found [root@linus ~]# [root@linus ~]# rmmod r8169 [root@linus ~]# modprobe r8169 [root@linus ~]# [root@linus ~]# mii-tool eth0: negotiated 100baseTx-FD flow-control, link ok [root@linus ~]# -- Additional comment from harald on 2008-03-31 06:09 EST -- *** Bug 437619 has been marked as a duplicate of this bug. *** -- Additional comment from loganjerry on 2008-04-03 16:08 EST -- Same problem here. I've had this machine since FC-5, and have had no problems on any kernel prior to 2.6.24. While the machine is trying to initialize eth0 during bootup, it waits for some timeout, then prints a message about a failed ping. However, the FROM address of the ping is the one I instructed my DHCP server to give to my machine, and the TO address is my router/gateway/DHCP server. Therefore, DHCP succeeded on the initial boot, and eth0 became unusable afterwards. I'm willing to experiment if anyone has any ideas. -- Additional comment from sveinrn on 2008-04-07 07:50 EST -- As I can see that several other people have the same problem, I changed the severity to "medium". Even though it is easy for me to work around this one, it could be a real showstopper for somebody trying out Linux for their first time. -- Additional comment from josep.puigdemont on 2008-04-26 16:05 EST -- Similar problem for Fedora 9 (preview release), which meant Fedora 9 could not be installed from network, and that network wouldn't work after installation from DVD/CDs. I doesn't only happen after reboot, it happens always here. I noticed that at start up, and just after 1 minute uptime, the r8169 driver had registered 17 million interrupts, according to /proc/interrupts: $ grep eth /proc/interrupts 16: 17132211 IO-APIC-fasteoi eth0 $ uptime 21:02:30 up 1 min, 2 users, load average: 0.97, 0.44, 0.16 The problem is solved after rmmod, and then modprobe the module again. This is an extract of dmesg when doing rmmod and modprobe: ACPI: PCI interrupt for device 0000:00:0b.0 disabled r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 16 (level, low) -> IRQ 16 eth0: RTL8110s at 0xf8904f00, 00:11:09:ce:a6:ca, XID 04000000 IRQ 16 Is the interrupt different? What does the extra [A] mean after modprobing the module? I think the severity should be higher (for some people it might block installation of F9), but on the other hand it might not affect too many people.
This is the same hardware as in this Fedora 8 installation: http://www.smolts.org/client/show/pub_c348ef55-d532-4197-afac-be8e3690c35e
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I updated my Fedora installation a while ago to version 9, and the problem was still there. But today I just noticed that I could remove the rmmod/modprobe and the NIC was still working. So I guess that at least part of the problem has been fixed in one of the later kernel updates, but I can't tell the exact version. And of course I don't now if it has been fixed for everyone.
Happens on F10 with 2.6.27.12-170.2.5.fc10.i686 updated as 9th February 2009. Doing the rmmod r8169; modprobe r8169 makes it work again
Updating to F10 according to comment #4.
*** This bug has been marked as a duplicate of bug 438046 ***