Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756721AbZFHPcT (ORCPT ); Mon, 8 Jun 2009 11:32:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754400AbZFHPcH (ORCPT ); Mon, 8 Jun 2009 11:32:07 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:43356 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753569AbZFHPcG (ORCPT ); Mon, 8 Jun 2009 11:32:06 -0400 Subject: Re: 2.6.30-rc8 Oops whilst booting From: James Bottomley To: Chris Clayton Cc: NeilBrown , Jaswinder Singh Rajput , linux-kernel@vger.kernel.org, scsi , Tejun Heo , Arjan van de Ven In-Reply-To: References: <200906061959.55592.chris2553@googlemail.com> <200906062215.30571.chris2553@googlemail.com> <1244381140.30664.12.camel@ht.satnam> <1244413881.18742.31.camel@ht.satnam> <2f9e3044bafcae848f74a1492b0ea471.squirrel@neil.brown.name> <1244471000.4079.36.camel@mulgrave.site> Content-Type: text/plain Date: Mon, 08 Jun 2009 15:32:04 +0000 Message-Id: <1244475124.4079.177.camel@mulgrave.site> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1399 Lines: 31 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/