rootfs on sda & async scan?

rootfs on sda & async scan?

[Guennadi Liakhovetski]

Hi

This is a basic confusion: if I read kernel config help to SCSI_SCAN_ASYNC 
correctly "If you build your SCSI drivers into the kernel, then everything         
will work fine if you say Y here." means I can have async "on" and root on 
sd* as long as the respective ldd is linked into the kernel. Now, this 
just didn't work for me under 2.6.22-rc3-... (scsi-misc-2.6) with 
sym53c8xx_2. I'd expected it would let scan run asynchronously, but wait 
as long as root on an sd* is requested. Do I understand it wrong or is 
this a bug somewhere. I also have 2 more ldd's compiled as modules.

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: rootfs on sda & async scan?

[Matthew Wilcox]

On Sun, Jun 17, 2007 at 12:42:44AM +0200, Guennadi Liakhovetski wrote:
> sd* as long as the respective ldd is linked into the kernel. Now, this 
> just didn't work for me under 2.6.22-rc3-... (scsi-misc-2.6) with 
> sym53c8xx_2. I'd expected it would let scan run asynchronously, but wait 
> as long as root on an sd* is requested. Do I understand it wrong or is 
> this a bug somewhere. I also have 2 more ldd's compiled as modules.

Did you have
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=f2f027c6e9912840020be8b78f037d5c8ac665e0
in your tree?  It's supposed to fix this bug.

Re: rootfs on sda & async scan?

[Guennadi Liakhovetski]

On Sat, 16 Jun 2007, Matthew Wilcox wrote:

> On Sun, Jun 17, 2007 at 12:42:44AM +0200, Guennadi Liakhovetski wrote:
> > sd* as long as the respective ldd is linked into the kernel. Now, this 
> > just didn't work for me under 2.6.22-rc3-... (scsi-misc-2.6) with 
> > sym53c8xx_2. I'd expected it would let scan run asynchronously, but wait 
> > as long as root on an sd* is requested. Do I understand it wrong or is 
> > this a bug somewhere. I also have 2 more ldd's compiled as modules.
> 
> Did you have
> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=f2f027c6e9912840020be8b78f037d5c8ac665e0
> in your tree?  It's supposed to fix this bug.

No, it is still not in scsi-misc-2.6.

Thanks for the pointer
Guennadi
---
Guennadi Liakhovetski