From: Greg KH <greg@kroah.com>
To: Andrew Clayton <andrew@digital-domain.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc strange hotplug/udev/uevent problem
Date: Mon, 7 Aug 2006 23:02:11 -0700 [thread overview]
Message-ID: <20060808060211.GA3206@kroah.com> (raw)
In-Reply-To: <44D79574.8080703@digital-domain.net>
On Mon, Aug 07, 2006 at 08:33:08PM +0100, Andrew Clayton wrote:
> Hi,
>
> Got a weird problem here.
>
> On x86 Fedora Core 5 with 2.6.17 with GNOME, plugging in a usb stick
> would result in it being mounted. With 2.6.18-rc this no longer occurs.
> FC5 got an update to hal to work with 2.6.18 kernels, but it don't work
> for me. I'm having the same problem on 3 x86 FC5 machines.
>
> The weird thing is, this all works on my x86-64 FC5 workstation with
> 2.6.18-rc both before and after the hal update.
>
> Anyway I submitted a bug report against HAL suspecting it broken
>
> https://bugs.freedesktop.org/show_bug.cgi?id=7756
>
> Perhaps not. So I turn my attention more to the kernel.
>
>
> 2.6.17 was working fine. You could plug/unplug/plug a USB memory stick
> and it would get mounted each time.
>
> 2.6.18-rc[23] works the same as above on my x86-64 FC5 box.
>
> 2.6.18-rc[23] and 2.6.18-rc3-git7 on x86 built with
> usb/scsi/sd/vfat/nls_* built as modules will mount on the first plug but
> not subsequent plugs.
>
> If you rmmod the sd_mod module and plug in, then it will get mounted.
That's just wierd. I can't think of anything that has changed recently
to cause this.
Can you use 'git bisect' to try to narrow it down which change caused
the problem?
thansk,
greg k-h
next prev parent reply other threads:[~2006-08-08 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 19:33 2.6.18-rc strange hotplug/udev/uevent problem Andrew Clayton
2006-08-08 6:02 ` Greg KH [this message]
2006-08-08 9:14 ` Andrew Clayton
2006-08-08 21:33 ` Andrew Clayton
2006-08-09 0:41 ` Andrew Clayton
2006-08-09 7:54 ` Andrew Morton
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=20060808060211.GA3206@kroah.com \
--to=greg@kroah.com \
--cc=andrew@digital-domain.net \
--cc=linux-kernel@vger.kernel.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