public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: "K.R. Foley" <kr@cybsft.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12-rc1 won't boot if SCSI drivers are selected as modules
Date: Fri, 1 Apr 2005 21:31:05 -0500	[thread overview]
Message-ID: <9e47339105040118312ba5b356@mail.gmail.com> (raw)
In-Reply-To: <424D3BDD.5010001@cybsft.com>

On Apr 1, 2005 7:17 AM, K.R. Foley <kr@cybsft.com> wrote:
> I have an old Dell Precision 620 workstation with dual PIII 933's and
> 512 Mb memory. It also uses AIC-7899P U160/m SCSI controllers with one
> U160 drive (boot drive) and one slower 18 Gb. I have been running many
> different variants of the kernel on this system for quite some time with
> much success. However, no amount of gnashing of teeth or pulling of hair
> have been able to get this system to boot ANY 2.6.12-rc1 (including
> 2.6.12-rc1 vanilla, 2.6.12-rc1-mm3 and various RT patches) variant when
> the SCSI drivers are selected as modules (which is the way that I have
> always done it). Last night I built all of the necessary drivers into
> the kernel and the system boots fine.

I am also seeing this but not on every boot. My work around is to add
a 'sleep 2' to the nash script after the modules are loaded. Compling
everything in also worked.

This is discussed in the thread: "current linus bk, error mounting
root". I believe the answer is that it is not a kernel problem,
instead the init scripts have to be fixed.

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2005-04-02  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01 12:17 2.6.12-rc1 won't boot if SCSI drivers are selected as modules K.R. Foley
2005-04-02  2:31 ` Jon Smirl [this message]
2005-04-02 14:07   ` K.R. Foley

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=9e47339105040118312ba5b356@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=kr@cybsft.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