mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_SCSI_WAIT_SCAN=m
Date: Tue, 3 Apr 2007 17:54:21 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704031736380.9029@blonde.wat.veritas.com> (raw)
In-Reply-To: <1175013257.3737.21.camel@mulgrave.il.steeleye.com>

On Tue, 27 Mar 2007, James Bottomley wrote:
> On Tue, 2007-03-27 at 17:25 +0100, Hugh Dickins wrote:
> > I'm not using an initrd, most of my kernel is builtin,
> > just a few modules for occasional filesystems.
> > 
> > CONFIG_MODULES=y
> > CONFIG_SCSI=y
> > CONFIG_SCSI_SCAN_ASYNC=y
> > CONFIG_SCSI_WAIT_SCAN=m
> > 
> > 2.6.21-rc5-mm2 VFS panics unable to find my root on /dev/sda2,
> > but boots okay if I change drivers/scsi/Kconfig to "default y"
> > instead of "default m" for SCSI_WAIT_SCAN.
> 
> Hmm ... it sounds like there's a missing scsi_complete_async_scans() in
> your environment?

Situation unchanged in 2.6.21-rc5-mm4.  By what route do you expect
scsi_complete_async_scans() to get called usually, in a monolithic
kernel?  Before you made scsi_wait_scan a separate loadable module,
it was called via that late_initcall(wait_scan_init), so perhaps now
we need...


Make sure there's a late_initcall to scsi_complete_async_scans when
it's built in, so a monolithic SCSI_SCAN_ASYNC kernel can rely on the
scans being completed before trying to mount root, even if they're slow.

Signed-off-by: Hugh Dickins <hugh@veritas.com>

--- 2.6.21-rc5-mm4/drivers/scsi/scsi_scan.c	2007-04-03 15:29:21.000000000 +0100
+++ linux/drivers/scsi/scsi_scan.c	2007-04-03 17:24:24.000000000 +0100
@@ -183,6 +183,7 @@ int scsi_complete_async_scans(void)
 
 /* Only exported for the benefit of scsi_wait_scan */
 EXPORT_SYMBOL_GPL(scsi_complete_async_scans);
+late_initcall(scsi_complete_async_scans);
 
 /**
  * scsi_unlock_floptical - unlock device via a special MODE SENSE command

  parent reply	other threads:[~2007-04-03 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 16:25 CONFIG_SCSI_WAIT_SCAN=m Hugh Dickins
2007-03-27 16:34 ` CONFIG_SCSI_WAIT_SCAN=m James Bottomley
2007-03-27 17:16   ` CONFIG_SCSI_WAIT_SCAN=m Hugh Dickins
2007-04-03 16:54   ` Hugh Dickins [this message]
2007-04-06 15:51 ` CONFIG_SCSI_WAIT_SCAN=m James Bottomley

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=Pine.LNX.4.64.0704031736380.9029@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --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®