From: Andrew Clayton <andrew@digital-domain.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc strange hotplug/udev/uevent problem
Date: Tue, 8 Aug 2006 22:33:21 +0100 [thread overview]
Message-ID: <20060808223321.45802fec@alpha.digital-domain.net> (raw)
In-Reply-To: <20060808060211.GA3206@kroah.com>
On Mon, 7 Aug 2006 23:02:11 -0700, Greg KH wrote:
> On Mon, Aug 07, 2006 at 08:33:08PM +0100, Andrew Clayton wrote:
> > 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?
I've done a binary search of kernels and found that the breakage occurs
between 2.6.17-git3 and 2.6.17-git4
Next I'll figure out git bisect to try and narrow it further.
> thansk,
>
> greg k-h
Cheers,
Andrew
next prev parent reply other threads:[~2006-08-08 21:33 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
2006-08-08 9:14 ` Andrew Clayton
2006-08-08 21:33 ` Andrew Clayton [this message]
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=20060808223321.45802fec@alpha.digital-domain.net \
--to=andrew@digital-domain.net \
--cc=greg@kroah.com \
--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