linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Bertoncin - Sun Microsystems UK - Platform OS Development Engineer <Marco.Bertoncin@Sun.COM>
To: linux-kernel@vger.kernel.org
Subject: Re: NFS/MOUNT/sunrpc problem?
Date: Wed, 10 Sep 2003 17:08:19 +0100 (BST)	[thread overview]
Message-ID: <200309101608.h8AG8J101998@brk-mail1.uk.sun.com> (raw)



I just realized I sent my reply only to Alan ... sorry!


------------- Begin Forwarded Message -------------

Date: Wed, 10 Sep 2003 17:02:24 +0100 (BST)
From: Marco Bertoncin - Sun Microsystems UK - Platform OS Development Engineer 
<mb144209@ms-ebrk02-02.uk>
Subject: Re: NFS/MOUNT/sunrpc problem?
To: alan@lxorguk.ukuu.org.uk



Alan,
thanks for replying so quickly!

> Update the kernel once installed, the 2.4.18- kernels are obsoleted by
> other security fixes

Yes, we are working with several versions (rh-8.0, rh-9.0, as2.1, el3.0a2), and 
would like to support all of them. If this was for internal use, we would just 
go to the most up-to-date version, but sometimes customers are reluctant to 
upgrade (don't ask, I am not a marketing person :-))))

> 
> I've seen one other report of this (with a via chip),
>

This is with Intel82801CA

 
> Are you using NFS root or just NFS mounts ?

Just NFS mounts. This is how we do PXE install: download vmlinuz and an initial 
initrd.img image. vmlinuz uncompresses, allocates a RAM disk and mounts 
initrd.img where it finds the modules necessary to carry on (tg3 driver amongst 
them), then it nfs mount a directory from the install server (something like 
/tftp/install/this_release/images/ where it would find configurastion files and 
images for the install) and it is this MOUNT request that, if the reply gets 
lost, starts the storm.
You said you already saw a similar report of this. Is this logged somewhere?

Again, Thanks very much.
Marco


------------- End Forwarded Message -------------



             reply	other threads:[~2003-09-10 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 16:08 Marco Bertoncin - Sun Microsystems UK - Platform OS Development Engineer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-12 17:43 NFS/MOUNT/sunrpc problem? Marco Bertoncin - Sun Microsystems UK - Platform OS Development Engineer
2003-09-12 18:51 ` Trond Myklebust
2003-09-11  9:32 Marco Bertoncin - Sun Microsystems UK - Platform OS Development Engineer
2003-09-11 15:17 ` Trond Myklebust
2003-09-10 14:37 Marco Bertoncin - Sun Microsystems UK - Platform OS Development Engineer
2003-09-10 15:41 ` Alan Cox
2003-09-10 16:20   ` Jeff Garzik
2003-09-11  2:37 ` Trond Myklebust

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=200309101608.h8AG8J101998@brk-mail1.uk.sun.com \
    --to=marco.bertoncin@sun.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).