| 1 |
On 11/11/2011 04:16 AM, Walter Dnes wrote: |
| 2 |
> On Thu, Nov 10, 2011 at 07:51:04PM +0100, Jarry wrote |
| 3 |
>> Hi, |
| 4 |
>> during testing I compiled kernel with some modules |
| 5 |
>> (make&& make modules_install). Now I deactivated |
| 6 |
>> module-support and compiled everything in kernel. |
| 7 |
> |
| 8 |
> On this very same topic, there's one module I can't seem to get rid |
| 9 |
> of. At the end of every "make", I see stuff like... |
| 10 |
> |
| 11 |
> Kernel: arch/x86/boot/bzImage is ready (#2) |
| 12 |
> Building modules, stage 2. |
| 13 |
> MODPOST 1 modules |
| 14 |
> CC drivers/scsi/scsi_wait_scan.mod.o |
| 15 |
> LD [M] drivers/scsi/scsi_wait_scan.ko |
| 16 |
> |
| 17 |
> Then "make modules_install" spits out... |
| 18 |
> |
| 19 |
> [i3][root][/usr/src/linux] make modules_install |
| 20 |
> INSTALL drivers/scsi/scsi_wait_scan.ko |
| 21 |
> DEPMOD 2.6.39-gentoo-r3 |
| 22 |
> |
| 23 |
> *BUT*, it doesn't seem to be running... |
| 24 |
> |
| 25 |
> [i3][root][/usr/src/linux] lsmod |
| 26 |
> Module Size Used by |
| 27 |
> |
| 28 |
> I can't seem to find where in the "make menuconfig" process it's |
| 29 |
> selected. I don't want to edit my .config directly. What gives? |
| 30 |
|
| 31 |
This module cannot be disabled. The function of this module is a bit |
| 32 |
special and unlike other modules. Its job is to stall the boot process |
| 33 |
of the kernel until the SCSI drivers have finished scanning all their |
| 34 |
buses. That's the only thing this module does. It's not a driver and |
| 35 |
does not offer any kind of functionality; it's just a "handbrake", and |
| 36 |
when that job is finished (SCSI drivers finished scanning) it's no |
| 37 |
longer needed. It is used by initrd scripts. If you don't use modules |
| 38 |
in initrd, then this module is not used at all. |
| 39 |
|
| 40 |
Also, it *needs* to be loaded as a module and can't be built into the |
| 41 |
kernel, since it stalls the boot process as soon as its loaded. It |
| 42 |
cannot be disabled. This is a conscious decision by upstream and not an |
| 43 |
oversight. The rationale is that there's nothing to gain by disabling |
| 44 |
it while it can be vital for people using initrd. |
| 45 |
|
| 46 |
So short answer: ignore it. Or simply delete it. |
Archives