mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: neilb@cse.unsw.edu.au, trond.myklebust@fys.uio.no,
	vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Various trouble in 2.5.31
Date: Tue, 13 Aug 2002 17:15:06 +0200	[thread overview]
Message-ID: <15705.8826.187824.60331@charged.uio.no> (raw)
In-Reply-To: <3D58F932.4D87A904@aitel.hist.no>

>>>>> " " == Helge Hafting <helgehaf@aitel.hist.no> writes:

     > Some problems and oddities I have seen: UP, no preempt
     > * nfs gets stuck sometimes.  klogd and rpciod shares the cpu,
     >   umounting is impossible.  cat'ing a nfs file shows the
     >   contents but the cat process won't die.  Stuck on close?
     >   This also happens with 2.5.30

Could you get me a log from tcpdump and 'echo 1 >/proc/sys/sunrpc/rpc_debug'
when this happens?

Cheers,
  Trond

  reply	other threads:[~2002-08-13 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13 12:18 Helge Hafting
2002-08-13 15:15 ` Trond Myklebust [this message]
2002-08-13 22:40 ` Neil Brown

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=15705.8826.187824.60331@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=vojtech@suse.cz \
    /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

all inboxes | Powered by JetHome®