From mboxrd@z Thu Jan 1 00:00:00 1970 From: maximilian attems Subject: Re: Remove scsi_wait_scan module Date: Wed, 30 May 2012 10:03:05 +0000 Message-ID: <20120530100305.GE10036@vostochny.stro.at> References: <1338110026.2957.5.camel@dabdike.int.hansenpartnership.com> <20120528100015.GB10036@vostochny.stro.at> <1338206866.6330.22.camel@dabdike> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <1338206866.6330.22.camel@dabdike> Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: James Bottomley Cc: linux-scsi , Dave Jones , Jeff Mahoney , Ben Hutchings , initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Mon, May 28, 2012 at 04:07:46PM +0400, James Bottomley wrote: > On Mon, 2012-05-28 at 10:00 +0000, maximilian attems wrote: > > > > There is quite a number of bug reports moaning about having to boot with > > `scsi_mod.scan=sync'. I didn't pass them on, because I didn't knew that > > the module itself got broken, for example: > > http://bugs.debian.org/616689 > > OK, so what these bugs show is the breakage ... basically scsi_wait_scan > isn't really waiting for the scans to complete. I can fix it in stable > so you can close your bug reports, but if I do, can you also transition > away from using it so I can remove it in 3.5? > Thank you very much for the patch, guess Ben will pick it for 3.2 via stable and we'll add it for 2.6.32 too. I'll have enough time for afterwards fix to have the udev wait root, even if right now I'm a bit unsure what it means beyond adding a specific rule? -- maks