public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Thibaut VARENE" <T-Bone@parisc-linux.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] add help to WAIT_SCAN option
Date: Sun, 27 May 2007 00:25:22 +0200	[thread overview]
Message-ID: <7d01f9f00705261525k56cd1b9ag531640cc212036ae@mail.gmail.com> (raw)
In-Reply-To: <20070526204447.GM5798@parisc-linux.org>

On 5/26/07, Matthew Wilcox <matthew@wil.cx> wrote:
> On Sat, May 26, 2007 at 01:11:27PM -0600, Grant Grundler wrote:
> > Thibaut Varene's parisc box didn't find the root disk.
> > Problem is he had ASYNC_SCAN enabled and the required SYM2 driver builtin
> > but the root disk wasn't discovered before the kernel wanted to mount root.
> > Oh, and he (like many folks who build their own kernels) didn't use
> > an initrd or initramfs. So no chance to load scsi_wait_scan module.
>
> I don't know what Thibaut's problem was, but this explanation is
> definitely incorrect.  If you build in the sym2 driver and the scsi
> core, then we wait for the discs to be discovered automatically.

My problem was that:
- I use a standalone kernel (no init{rd,ramfs})
- I have CONFIG_MODULES=y
- I build all my (needed) scsi drivers 'y' (builtin)

Yet CONFIG_SCSI_WAIT_SCAN defaults to 'm' with no possibility of
setting it otherwise. So I ended up with a kernel with builtin async
scsi scan and no wait_scan, thus not waiting for the probes to
complete before trying to mount rootfs...

Editing KConfig to allow setting CONFIG_SCSI_WAIT_SCAN=y "fixed" the problem.

HTH

T-Bone

-- 
Thibaut VARENE
http://www.parisc-linux.org/~varenet/

  reply	other threads:[~2007-05-26 22:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26 19:11 [PATCH] add help to WAIT_SCAN option Grant Grundler
2007-05-26 19:50 ` James Bottomley
2007-05-27  0:06   ` Grant Grundler
2007-05-27  0:15     ` James Bottomley
2007-05-27  0:27       ` Matthew Wilcox
2007-05-27  0:29         ` James Bottomley
2007-05-27  0:33           ` Matthew Wilcox
2007-05-27  0:53             ` Grant Grundler
2007-05-26 20:44 ` Matthew Wilcox
2007-05-26 22:25   ` Thibaut VARENE [this message]
2007-05-26 23:03     ` Matthew Wilcox
2007-05-26 23:10       ` Thibaut VARENE
2007-05-27  0:05         ` Matthew Wilcox

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=7d01f9f00705261525k56cd1b9ag531640cc212036ae@mail.gmail.com \
    --to=t-bone@parisc-linux.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=grundler@parisc-linux.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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