From: Bill Davidsen <davidsen@tmr.com>
To: Thomas Schlichter <schlicht@uni-mannheim.de>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.60-mm2
Date: Sun, 16 Feb 2003 20:59:54 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.1030216205709.29049B-101000@gatekeeper.tmr.com> (raw)
In-Reply-To: <200302141110.49348.schlicht@uni-mannheim.de>
[-- Attachment #1: signed data --]
[-- Type: TEXT/PLAIN, Size: 552 bytes --]
On Fri, 14 Feb 2003, Thomas Schlichter 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?!
I was looking for network issues when I started timing pings, and didn't
see any. I thought it was bad timing, link not raining when you have a
coat, but maybe I was curing it.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
[-- Attachment #2: signature --]
[-- Type: APPLICATION/PGP-SIGNATURE, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-17 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 9:31 2.5.60-mm2 Andrew Morton
2003-02-14 9:38 ` 2.5.60-mm2 Dave Jones
2003-02-14 9:58 ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:13 ` 2.5.60-mm2 Dave Jones
2003-02-14 10:22 ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:10 ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 1:59 ` Bill Davidsen [this message]
2003-02-17 12:08 ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:35 ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 18:32 ` 2.5.60-mm2 Bill Davidsen
2003-02-14 20:59 ` compile fail: 2.5.60-mm2 Core
2003-02-14 22:06 ` Andrew Morton
2003-02-15 20:27 ` 2.5.60-mm2 Arador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.96.1030216205709.29049B-101000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=schlicht@uni-mannheim.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox