On Mon, 28 Aug 2006 10:00:12 -0700
[email protected] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=7065
>
> Summary: Devices no longer automount
A post-2.6.17 regression, nicely bisected down to a particular changeset
(thanks!).
Is anyone else hitting this?
> Kernel Version: 2.6.18-rc5
> Status: NEW
> Severity: normal
> Owner: [email protected]
> Submitter: [email protected]
>
>
> Most recent kernel where this bug did not occur:
> 2.6.17-git3
>
> Distribution:
> Fedora Core 5
>
> Hardware Environment:
> x86 UP (Athlon and P4)
>
> Software Environment:
> FC5 + latest updates
>
> Problem Description:
> When in GNOME and a USB storage device is plugged in, the device is no
> longer mounted automatically.
>
> Steps to reproduce:
> When in GNOME, plug in a USB storage device e.g USB memory stick.
>
> Seems uvents for the mount command are not being generated.
>
> Last bit of output from udevmonitor for working kernel
>
> UEVENT[1154789231.832312] add@/block/sda
> UEVENT[1154789231.834681] add@/block/sda/sda1
> UDEV [1154789231.836590] add@/class/scsi_device/9:0:0:0
> UDEV [1154789231.933474] add@/block/sda
> UDEV [1154789232.106892] add@/block/sda/sda1
> UEVENT[1154789235.937510] mount@/block/sda/sda1
> UDEV [1154789235.937510] mount@/block/sda/sda1
>
> Last of bit of output from non-working kernel
>
> UEVENT[1154789364.586896] add@/block/sda
> UEVENT[1154789364.586954] add@/block/sda/sda1
> UEVENT[1154789364.586963] add@/class/scsi_device/10:0:0:0
> UDEV [1154789364.598962] add@/class/scsi_device/10:0:0:0
> UDEV [1154789364.719350] add@/block/sda
> UDEV [1154789364.874149] add@/block/sda/sda1
>
>
> This regression happened between 2.6.17-git3 and 2.6.17-git4
>
> A GIT bisect led to the following culprit.
>
> 53877d06d53a412d901bb323f080296c363d8b51 is first bad commit
> commit 53877d06d53a412d901bb323f080296c363d8b51
> Author: Kay Sievers <[email protected]>
> Date: Tue Apr 4 20:42:26 2006 +0200
>
> [PATCH] Driver core: bus device event delay
>
> split bus_add_device() and send device uevents after sysfs population
>
> Signed-off-by: Kay Sievers <[email protected]>
> Signed-off-by: Greg Kroah-Hartman <[email protected]>
>
> :040000 040000 468b93360ff68fb133558a84f609731ddc2d846a
> 4db81e3af789cb7c0c3faea57a9f36ffa00732c3 M drivers
>
>
> Reverting this patch fix'd the problem. Seems though that this is not the ideal
> solution.
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
On Mon, Aug 28, 2006 at 12:10:57PM -0700, Andrew Morton wrote:
> On Mon, 28 Aug 2006 10:00:12 -0700
> [email protected] wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=7065
> >
> > Summary: Devices no longer automount
>
> A post-2.6.17 regression, nicely bisected down to a particular changeset
> (thanks!).
>
> Is anyone else hitting this?
>
>
> > Kernel Version: 2.6.18-rc5
> > Status: NEW
> > Severity: normal
> > Owner: [email protected]
> > Submitter: [email protected]
This was narrowed down to a broken userspace configuration by the
freedesktop.org developers.
Many thanks to them.
So no kernel issue here.
thanks,
greg k-h
--
VGER BF report: U 0.46418
Greg KH wrote:
> This was narrowed down to a broken userspace configuration by the
> freedesktop.org developers.
>
> Many thanks to them.
>
> So no kernel issue here.
>
Do you have a reference to what the fix is?
Thanks,
J
--
VGER BF report: H 0
On Sat, Sep 02, 2006 at 02:48:20AM -0700, Jeremy Fitzhardinge wrote:
> Greg KH wrote:
> >This was narrowed down to a broken userspace configuration by the
> >freedesktop.org developers.
> >
> >Many thanks to them.
> >
> >So no kernel issue here.
> >
>
> Do you have a reference to what the fix is?
Are you having this same problem? I think it was an invalid HAL
configuration file from what I heard. Kay would know for sure.
thanks,
greg k-h
--
VGER BF report: H 0
Greg KH wrote:
> Are you having this same problem? I think it was an invalid HAL
> configuration file from what I heard. Kay would know for sure.
>
Yes. The automounting device stuff has always been a bit random. It
worked at first with a fresh FC6-T1 install, but it has become pretty
flakey lately. I'd never got around to trying to track down how it all
really works.
J
--
VGER BF report: H 3.01476e-12
On Sat, 2 Sep 2006 02:51:43 -0700, Greg KH wrote:
> On Sat, Sep 02, 2006 at 02:48:20AM -0700, Jeremy Fitzhardinge wrote:
> > Greg KH wrote:
> > >This was narrowed down to a broken userspace configuration by the
> > >freedesktop.org developers.
> > >
> > >Many thanks to them.
> > >
> > >So no kernel issue here.
> > >
> >
> > Do you have a reference to what the fix is?
>
> Are you having this same problem? I think it was an invalid HAL
> configuration file from what I heard. Kay would know for sure.
I was unsure what was actually broke as it happened at the same time on
three different machines.
On my laptop I removed udev and hal and reinstalled them (got an
updated udev in the process) and now it works with 2.6.18-rc5.
> thanks,
>
> greg k-h
Cheers,
Andrew