From: Oleg Drokin <green@namesys.com>
To: "J. Tang" <tang@jtang.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops: nfsd/reiserfs, 2.4.20 with preemption
Date: Fri, 21 Feb 2003 11:10:42 +0300 [thread overview]
Message-ID: <20030221111042.A29170@namesys.com> (raw)
In-Reply-To: <20030220182949.557DC3E62@cavall.jtang.org>
Hello!
On Thu, Feb 20, 2003 at 01:29:49PM -0500, J. Tang wrote:
> I have been experiencing some very odd nfs problems lately; eventually I
> was able to get this output:
> EIP: 0010:[<d6bec2b0>] Not tainted
...
Can you run this through ksymoops please?
Bye,
Oleg
prev parent reply other threads:[~2003-02-21 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 18:29 Oops: nfsd/reiserfs, 2.4.20 with preemption J. Tang
2003-02-21 8:10 ` Oleg Drokin [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=20030221111042.A29170@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tang@jtang.org \
/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