Messages in this thread |  | | | Date | Wed, 23 Jun 2004 16:14:47 +0000 | | From | Mikael Bouillot <> | | Subject | Re: Forcedeth driver bug |
| |
> Are you sure both come back? If so, what does dmesg say during this time? > Is the system in question under heavy load? > > Can you confirm that the ping packet got stuck in the receive path or > could the associated pong reply have gotten stuck in the send path?
A tcpdump at the remote end shows the packet leaving, but a tcpdump at the local side doesn't show it until the next packet arrives. I tried this on a system running nothing but tcpdump, but the network load is high (ping sends packets as soon as the previous reply comes back).
> It could be a weird interaction with interrupt mitigation, but I doubt it. > Nobody has ever mailed me about such problems with the driver.
Another note: I run my 2.6.7 with Local APIC and IO-APIC. Maybe that has to do with interrupt problems. I will try reverting to the older PIC during further testing to see if that has an effect on things.
> forcedeth_gigabit_try19.txt is the most recent one. > Changes against try17: > - fix compilation warnings and rename the Kconfig entry > > Get it at > http://www.hailfinger.org/carldani/linux/patches/forcedeth/ > and please report if it fixes your problem.
OK, I'll do that.
-- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |