From: Greg Wooledge <greg@wooledge.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: NFS client hangs when X is running (2.4.20)
Date: Sat, 12 Apr 2003 15:15:13 -0400 [thread overview]
Message-ID: <20030412191512.GA21966@pegasus.wooledge.org> (raw)
In-Reply-To: <shsfzoodpgy.fsf@charged.uio.no>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
Trond Myklebust (trond.myklebust@fys.uio.no) wrote:
> Sounds very much like a network card driver problem.
I don't think so, simply because this has happened to me on two
compeletely different Linux systems. One (griffon) has a 3c59x
card, and the other (dwarf) had a tulip and an ne2k-pci.
(Or did you mean on the server side? The OpenBSD box is using two
RTL 8139 cards.)
> > [5.] nfs: server pegasus not responding, still trying However,
> > this is erroneous. Pegasus (the OpenBSD box) responds
> > perfectly to ping, showmount -e, ssh and so on. Any existing
> > ssh connections to pegasus continue working, even ones I
> > started in an rxvt window in the 15-30 second period when the
> > NFS subsystem hadn't locked up yet. No other errors are
> > reported.
>
> .... and a tcpdump would show?
I haven't tried that yet, but after discussing this with another
person who was having the same problems, we learned that OpenBSD's
firewall (pf) was blocking the Linux packets when configured with
"scrub in all" (which is recommended in the OpenBSD FAQs).
After commenting out the "scrub in all" and rebooting back to 2.4.20,
I have X and NFS working simultaneously.
--
Greg Wooledge | "Truth belongs to everybody."
greg@wooledge.org | - The Red Hot Chili Peppers
http://wooledge.org/~greg/ |
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
prev parent reply other threads:[~2003-04-12 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 23:31 Greg Wooledge
2003-04-12 9:39 ` Trond Myklebust
2003-04-12 19:15 ` Greg Wooledge [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=20030412191512.GA21966@pegasus.wooledge.org \
--to=greg@wooledge.org \
--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
all inboxes | Powered by JetHome®