Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753842AbZDUMau (ORCPT ); Tue, 21 Apr 2009 08:30:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751813AbZDUMah (ORCPT ); Tue, 21 Apr 2009 08:30:37 -0400 Received: from qw-out-2122.google.com ([74.125.92.24]:10208 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751498AbZDUMag (ORCPT ); Tue, 21 Apr 2009 08:30:36 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=C0X9/w157pVNxIQWANWV3pIZYFLiHRiYIx0qh4rMClzc9njnPggA3w7oIsM998F31q lriVRI/l2GsdYEG/xQr+vhF4CBRXhf/K6XYoqgUeh8GQ5fTF43n7DUsVh3TPi1BLwtVH p2YqWJn/+vF8MapmNvkLJ1rIaVZnSN/HQR/9I= Message-ID: <49EDBC62.5070202@panasas.com> Date: Tue, 21 Apr 2009 15:30:26 +0300 From: Benny Halevy User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: Matthew Wilcox CC: Jeff Garzik , Jeff Garzik , lkml , linux-ide@vger.kernel.org, linux-scsi , Arjan van de Ven , Andrew Morton Subject: Re: Is sata_nv compatible with async scsi scan? References: <49ED6FD7.3070307@panasas.com> <49ED9FAC.1080303@garzik.org> <20090421112608.GV1926@parisc-linux.org> In-Reply-To: <20090421112608.GV1926@parisc-linux.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1740 Lines: 47 On Apr. 21, 2009, 14:26 +0300, Matthew Wilcox wrote: > On Tue, Apr 21, 2009 at 06:27:56AM -0400, Jeff Garzik wrote: >> Benny Halevy wrote: >>> Hi Jeff, >>> >>> Since 2.6.29 I'm having intermittent problems with booting kernels. >>> After supposedly waiting for scsi async scan to complete, >>> quite frequently I see errors from the init resume process >>> when it fails to find the swap partition and later the root >>> file system fails to load. >>> >>> A workaround that I found to be helpful is booting the kernel >>> with scsi_mod.scan=sync so I suspect sata_nv has a problem >>> with asynchronous scanning. >> Personally, I think the whole system is broken, so continue to use this >> workaround until it gets fixed upstream. This sounds like some timing >> issues related to waiting for the device probe to finish, something that >> people keep breaking (witness my USB flash drive boot breakage). > > No, it's 4ace92fc112c6069b4fcb95a31d3142d4a43ff2a. > > Specifically, this bit: > > @@ -179,6 +180,8 @@ int scsi_complete_async_scans(void) > spin_unlock(&async_scan_lock); > > kfree(data); > + /* Synchronize async operations globally */ > + async_synchronize_full(); > return 0; > } > > Vegard Nossum has a patch that seems to have been ignored: > > http://marc.info/?l=linux-kernel&m=123920746830420&w=2 > Hmm, it might help somewhat but my test machine still failed to boot 2 out of 5 times with this patch. Benny -- 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/