On Mon, Sep 27, 2004 at 04:18:45PM -0700, David S. Miller wrote:
> In particular, if there are hubs or switches involved on
> your local network that might be getting the duplex wrong,
> or some NAT or firewall machines in the path in question,
> please specify their setup precisely.
>
> Otherwise there is zero chance of this problem ever being
> fixes.
Well I was going to do a few more tests and send a nice email doing just
that but in going through my package list with dpkg I spotted cpudyn and
cpufreqd installed. I've uninstalled them and now I cannot reproduce
the problem.
As such, and I hope I'm not speaking to you, it appears 'solved'. They
must've been interfering with the network layer somehow (or something)
and now that they are gone all's well.
My apologies if anyones time was wasted.
--
Red herrings strewn hither and yon.
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
