From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Greg KH <gregkh@suse.de>
Cc: Adrian Bunk <bunk@stusta.de>, Robert Love <rml@novell.com>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>,
kay.sievers@suse.de
Subject: Re: 2.6.16-rc4: known regressions
Date: Wed, 22 Feb 2006 00:51:01 +0200 [thread overview]
Message-ID: <1140562261.11278.6.camel@localhost> (raw)
In-Reply-To: <20060220010205.GB22738@suse.de>
On Sun, 2006-02-19 at 17:02 -0800, Greg KH wrote:
> If you revert this one patch, on top of a clean 2.6.16-rc4, do things
> start working for you again?
Okey dokey, bisecting with mrproper took little longer than expected but
I found the bad changeset:
033b96fd30db52a710d97b06f87d16fc59fee0f1 is first bad commit
diff-tree 033b96fd30db52a710d97b06f87d16fc59fee0f1 (from 0f76e5acf9dc788e664056dda1e461f0bec93948)
Author: Kay Sievers <kay.sievers@suse.de>
Date: Fri Nov 11 06:09:55 2005 +0100
[PATCH] remove mount/umount uevents from superblock handling
The names of these events have been confusing from the beginning
on, as they have been more like claim/release events. We needed these
events for noticing HAL if storage devices have been mounted.
Thanks to Al, we have the proper solution now and can poll()
/proc/mounts instead to get notfied about mount tree changes.
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
:040000 040000 0397ffe6fdbffa290e2d22f5f59c5a8cc2861ef0 44e4df27174f1dfb125481f9ce4471edaa93c57d M fs
:040000 040000 94178115d8c608d6247bed322efeddf19047ad99 55655fc60af26aed51a7d3ddee452c859ec3c501 M include
:040000 040000 40bd1625895ddca1d39381887587f4465abed222 397331a2cd3077cd3f41901f4af74ab6ad3fb13a M lib
Reverting the above from yesterday's git head fixes the problem for me
and I get my Ipod icon in Gnome again. I am running udev 079, dbus 060,
hal 0.5.5.1, and gnome-volume-manager 1.5.4 on Gentoo/x86. The patch
should probably be reverted for 2.6.16 because it breaks userspace.
Pekka
next prev parent reply other threads:[~2006-02-21 22:51 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 22:45 Linux 2.6.16-rc4 Linus Torvalds
2006-02-17 23:14 ` 2.6.16-rc4: known regressions Adrian Bunk
2006-02-19 11:06 ` Pekka Enberg
2006-02-19 14:54 ` Adrian Bunk
2006-02-19 17:50 ` Pekka Enberg
2006-02-19 21:14 ` Pekka Enberg
2006-02-20 1:02 ` Greg KH
2006-02-20 7:08 ` Pekka J Enberg
2006-02-21 22:51 ` Pekka Enberg [this message]
2006-02-21 22:57 ` Kay Sievers
2006-02-21 23:33 ` Andrew Morton
2006-02-22 0:04 ` Kay Sievers
2006-02-22 0:15 ` Mark Lord
2006-02-22 0:21 ` Andrew Morton
2006-02-22 0:34 ` Linus Torvalds
2006-02-22 0:46 ` Con Kolivas
2006-02-22 1:06 ` Linus Torvalds
2006-02-22 11:21 ` Theodore Ts'o
2006-02-22 14:25 ` uswsusp & initrd -- was " Pavel Machek
2006-02-22 15:48 ` Joel Becker
2006-02-22 16:25 ` Theodore Ts'o
2006-02-22 17:33 ` Gabor Gombas
2006-02-22 17:57 ` Linus Torvalds
2006-02-22 18:37 ` Christian Trefzer
2006-02-22 18:59 ` Joel Becker
2006-02-22 19:18 ` Greg KH
2006-02-22 19:29 ` Arjan van de Ven
2006-02-22 19:40 ` Greg KH
2006-02-22 20:45 ` Jens Axboe
2006-02-22 22:51 ` Greg KH
2006-02-23 6:39 ` Jens Axboe
2006-02-23 17:29 ` Martin Bligh
2006-02-23 17:52 ` Greg KH
2006-02-23 18:01 ` Martin Bligh
2006-02-23 18:04 ` Arjan van de Ven
2006-02-23 20:26 ` Benjamin LaHaise
2006-02-24 23:42 ` Eric W. Biederman
2006-02-22 19:39 ` Linus Torvalds
2006-02-22 19:54 ` Andrew Morton
2006-02-22 20:02 ` Arjan van de Ven
2006-02-22 20:12 ` Linus Torvalds
2006-02-22 20:44 ` Andrew Morton
2006-02-22 20:26 ` Greg KH
2006-02-23 5:28 ` Jody McIntyre
2006-02-22 20:57 ` Diego Calleja
2006-02-22 21:19 ` Russell King
2006-02-22 21:30 ` Greg KH
2006-02-22 20:47 ` Bryan O'Sullivan
2006-02-22 19:07 ` Greg KH
2006-02-22 17:06 ` Matthias Andree
2006-02-23 12:36 ` Paulo Marques
2006-02-22 10:49 ` Diego Calleja
2006-02-22 7:06 ` Pekka J Enberg
2006-02-22 15:27 ` Kay Sievers
2006-02-22 15:44 ` Linus Torvalds
2006-02-22 16:03 ` Arjan van de Ven
2006-02-22 16:11 ` Christoph Hellwig
2006-02-22 17:17 ` sysfs regressions (was: 2.6.16-rc4: known regressions) Matthias Andree
2006-02-22 17:47 ` Greg KH
2006-02-22 16:18 ` 2.6.16-rc4: known regressions David Zeuthen
2006-02-22 16:35 ` Christoph Hellwig
2006-02-22 16:46 ` David Zeuthen
2006-02-22 16:51 ` Christoph Hellwig
2006-02-22 17:08 ` Linus Torvalds
2006-02-22 17:31 ` Linus Torvalds
2006-02-22 18:04 ` Al Viro
2006-02-23 3:01 ` John Stoffel
2006-02-22 17:51 ` Al Viro
2006-02-22 17:55 ` Christoph Hellwig
2006-02-22 18:10 ` Al Viro
2006-02-22 19:25 ` David Zeuthen
2006-02-22 17:10 ` Al Viro
2006-02-22 17:10 ` grundig
2006-02-22 17:14 ` Martin Bligh
2006-02-23 4:17 ` Theodore Ts'o
2006-02-22 18:10 ` Pekka Enberg
2006-02-22 8:28 ` Arjan van de Ven
2006-02-17 23:27 ` Linux 2.6.16-rc4 Nigel Cunningham
2006-02-18 8:59 ` Edmondo Tommasina
2006-02-18 9:19 ` Gene Heskett
2006-02-18 10:20 ` Con Kolivas
2006-02-18 11:26 ` Gene Heskett
2006-02-18 16:04 ` Jean Delvare
2006-02-22 22:02 ` Linux 2.6.16-rc4 edac oops Mark Rustad
2006-02-24 11:09 ` Andrew Morton
2006-02-22 2:39 2.6.16-rc4: known regressions Yu, Luming
2006-02-22 3:16 ` Adrian Bunk
2006-02-22 6:55 Yu, Luming
2006-02-22 12:23 ` Adrian Bunk
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=1140562261.11278.6.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=torvalds@osdl.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).