From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "Greg KH" <greg@kroah.com>
Cc: torvalds@linux-foundation.org, agruen@suse.de, neilb@suse.de,
viro@zeniv.linux.org.uk, hch@lst.de, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: Bug in current -git tree causing dbus and gnome to chew up cpu time
Date: Wed, 14 Feb 2007 10:47:27 +0100 [thread overview]
Message-ID: <5a4c581d0702140147s7931bd63ief299780fa6963a5@mail.gmail.com> (raw)
In-Reply-To: <20070213195116.GA5181@kroah.com>
On 2/13/07, Greg KH <greg@kroah.com> wrote:
> 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?
Just to add a data point, I see the same problem (startx never
completes, gnome-vfs-daemon keeps getting forked by dbus
to no end) on 2.6.20-git9 while -git7 is fine, and my pieces are
from FC6 updates as of two days ago or so:
[asuardi@sandman ~]$ rpm -q dbus gnome-vfs2 hal nautilus
dbus-1.0.1-9.fc6
gnome-vfs2-2.16.2-2.fc6
hal-0.5.8.1-6.fc6
nautilus-2.16.2-7.fc6
Since the patch breaks userspace in a deadly way, I guess
it should be reverted until an usable version of the fix can
be found. And yes, I'm up for testing of course.
--alessandro
"but I thought that I should let you know
the things that I don't always show
might not be worth the time it took"
(Steve Wynn, 'If My Life Was An Open Book')
next prev parent reply other threads:[~2007-02-14 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 19:51 Bug in current -git tree causing dbus and gnome to chew up cpu time Greg KH
2007-02-13 19:58 ` 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 [this message]
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=5a4c581d0702140147s7931bd63ief299780fa6963a5@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=agruen@suse.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--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;
as well as URLs for NNTP newsgroup(s).