Bug 7065

Summary:	Devices no longer automount
Product:	Drivers	Reporter:	Andrew Clayton (andrew)
Component:	Other	Assignee:	Greg Kroah-Hartman (greg)
Status:	REJECTED INVALID
Severity:	normal	CC:	bugzilla, kay
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.18-rc5	Subsystem:
Regression:	---	Bisected commit-id:

Description Andrew Clayton 2006-08-28 09:52:33 UTC

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 <kay.sievers@suse.de>
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 <kay.sievers@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

:040000 040000 468b93360ff68fb133558a84f609731ddc2d846a
4db81e3af789cb7c0c3faea57a9f36ffa00732c3 M      drivers


Reverting this patch fix'd the problem. Seems though that this is not the ideal
solution.

Comment 1 Greg Kroah-Hartman 2006-08-28 10:13:10 UTC

Kay, any thoughts here?

Comment 2 Greg Kroah-Hartman 2006-08-30 01:12:17 UTC

As per the freedesktop team, this was an invalid userspace configuration, 
and didn't have anything to do with the kernel.

Am closing as invalid.