Re: [Bugme-new] [Bug 7065] New: Devices no longer automount



On Mon, 28 Aug 2006 10:00:12 -0700
bugme-daemon@xxxxxxxxxxxxxxxxxxx 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: other_other@xxxxxxxxxxxxxxxxxxxx
Submitter: andrew@xxxxxxxxxxxxxxxxxx


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@xxxxxxx>
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@xxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>

: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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: [PATCH] (Re: regression tracking (Re: Linux 2.6.21))
    ... >> The problem is that we aren't able to handle the many regression reports ... >> spent much time and energy in writing a good bug report. ... >> source of quality problems in the Linux kernel. ...
    (Linux-Kernel)
  • Re: [PATCH] x86/paravirt: revert exports to restore old behaviour
    ... Christoph Hellwig objects to this patch on the grounds that modules ... CONFIG_PARAVIRT and non-CONFIG_PARAVIRT configurations. ... Current practice in the kernel is that when something that should not be ... It cannot be a regression since the kernel does not have a stable API ...
    (Linux-Kernel)
  • Re: [regression] Re: brk randomization breaks columns
    ... I believe it shows clear regression in latest 2.6.25 kernel. ... disables or enables it. ... Those "invalid assumptions" crept into documentation. ...
    (Linux-Kernel)
  • Re: How to improve the quality of the kernel?
    ... >> 20 other patches in the tree depending on it causing a regression, ... > "If the patch introduces a new regression" ... >> problem which lies in our bug handling. ... There's now much money in the Linux market, and the kernel quality ...
    (Linux-Kernel)