mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: david@lang.hm
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org
Subject: Re: deterministic scsi order with async scan
Date: Thu, 16 Jul 2009 11:31:13 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0907161128550.9159@asgard> (raw)
In-Reply-To: <20090716181521.GT24310@parisc-linux.org>

On Thu, 16 Jul 2009, Matthew Wilcox wrote:

> On Thu, Jul 16, 2009 at 10:23:45AM -0700, david@lang.hm wrote:
>> hmm, in that case how can I troubleshoot why this system is detecting the
>> two different PCI-E cards in different orders on different boots.
>
> I don't know.  Are the cards actually being detected in a different
> order, or are the Linux drivers being bound to them in a different order?

I don't know, the end result is that what device is scsi1, scsi2 is 
sometimes different when the machine boots. unfortunantly when they show 
up in the wrong order the system can't find it's boot drive

I guess that the fact that the bios is finding lilo and lilo is finding 
the kernel to try to boot is probably indicating that the hardware is 
being detected in the same order.

> Are you using modules or are these drivers built-in?

built-in

      reply	other threads:[~2009-07-16 18:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16  1:09 david
2009-07-16 11:33 ` Boaz Harrosh
2009-07-16 17:22   ` david
2009-07-16 18:32     ` James Smart
2009-07-16 18:43       ` david
2009-07-16 19:39         ` James Bottomley
2009-07-16 19:48           ` david
2009-07-16 19:56             ` James Bottomley
2009-07-16 20:59               ` david
2009-07-16 19:58             ` Boaz Harrosh
2009-07-16 20:05             ` Matthew Wilcox
2009-07-16 19:53     ` Boaz Harrosh
2009-07-16 11:57 ` Matthew Wilcox
2009-07-16 17:23   ` david
2009-07-16 18:15     ` Matthew Wilcox
2009-07-16 18:31       ` david [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=alpine.DEB.1.10.0907161128550.9159@asgard \
    --to=david@lang.hm \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®