From: Douglas Gilbert <dougg@torque.net>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org, james.bottomley@steeleye.com
Subject: Re: [PATCH] link scsi_debug later
Date: Sat, 18 Mar 2006 01:24:03 -0500 [thread overview]
Message-ID: <441BA783.3030807@torque.net> (raw)
In-Reply-To: <20060317221920.3c84fc65.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> On Fri, 17 Mar 2006 21:29:24 -0800 Andrew Morton wrote:
>
>
>>"Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>>
>>>From: Randy Dunlap <rdunlap@xenotime.net>
>>>
>>>Link scsi-debug driver after SATA so that scsi-debug does not
>>>interfere with real SCSI device ordering.
>>>Yes, I was bitten by this.
>>>
>>
>>What does "bitten" mean?
>
>
> It means that I got the usual "VFS: could not find root filesystem on
> device (8,8)" (or however it is spelled).
> Oh, and that I had to add netconsole to see what was causing it,
> but that is easy enough to do.
>
>
>>Is this a regression?
>
>
> It's probably been like this ever since SATA was added (libata)
> and only happens if SCSI_DEBUG=y (so I changed it to =m).
> I can't say that it's a regression since this occurred on a new
> machine.
Ah, if scsi_debug is a module, nothing is going to
load it automatically (at least the PCI subsystem
won't load it). However if it is built in then
it will "steal" /dev/sda (if some other SCSI LLD
hasn't already got it). That would then cause
a SATA driver to get /dev/sdb ... That is enough
to cause a kernel parameter like "root=/dev/sda8"
to flounder and give the "could not find root filesystem"
error.
A regression??
Hmm.
Doug Gilbert
next prev parent reply other threads:[~2006-03-18 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 20:44 [PATCH] link scsi_debug later Randy.Dunlap
2006-03-18 5:29 ` Andrew Morton
2006-03-18 6:19 ` Randy.Dunlap
2006-03-18 6:24 ` Douglas Gilbert [this message]
2006-03-18 13:22 ` James Bottomley
2006-03-18 19:07 ` Randy.Dunlap
2006-03-18 6:27 ` Andrew Morton
2006-03-18 13:07 ` 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=441BA783.3030807@torque.net \
--to=dougg@torque.net \
--cc=akpm@osdl.org \
--cc=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.