From: Neil Brown <neilb@suse.de>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SCSI discover order strangeness [Bug 8412] New: CONFIG_MOUSE_PS2 makes RAID detection fail
Date: Mon, 7 May 2007 14:22:58 +1000 [thread overview]
Message-ID: <17982.43426.945725.747958@notabene.brown> (raw)
In-Reply-To: message from Greg KH on Tuesday May 1
On Tuesday May 1, greg@kroah.com wrote:
> On Tue, May 01, 2007 at 07:46:36PM +1000, Neil Brown wrote:
> >
> > My first thought was that the new threaded device discovery was
> > allowing md init to happen before scsi discovery was complete. Maybe
> > the presence of CONFIG_MOUSE_PS2 makes some bit go faster...
> >
> > However
> > # CONFIG_SCSI_SCAN_ASYNC is not set
> >
> > so maybe not...
> >
> > Greg (or anyone else reading): you know about this threaded
> > discovery.. could it allow some discovery to complete after userspace
> > has started, and does CONFIG_SCSI_SCAN_ASYNC affect it?
>
> This kind of threaded discovery is different from the bus-level threaded
> probing that I originally proposed a while back, and then later
> retracted due to bugs.
>
> So this is just a scsi thing, I know nothing about it.
>
OK, thanks. It turns out they are USB drives, so maybe it is a USB
problem, or maybe their expectations are wrong.
It also turns out that the email->bugzilla gateway completely failed
for me in trying to deal with this bug. Ho hum.
NeilBrown
prev parent reply other threads:[~2007-05-07 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705010918.l419IC8B016596@fire-2.osdl.org>
2007-05-01 9:46 ` Neil Brown
2007-05-02 3:31 ` Greg KH
2007-05-07 4:22 ` Neil Brown [this message]
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=17982.43426.945725.747958@notabene.brown \
--to=neilb@suse.de \
--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
all inboxes | Powered by JetHome®