From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 17 Feb 2003 07:08:19 -0500 (EST) From: Bill Davidsen Subject: Re: 2.5.60-mm2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/SIGNED; PROTOCOL="application/pgp-signature"; MICALG=pgp-sha1; BOUNDARY="Boundary-02=_pCMT+DYGeShQy4x"; CHARSET=iso-8859-1 Content-ID: Sender: owner-linux-mm@kvack.org Return-Path: To: Thomas Schlichter Cc: Linux Kernel Mailing List , linux-mm@kvack.org List-ID: --Boundary-02=_pCMT+DYGeShQy4x Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1 Content-ID: Content-Description: signed data On Sun, 16 Feb 2003, I wrote: > > I've got NFS problems with 2.5.5x - 60-bk3, too, but here I can workaround > > them by simply pinging the NFS-server every second... Funny, but it works! > > Perhaps this can help finding the real bug?! [ let's try this again, not typing in a moving car ] > I was looking for network issues when I started timing pings, and didn't > see any. I thought it was bad timing, like not raining when you have a > coat, but maybe I was curing it. Since it's possible that pings will actually change the problem rather than measure it, I'll tcpdump for a while and see if that tells me anything. I suspected network problems, since tcp has priority over udp in some places. I looked at the code last night, but I don't see anything explaining a ping making things better. Something getting flushed? -- bill davidsen CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. --Boundary-02=_pCMT+DYGeShQy4x Content-Type: APPLICATION/PGP-SIGNATURE Content-ID: Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+TMCpYAiN+WRIZzQRAkV8AJwKY8v7t1jvBMFbyNXaFt1c5QzKbQCdFcXB /KQsXPQPTki+B5HzH3QsQZc= =PNko -----END PGP SIGNATURE----- --Boundary-02=_pCMT+DYGeShQy4x-- -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org