[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1244475124.4079.177.camel@mulgrave.site>
Date: Mon, 08 Jun 2009 15:32:04 +0000
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Chris Clayton <chris2553@...glemail.com>
Cc: NeilBrown <neilb@...e.de>,
Jaswinder Singh Rajput <jaswinder@...nel.org>,
linux-kernel@...r.kernel.org, scsi <linux-scsi@...r.kernel.org>,
Tejun Heo <tj@...nel.org>,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: 2.6.30-rc8 Oops whilst booting
On Mon, 2009-06-08 at 16:17 +0100, Chris Clayton wrote:
> > Actually, you can save yourself a lot of pain by mounting by label
> > instead ... that way both grub and fstab will find your root disc even
> > if it has swapped order.
> >
>
> Would I be right in assuming from this that "out-of-order" detection
> is expected behaviour? If so, I'll fix up my system and shut up :-) I
> suspect I may not be the only person on the planet who specifies the
> root filesystem in this way, though.
Yes and no ... yes generally because parallel asynchronous probing does
relax the ordering rules, so if you have multiple devices the ordering
can easily change. No in your particular case because you have a single
ata_piix and even with async enabled it should probe PATA first (master
and slave) followed by SATA. The fact that the PATA and SATA probes
didn't synchronise is a bug somewhere, but I'm not sure where.
Could you fix your system to do the label mounting and post the full
boot log where it's out of sequence? I have a nasty feeling we might
have got the ata probe order correct only to be thrown out of order by
sd driver attachment.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists