From: Birger Lammering <b.lammering@science-computing.de>
To: trond.myklebust@fys.uio.no
Cc: linux-kernel@vger.kernel.org
Subject: Re: more tcpdumpinfo for nfs3 problem: aix-server
Date: Wed, 9 Jan 2002 16:06:46 +0100 [thread overview]
Message-ID: <15420.23686.566719.128899@stderr.science-computing.de> (raw)
In-Reply-To: <15418.63966.866222.749974@charged.uio.no>
In-Reply-To: <15418.55750.210978.737165@stderr.science-computing.de> <15418.63966.866222.749974@charged.uio.no>
Hi Trond,
Trond Myklebust writes:
> > Now we've tried 2.4.18pre1 and got the same results as
> > before. But with Trond's patches things improved a bit:
>
> Is this problem still only occurring when using amd?
still the same: We couldn't reproduce the problem by mounting
manually. :-(
Strange situation: both, you and the amd-guys, think the bug is
somewhere in the code of the other. And I have no idea, how to circle
in the bug.... (Kernel-debugging???)
cheers,
Birger
>
> Cheers,
> Trond
>
prev parent reply other threads:[~2002-01-09 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 11:36 Birger Lammering
2002-01-08 13:53 ` Trond Myklebust
2002-01-09 16:04 ` Trond Myklebust
2002-01-09 15:06 ` Birger Lammering [this message]
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=15420.23686.566719.128899@stderr.science-computing.de \
--to=b.lammering@science-computing.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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
Powered by JetHome