linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: linux-nfs@vger.kernel.org
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	linux-hotplug@vger.kernel.org
Subject: Re: very slow NFS boot on linux-next and -mm
Date: Sun, 03 May 2009 12:40:13 +0000	[thread overview]
Message-ID: <20090503124013.GA31700@localhost> (raw)
In-Reply-To: <20090503105456.GA30449@localhost>

Ah it's not really a NFS problem..

On Sun, May 03, 2009 at 06:54:56PM +0800, Wu Fengguang wrote:
> 
> My NFSROOT box sometimes will get stuck for a dozen seconds during boot.
> 
[snip]
> The NFSROOT client that got stuck is running latest linux-next, the
> server side is running 2.6.30-rc3.
> 
> Switching the client kernel to latest -mm makes it very reproducible.
> Here is another stack dump:
> 
> [  180.399845] udevd         D ffff8800280291e0  3056  1388      1

The udevd is doing this busy loop like mad:

        open("/etc/group", O_RDONLY|O_CLOEXEC)  = 7
        lseek(7, 0, SEEK_CUR)                   = 0
        fstat(7, {st_mode=S_IFREG|0644, st_sizey7, ...}) = 0
        mmap(NULL, 797, PROT_READ, MAP_SHARED, 7, 0) = 0x7f6791601000
        lseek(7, 797, SEEK_SET)                 = 797
        munmap(0x7f6791601000, 797)             = 0
        close(7)                                = 0

udev version is 0.141-1.

Thanks,
Fengguang


       reply	other threads:[~2009-05-03 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090503105456.GA30449@localhost>
2009-05-03 12:40 ` Wu Fengguang [this message]
2009-05-03 12:56   ` very slow NFS boot on linux-next and -mm Kay Sievers
     [not found]     ` <20090504133019.GA14300@localhost>
2009-05-06 13:42       ` Kay Sievers
2009-05-07 11:59         ` [PATCH] inotify: report rounded-up event size to user space Wu Fengguang
2009-05-07 12:16           ` Eric Paris

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=20090503124013.GA31700@localhost \
    --to=fengguang.wu@intel.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-nfs@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).