Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753958Ab2E3XAq (ORCPT <rfc822;w@1wt.eu>);
	Wed, 30 May 2012 19:00:46 -0400
Received: from mail-ob0-f174.google.com ([209.85.214.174]:52627 "EHLO
	mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751635Ab2E3XAo convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 30 May 2012 19:00:44 -0400
MIME-Version: 1.0
In-Reply-To: <jq3r1h$p37$1@dough.gmane.org>
References: <20120525175140.22423.21697.stgit@dwillia2-linux.jf.intel.com>
	<jq3r1h$p37$1@dough.gmane.org>
Date: Wed, 30 May 2012 16:00:43 -0700
X-Google-Sender-Auth: vrK32Iux3LruoJeTiBkoojVuy70
Message-ID: <CAA9_cmfPXrx-DAA2oSH+ZvrLTvZsT8g0O3jNMT5ZnA8Z_GWTMA@mail.gmail.com>
Subject: Re: [PATCH v2] scsi: fix async probe regression
From: Dan Williams <dan.j.williams@intel.com>
To: walt <w41ter@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1288
Lines: 32

On Tue, May 29, 2012 at 5:53 PM, walt <w41ter@gmail.com> wrote:
> On 05/25/2012 10:55 AM, Dan Williams wrote:
>> Commit a7a20d1 "[SCSI] sd: limit the scope of the async probe domain"
>> moved sd probe work out of reach of wait_for_device_probe(). ?Allow it
>> to be synced via scsi_complete_async_scans().
>
> Hi Dan. ?After applying version 2 of a7a20d1 I can boot again, but there's
> a catch :)

Ah you took me off the cc, so I missed this originally.

>
> My grub.cfg boot menu entry uses the root=PARTUUID=<guid> syntax, but that
> has stopped working. ?After a7a20d1(v2) I have to use root=/dev/sda5 or I
> get the familiar "can't find block device (foo,bar)" kernel panic.

What is a7a20d1(v2)?  That's the original commit that broke things, so
I'm confused.

> Any idea what would cause that particular kind of breakage?

The fix should be equivalent for both root= options because if the
device can be found by /dev/sda5 I don't see anything related to the
async subsystem that would prevent it from being looked up by uuid??

--
Dan
--
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/