Description of problem: For the second time I've seen a very strange phenomenon, namely that my two on-board forcedeth NICs wouldn't see Ethernet packets (at least that's what I interpret into it). Version-Release number of selected component (if applicable): kernel-2.6.23.9-85.fc8.x86_64 How reproducible: I've only seen this for the second time, not sure if this is somehow triggerable. Steps to Reproduce: 1. Wait? 2. Try to ping a host over one of the forcedeth NIC (or ping one of this machine's forcedeth interfaces from another machine) Actual results: Ping doesn't get through unless wireshark or tcpdump are running in parallel and set the interface into promiscuous mode (I did that for debugging, when promiscuous, everything gets through). Expected results: Works without promiscuous interface, all the time. Additional info: "ifdown"/"ifup" didn't remedy. I unfortunately didn't try removing the module and loading it again. After a reboot everything works again. I can imagine that this is a PITA to debug, but perhaps somebody else experiences the same problem and can add details.
Created attachment 291086 [details] Output of "lspci"
This problem has hit me again with 2.6.23.14-107.fc8.x86_64. I've set the interface to promiscuous so that I can work, but now would be the time to ask me questions.
Created attachment 293244 [details] wireshark capture with promiscuous interface This is what I captured with wireshark on the affected machine when pinging another host while the interface was set to promiscuous: nils@wombat:~> ping 10.0.1.10 PING 10.0.1.10 (10.0.1.10) 56(84) bytes of data. 64 bytes from 10.0.1.10: icmp_seq=1 ttl=64 time=0.906 ms 64 bytes from 10.0.1.10: icmp_seq=2 ttl=64 time=0.816 ms 64 bytes from 10.0.1.10: icmp_seq=3 ttl=64 time=0.857 ms 64 bytes from 10.0.1.10: icmp_seq=4 ttl=64 time=0.808 ms --- 10.0.1.10 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3001ms rtt min/avg/max/mdev = 0.808/0.846/0.906/0.052 ms nils@wombat:~>
Created attachment 293245 [details] wireshark capture with non-promiscuous interface After setting the interface non-promiscuous ("ifconfig eth1 -promisc"), I captured this while pinging the other host: nils@wombat:~> ping 10.0.1.10 PING 10.0.1.10 (10.0.1.10) 56(84) bytes of data. --- 10.0.1.10 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 2999ms nils@wombat:~>
Is there anything else I need to test or check while the problem is manifest? I'd like to get this done quickly so that I can shut down the machine when not in use.
What does the 'ifconfig eth0' command print?
This is with the interfaces set to promiscuous mode: --- 8< --- root@wombat:~> ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:18:F3:7D:21:3C inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::218:f3ff:fe7d:213c/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:2112 errors:0 dropped:0 overruns:0 frame:0 TX packets:17367 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:127755 (124.7 KiB) TX bytes:9420413 (8.9 MiB) Interrupt:253 Base address:0xc000 root@wombat:~> ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:18:F3:7D:24:EC inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::218:f3ff:fe7d:24ec/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:314432 errors:0 dropped:0 overruns:0 frame:0 TX packets:385922 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:41481525 (39.5 MiB) TX bytes:266095627 (253.7 MiB) Interrupt:252 Base address:0xe000 --- >8 --- And this with the interfaces set to non-promiscuous: --- 8< --- root@wombat:~> ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:18:F3:7D:21:3C inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::218:f3ff:fe7d:213c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2112 errors:0 dropped:0 overruns:0 frame:0 TX packets:17371 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:127755 (124.7 KiB) TX bytes:9421293 (8.9 MiB) Interrupt:253 Base address:0xc000 root@wombat:~> ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:18:F3:7D:24:EC inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::218:f3ff:fe7d:24ec/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:314436 errors:0 dropped:0 overruns:0 frame:0 TX packets:385931 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:41481825 (39.5 MiB) TX bytes:266096996 (253.7 MiB) Interrupt:252 Base address:0xe000 --- >8 --- NB: eth1 is the more heavily utilized one of both forcedeth interfaces, as it's facing the WLAN and gets my laptop's traffic.
Just another datapoint: Usually, I suspend the machine to disk when not in use -- maybe the problem is connected to the suspending/resuming of the driver.
Hmm, seems to be a known problem: http://lkml.org/lkml/2008/1/2/253 So does suspending and resuming again fix it?
It seems it does: 1. I started a ping on my WLAN access point (with the interfaces set to promiscuous, the pings went through) 2. I set the interfaces to non-promiscuous, the pings stopped to go through 3. After hibernate/wakeup, pings went through again
Should be fixed in 2.6.24... please test 2.6.24.3-22 when it appears in updates-testing.
*** Bug 437284 has been marked as a duplicate of this bug. ***
Still present in F9, kernel-2.6.25.3-18.fc9.x86_64
... and 2.6.25.4-30.fc9.x86_64
One thing is different than on F8 though -- suspend/resume doesn't help anymore, I've got to set the interfaces to promiscuous every time I wake the machine up from hibernation.
So it's like the MAC address now gets reversed one time on the first hibernation and then never again?
(In reply to comment #16) > So it's like the MAC address now gets reversed one time on the first hibernation > and then never again? I can't say for certain that it would change the MAC address (ifconfig would always show the correct one), only that the symptoms are similar: after first hibernation, the focedeth NICs only let things through when set to promiscuous, or when the driver is reloaded (ifdown ...; rmmod ...; ifup ...). FWIW, the kernel is 2.6.25.6-55.fc9.x86_64.
Same symptoms with 2.6.25.10-86.fc9.x86_64. Is there any other information you need to work on this?
Same symptoms with kernel-2.6.25.11-97.fc9.x86_64...
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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
Haven't seen this on F-10, closing.