public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: torvalds@linux-foundation.org, agruen@suse.de, neilb@suse.de,
	viro@zeniv.linux.org.uk, hch@lst.de, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Bug in current -git tree causing dbus and gnome to chew up cpu time
Date: Tue, 13 Feb 2007 11:51:16 -0800	[thread overview]
Message-ID: <20070213195116.GA5181@kroah.com> (raw)

Hi,

I've used 'git bisect' to track down a change in the latest git tree
that is causing dbus-daemon to sit and spin at the time GNOME launches,
preventing nautlius from ever running.

The bad commit is:
commit eb3dfb0cb1f4a44e2d0553f89514ce9f2a9fcaf1
Author: Andreas Gruenbacher <agruen@suse.de>
Date:   Mon Feb 12 00:51:47 2007 -0800

    [PATCH] Fix d_path for lazy unmounts

With that patch out, GNOME startup works just fine.  I have a strace of
the dbus process running showing the problem, if anyone thinks that will
help out any.

I'm running pretty new GNOME and dbus here:
	dbus 1.0.2
	gnome 2.16.2
	hal 0.5.7.1
	nautilus 2.16.3

Any ideas of things I can test?

thanks,

greg k-h

             reply	other threads:[~2007-02-13 19:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 19:51 Greg KH [this message]
2007-02-13 19:58 ` Bug in current -git tree causing dbus and gnome to chew up cpu time Andreas Gruenbacher
     [not found]   ` <20070213200132.GA6149@kroah.com>
2007-02-13 20:16     ` Andreas Gruenbacher
2007-02-13 21:37   ` Greg KH
2007-02-13 22:30     ` Andreas Gruenbacher
2007-02-13 22:39     ` Neil Brown
2007-02-13 23:03       ` Andreas Gruenbacher
2007-02-14  9:47 ` Alessandro Suardi
2007-02-14  9:57   ` Andreas Gruenbacher
2007-02-14 11:13     ` Alessandro Suardi
2007-02-14 16:39       ` Greg KH

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=20070213195116.GA5181@kroah.com \
    --to=greg@kroah.com \
    --cc=agruen@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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